blunalucero / MODS-RDF

MODS RDF is an RDF ontology for MODS. As MODS is an XML schema for a bibliographic element set, MODS RDF is an expression of that element set in RDF.
7 stars 4 forks source link

digitalOrigin #31

Open melanieWacker opened 9 years ago

melanieWacker commented 9 years ago

Ref: http://www.loc.gov/standards/mods/userguide/physicaldescription.html#digitalorigin We agreed to do away with the physicalDescription wrapper, which is fine. However, there is one more issue that I don't believe was discussed: digitalOrigin comes with controlled values: 1) born digital – A resource was created and is intended to remain in digital form. 2) reformatted digital – A resource was created by digitization of the original which was in a non-digital form (except original microforms). 3) digitized microfilm – A resource was created by digitizing a microform. 4) digitized other analog – A resource was created by digitizing an intermediate form of the original resource (but not microform) such as photocopy, transparency, slide, 2nd generation analog tapes, etc.

These controlled string values could be easily converted to URIs. Currently, there is no other source vocabulary (that I could find) that includes these values, except for codes in the 007 in MARC, but that's only for three of them (not born digital) and even these three aren't on id.loc.gov as far as I can see. Is there any chance that these values could be defined for id.loc.gov or is there another way to handle them?

raydAtLC commented 9 years ago

There is another way to do it. Define RDF class modsrdf:DigitalOrigin, subclass of skos:Concept, and define “instances” of class madsrdf:DigitalOrigin: madsrdf:bornDigital, etc.

Here’s an example: http://www.w3.org/TR/annotation-model/#motivations

Ray

From: melanieWacker [mailto:notifications@github.com] Sent: Monday, March 30, 2015 4:52 PM To: blunalucero/MODS-RDF Subject: [MODS-RDF] digitalOrigin (#31)

Ref: http://www.loc.gov/standards/mods/userguide/physicaldescription.html#digitalorigin We agreed to do away with the physicalDescription wrapper, which is fine. However, there is one more issue that I don't believe was discussed: digitalOrigin comes with controlled values: 1) born digital – A resource was created and is intended to remain in digital form. 2) reformatted digital – A resource was created by digitization of the original which was in a non-digital form (except original microforms). 3) digitized microfilm – A resource was created by digitizing a microform. 4) digitized other analog – A resource was created by digitizing an intermediate form of the original resource (but not microform) such as photocopy, transparency, slide, 2nd generation analog tapes, etc.

These controlled string values could be easily converted to URIs. Currently, there is no other source vocabulary (that I could find) that includes these values, except for codes in the 007 in MARC, but that's only for three of them (not born digital) and even these three aren't on id.loc.gov as far as I can see. Is there any chance that these values could be defined for id.loc.gov or is there another way to handle them?

— Reply to this email directly or view it on GitHubhttps://github.com/blunalucero/MODS-RDF/issues/31.