The dpp: namespace

Custom JSON-LD vocabulary for EU Digital Product Passport fields that aren't yet covered by Schema.org or GS1. Editioned uses this namespace in every per-edition DPP export.

Why a custom namespace

ESPR Regulation 2024/1781 and the CIRPASS-2 reference architecture define a set of fields that any EU Digital Product Passport must carry: edition number within a series, carbon footprint, recycled-content percentage, expected lifespan, conformity markings, and several more. None of these properties exist in Schema.org or the GS1 web vocabulary yet.

Until the published EN 1821x URIs are broadly adopted by downstream tooling, JSON-LD records need a stable identifier so downstream tooling (validators, registries, marketplaces, AI agents) can resolve the fields. The dpp: namespace is that placeholder. It is documented here so any consumer can dereference https://editioned.app/vocab/dpp# and get a real, structured definition.

Properties

Every property below is in active use in Editioned's DPP JSON-LD exports. The blog post DPP JSON-LD fields, validators, and traps walks through each one with realistic values, units, and validator behaviour.

JSON-LD @context

Add the namespace to your @context array alongside Schema.org and GS1:

{
  "@context": [
    "https://schema.org",
    { "gs1": "https://gs1.org/voc/" },
    { "dpp": "https://editioned.app/vocab/dpp#" }
  ]
}

Stability and the CEN/CENELEC swap path

Editioned commits to maintaining the https://editioned.app/vocab/dpp# URI through the publication of CEN/CENELEC EN 1821x. After publication:

• This page will continue to resolve so historical DPP records do not break.
• Where the field name is identical in EN 1821x, the official URI becomes the canonical reference and Editioned exports will start emitting it as the primary key with dpp: kept as an alias.
• Where EN 1821x renames a field, this page will document the mapping so consumers can rewrite at their own pace.

See also

• Shopify provenance certificates in 2026, the complete guide, the operational pillar covering the four implementation approaches and the five-minute hosted-cert setup.
• DPP JSON-LD fields, validators, and traps, practical walkthrough of every field, with example values and validator notes.
• EU DPP timeline 2026-2030, when each sector's regulation lands.
• Why the EU rejected blockchain for the Digital Product Passport, architectural context.
• About Editioned, who built this and why.