How a description is structured and moved between systems — the working machinery of records, structural and preservation metadata, and domain-specific schemas.
Standard · encodingActiveFree to access
MARC 21
Still the most widely used record-exchange format in production catalogs, even as libraries transition toward BIBFRAME; the specification itself is freely published. Status here reflects its current role in practice, not its direction of travel.
See also: MODS.
loc.gov/marc
Standard · linked dataEmergingFree to access
BIBFRAME · Bibliographic Framework Initiative
The Library of Congress's linked-data vocabulary for describing bibliographic resources, built to eventually succeed MARC. The entire LC catalog has now been converted at id.loc.gov; a Conversion 3.0 was announced in December 2025 and an update forum held in February 2026, showcasing production tools including the Marva editor and the Scriptshifter transliteration tool. Emerging here describes adoption, not readiness: BIBFRAME is in production use at the Library of Congress, but the field has not settled on it the way it still relies on MARC 21. See also knowledge graphs, Section VII.
loc.gov/bibframe
ProjectEmergingMixed
MARC21 to LRM/RDA/RDF Mapping and Conversion Project · M2R / MARC2RDA
An independent, volunteer-led, open-source effort, begun in 2021 at the University of Washington Libraries, to map MARC21 bibliographic records to LRM/RDA/RDF and convert them with an XSLT transformation — a route from legacy records to the IFLA LRM and Official RDA that does not run through BIBFRAME. Phase I (concluded September 2025) covered single-expression manifestations and simple augmentation aggregates, and published mapping spreadsheets, transformation code, documentation, sample transformed records from the Library of Congress, the University of Washington Libraries, and the National Library of New Zealand, and an online conversion tool. Phase II extends the work to more complex aggregates and diachronic works. The project cautions that its output data and URIs are experimental, not persistent, and not ready for production. Co-led by Crystal E. Yragui and Cypress Payne (West Virginia University). The project’s documentation site is licensed CC BY-SA 4.0; the code license was not confirmed in the sources checked here, so confirm it in the repository before reuse.
marc2rda.info
github.com/crystalyragui/MARC2RDA
Standard · metadataActiveFree to access
MODS · Metadata Object Description Schema
The Library of Congress's XML schema and guidelines for encoding a resource description. It can carry selected data from MARC 21 records and also supports original description, using language-based element names rather than MARC's numeric tags, which has made it a common descriptive layer in digital library systems; MODS records are often embedded in METS packages. Maintained by the MODS/MADS Editorial Committee with LC's Network Development and MARC Standards Office. Its companion for authority data is MADS (Section VI).
See also: MADS (Section VI), METS, MARC 21.
loc.gov/standards/mods
Vocabulary · metadataActiveFree to access
DCMI Metadata Terms · Dublin Core
The cross-domain vocabulary — the DCMI Metadata Terms, which extend the original fifteen-element Dublin Core set — still used and taught as one of the simplest on-ramps to structured description, and the schema Omeka is built around (Section IX).
See also: DCTAP.
dublincore.org
Standard · metadataActiveFree to access
DCTAP · DC Tabular Application Profiles
A DCMI community specification for writing a metadata application profile as a table. Each row names a property and the rules for using it in one project: whether it is mandatory or repeatable, what kind of value it takes, and any constraint on those values. Only the propertyID column is required, and profiles are usually saved as CSV, so a profile can be drafted in any spreadsheet. DCTAP is the intermediate step between a general vocabulary such as DCMI Metadata Terms and the records a project creates. Supporting tools include dctap-python, which reads a profile and reports problems, and Tapir, a graphical editor; related tools generate SHACL shapes from a profile. A profile states rules; testing records against them is a separate step (see SHACL). The specification's license was not checked for this edition, so it is labeled Free to access. A sample profile for student projects is linked below.
See also: DCMI Metadata Terms, SHACL (Section VII), SHACL Playground (Section XIV).
dublincore.org/specifications/dctap/primer
github.com/dcmi/dctap
toolbox-sample-dctap.csv (sample profile, CSV)
Standard · metadataActiveFree to access
METS · Metadata Encoding & Transmission Standard
Structural metadata for digital library objects — how pages, files, and behaviors of a digital object relate to one another.
See also: MODS, BagIt.
loc.gov/standards/mets
Standard · metadataActiveFree to access
PREMIS · Preservation Metadata: Implementation Strategies
A widely used standard for documenting the preservation history and integrity of digital objects.
See also: BagIt, DART (Section X), CLOCKSS (Section X).
loc.gov/standards/premis
StandardActiveFree to access
BagIt · File Packaging Format (RFC 8493)
A set of file-layout conventions for storing and transferring digital content. A bag is a folder holding the payload files plus small text tag files, including a manifest that lists every payload file with its checksum, so a receiving system can verify that what arrived matches what was packaged. Developed by the Library of Congress and the California Digital Library; version 1.0 was published as RFC 8493 in October 2018. A packaging specification, not software: DART (Section X) creates and validates bags. The teaching question: what exactly travels with a digital object, and how do we check that the transferred files match what was packaged?
See also: DART (Section X), PREMIS, METS.
rfc-editor.org/rfc/rfc8493
Standard · encodingActiveFree to access
TEI · Text Encoding Initiative
A widely used markup standard for representing humanities texts in machine-readable form; still very actively maintained.
tei-c.org
Standard · encodingActiveFree to access
EAD · Encoded Archival Description
The archival finding-aid encoding standard. The Library of Congress presents EAD4 as the current version; EAD3 and the older EAD 2002 persist in existing finding aids and tools.
See also: ArchivesSpace (Section IX), AtoM (Section IX).
loc.gov/ead
Standard · protocolActiveFree to access
IIIF · International Image Interoperability Framework
A widely adopted framework for interoperable delivery of digitized images and audiovisual material across institutions.
iiif.io
Standard · metadataActiveFree to access
PBCore
Metadata standard for public broadcasting and audiovisual archives.
pbcore.org
Standard · e-learningLegacyFree to access
SCORM · Sharable Content Object Reference Model
Not primarily a metadata standard, despite often being filed as one — it's a content-packaging and runtime-communication specification (how an e-learning package is structured, and how it talks to the LMS via a JavaScript API), with a metadata layer folded in. Frozen since 2009 and still widely supported — many LMS platforms still import it — even though current guidance from the field treats it as legacy rather than the forward-looking choice.
See also: Common Cartridge.
adlnet.gov/scorm
Standard · e-learningActiveFree to access
xAPI (Experience API) / cmi5
xAPI (2013) tracks learning activity as "noun, verb, object" statements sent to a Learning Record Store, capturing activity SCORM can't see — offline, cross-device, outside the LMS entirely. cmi5 is a profile built on xAPI that adds back SCORM-style launch and completion structure. Some current guidance, including from the US Department of Defense, treats cmi5 as SCORM's intended successor for new development; SCORM's large existing content library is a main reason it has not been displaced outright. xAPI and cmi5 are related but not interchangeable: confirm which one a system actually supports.
See also: Common Cartridge.
xapi.com
Standard · e-learning packagingActiveMixed
Common Cartridge · 1EdTech
1EdTech's standard for packaging and exchanging digital learning materials and assessments between publishers, learning platforms, portals, and repositories, including links to LTI tools. A cartridge bundles content, activities, and assessments, and its learning objects can be tagged with topics, object types, and academic standards; version 1.4 adds accessibility and K-12 metadata. Mixed because version 1.3 is public while the 1.4 specification, implementation guide, validators, and certification materials are for members. These specifications address related but different problems: packaging and exchanging learning resources (Common Cartridge), packaging content and communicating with a learning platform at runtime (SCORM), and recording learning activity (xAPI and cmi5). They are not interchangeable. Aletheia (Section IX) is a reported implementation example: it exports Common Cartridge files, which is not evidence of certification or of tested compatibility beyond what its developer reports.
See also: SCORM, xAPI (Experience API) / cmi5, Aletheia (Section IX).
1edtech.org/standards/cc
Standard · metadataLegacyMixed
IEEE LOM · Learning Object Metadata (IEEE 1484.12.1)
Present in the 2001 original under “Digital Learning Objects”; formally still alive (revised as recently as 2020, clearing IEEE's 10-year automatic-withdrawal rule), but its real ambition — a rich, nine-category schema meant to make learning objects discoverable and reusable across a networked ecosystem of repositories — never really arrived. All elements are optional, and most real records populate only a thin slice. Most often met today as the metadata layer folded into SCORM above. IEEE publishes the standard text, which is sold; free secondary descriptions exist.
Vocabulary · metadataActiveFree to access
schema.org
Cross-domain structured-data vocabulary consumed directly by search engines; used throughout this site's own JSON-LD. See also knowledge graphs and validation tools, Sections VII and XIV.
schema.org