To provide rich technical metadata about binary content, I would like to use full-featured descriptions attached to the binary:

  1. I would like to store the XML technical metadata generated by FITS.  There is currently an effort to develop a shared RDF vocabulary for technical metadata that may replace FITS in the future, but current tools work with FITS XML.
  2. I would like to store PREMIS RDF, which contains a many nested elements with blank node identifiers.  Skolemizing these blank nodes in my application is possible, but would be very cumbersome.  It would be much more convenient for the blank nodes to be Skolemized by Fedora.

In both of these cases, I would like the descriptions to be dependent on the binary – they are not useful without the binary they describe.  In particular, they should be automatically removed if the binary is removed.

 

  • No labels

3 Comments

  1. Is there some reason you can't use hash-URIs instead of blank nodes?

    1. Unknown User (escowles@ucsd.edu)

      We could use hash-URIs instead.  Having the repository convert bnodes in POSTed RDF to hash-URIs would be even better.

      1. That's an intriguing possibility. I'd have to think about it to understand whether it makes semantic sense. Can you bring this up at a weekly call?