METS Application Profiles Morgan Cundiff Network Development and MARC Standards Office Library of Congress
What is a METS Application Profile? “METS Profiles are intended to describe a class of METS documents in sufficient detail to provide both document authors and programmers the guidance they require to create and process METS documents conforming with a particular profile.” A profile is expressed as an XML document. There is a schema for this purpose.
What is a “class of documents”? • An open question • At LC we are making a one-to-one relationship between a document class, or “object type” and a typical library item, e.g. a book, a photograph, a compact disc, etc.
How does one get started with Profiles? • Download the documentation • Download the XML Schema for Profiles • Download the example Profile document http://www.loc.gov/mets
How will Profiles be made available? A registry of METS profiles will be maintained on the METS website. All profiles can be freely downloaded.
How does one register a Profile? • Send the profile document via email to email@example.com • The METS Editorial Board will review the profile, perhaps suggest changes, etc • Upon completion of review it will be added to the METS website registry.
What are the 13 components of a Profile? • Unique URI • Short Title • Abstract • Date and time of creation • Contact Information • Related profiles
What are the 13 components? (cont’d) • Extension schemas • Rules of description • Controlled vocabularies • Structural requirements • Technical requirements • Tools and applications • Sample document
What are “structural requirements”? • Occurrence of elements (METS) • Occurrence of elements (extension schemas) • Structure Map model • Include metadata with mdRef or mdWrap • Embed content file data in METS document with Fcontent or reference using Flocat • Associate elements with ID/IDREF attributes
Summary Application Profiles: • Provide guidance for the creation on METS documents • Aid machine processing of METS documents (software tool building) • A step towards interoperability of digital libraries