Positioning
Labelcopy is designed to complement existing standards.
DDEX remains important for established business-message, rights, reporting, and DSP workflows. Labelcopy focuses on an open, developer-friendly source-of-truth model for release metadata and verifiable packages.
| Area | Labelcopy | DDEX |
|---|---|---|
| Primary role | Canonical release model, validation, packaging, archiving, and provenance. | Established industry message standards for enterprise delivery, reporting, rights, and partner exchange. |
| Developer surface | JSON Schema, content-addressed IDs, LCX packages, examples, and reference tooling in scope. | XML-based standards with broad adoption in major-label, distributor, DSP, and rights workflows. |
| Best fit | Artists, labels, archives, production teams, tool builders, and systems that need a clear internal source of truth. | Downstream integrations where trading partners already require DDEX messages. |
| Interoperability stance | Can act as the authoritative internal model and export to required partner formats. | Can remain the required external format for specific business relationships. |
| Governance goal | Open, accessible, community-shaped specifications with no membership barrier to read or implement. | Mature standards process serving a large existing industry network. |
The practical goal is simple: keep release metadata accurate at the source, then interoperate with whatever the destination requires.