• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Finally, you can manage your Google Docs, uploads, and email attachments (plus Dropbox and Slack files) in one convenient place. Claim a free account, and in less than 2 minutes, Dokkio (from the makers of PBworks) can automatically organize your content for you.


Formal data model for MODS and MADS

Page history last edited by Jenn Riley 9 years, 3 months ago

What we want to do


The metadata landscape in the cultural heritage community has evolved significantly since MODS and MADS were first designed. At this point it appears there is value in a clearly and intentionally articulated formal data model to define these formats, upon which can be defined various encoding options. The expression of a data model both in a textual form for human consumption, and as RDF classes and properties are common techniques in this community, and upon initial analysis both of these appear to be a fruitful direction for MODS and MADS. It is likely that a formal application profile for the encoding of bibliographic information would be beneficial to current MODS implementers as well.


This work is planned to occur in stages:

  1. Analyze current MODS and MADS XML Schemas to determine the semantics behind the XML encoding
  2. Articulate these semantics in prose, and as RDF classes and properties
  3. Refine this prose and the RDF classes and properties to be clearer, and otherwise improve them (defining domains/ranges)
  4. Connect (using RDF mechanisms) the MODS RDF classes and properties to RDF related classes and properties from other sources (via RDFS)
  5. Provide written guidance for MODS XML implementers in how to achieve the semantics of legacy XML records in the new form
  6. Create other data encodings for the MODS classes and properties defined in RDF, including XML
  7. (possibly) Articulate a formal application profile for the use of RDF classes and properties from a variety of sources to create robust linked bibliographic and authority descriptions


Many features of MODS exist in close or loose matches in other RDF vocabularies. We hope to achieve maximum flexibility by defining all significant classes and properties implied by the existing XML encoding in a MODS RDF namespace, but also making large numbers of connections to other vocabularies (BIBO, ISBD in RDF, FRBR in RDF, RDA in RDF, etc.).


Discussion documents (beware! under constant revision)


Comments (0)

You don't have permission to comment on this page.