xdm:navOrder |
---|
2 |
XDM incorporates or builds a number of existing standards and specifications.
Standard | Used for | Status |
---|---|---|
Microsoft CDM | Data model for business | Beta |
XMP | Asset | Stable |
schema.org | Business schemas | Evolving |
JSON Schema | Representing data model | Evolving |
JSON Hypertext Application Language | Expressing links between models | Evolving |
EXIF | Image metadata | Stable |
TIFF | Image metadata | Frozen |
W3C Activity Streams | Event model | Stable |
Dublin Core | Cross-media metadata | Stable |
URI | Core datatype | Stable |
BCP 47 – Tags for Identifying Languages | Core datatype | Stable |
Prior to XDM, Adobe defined and standardized the Extensible Metadata Platform (XMP) throughout its Creative Cloud products. The vocabularies and operations of XMP entities are essential for those products as is XDM for the wider experience technology ecosystem.
In XDM, these two efforts are integrated via the Resource Description Framework (RDF), which is a Word Wide Web Consortium (W3C) standard for data model interchange. XMP models are, at their core, RDF models expressed in an XML-based serialization. XDM models are, at their core, also RDF models, expressed in JSON-LD. Either one can be translated to the other using the underlying RDF model as an intermediary.
This fundamental interoperability means all existing XMP models (vocabularies, in XMP parlance) are intrinsically available for use in XDM. Accordingly, XDM preserves these models with their existing, fully-qualified property names and semantics. When ACP incorporates these properties into specific media types, a JSON Schema definition, and associated JSON-LD context, are also defined for these properties, as for any other XDM property.
XDM consumers that work with digital media assets (PSD, PDF, and so on) are expected to support XMP as-is—that is, serialized in XMP—as well as expressed in JSON-LD. This latter requirement makes XMP-based data available to all other system components in XDM's preferred format.