Skip to content

Host DPP content specifications (JSON-LD) under /spec/ — immutable, PoC-marked, DCAT-listed #135

Closed

Description

@stiebitzhofer

Counterpart of material-identity/schema#478 (decided 2026-10-13): DPP content specifications become JSON-LD and are hosted here, next to the dictionary entries, because the technical requirements are the same: immutable versioned resources, stable resolvable IRIs, cache headers, digests and a release process. Everything remains a PoC.

Scope for this repo: hosting only

  • A new collection under /spec/, e.g. https://material-identity.eu/spec/<act>/<version>. The IRIs carry no "poc" segment, because they are permanent.

  • The content arrives finished from the schema repo, which does the authoring and the Java gates. This repo hosts the immutable result. It checks JSON-LD syntax and the presence of the PoC status, but does not re-validate content rules.

  • Unmistakable PoC marking:

    • a status field in every JSON-LD;
    • PoC text on every HTML page;
    • the entry in the DCAT catalogue.

    The EU will publish real content specifications as JSON-LD too, and a spec on a .eu domain must not be mistaken for one.

  • Licence per resource via dct:license. The repo's blanket CC0 statement must not cover specs unless they are decided to be CC0. Open decision on schema#478: CC0 or CC-BY-4.0.

  • Immutability and caching as for entries: Cache-Control: public, max-age=31536000, immutable on a published version. An index or catalogue of versions is short-cached, like /feed.xml and /superseded.json.

  • Content negotiation: application/ld+json for machines and HTML for people (cf. schema#399).

  • A DCAT catalogue listing dictionary releases and content specifications, each with its distributions and SHA-256 checksums.

Constraint: two-phase release

A content specification may only pin entries already published here: resolvable, immutable, and digest-verifiable. Entries are released first and the specification follows later, never in the same release. The schema repo's publication gate enforces this by resolving each dictionaryReference against this site.

Not in scope

Authoring specifications, the content gates, and passport validation all stay in the schema repo.

Activity

  1. stiebitzhofer commented on Oct 13, 2026

    @stiebitzhofer
    MemberAuthor

    Licence decided (owner, 2026-10-13): CC0-1.0 for content specifications, same as entries. State it per resource anyway (dct:license in each JSON-LD and in the DCAT catalogue).

  2. stiebitzhofer commented on Nov 2, 2026

    @stiebitzhofer
    MemberAuthor

    Scheduled as part of schema DPP v0.0.3 (material-identity/schema#546). This must be released before the schema repo publishes v0.0.3 (two-phase rule). Scope per the merged design docs/design/content-spec-jsonld.md: /spec/<act>/<version> (+ /context.jsonld, /compressed.schema.json, /full.schema.json), the /spec/<act> series and /catalog DCAT, checks (add-only spec/, JSON-LD syntax via oxigraph, PoC status, CC0, pins published), and the new mi: terms plus a resolvable /ns. No new entries are needed: the v0.0.3 closure equals v0.0.2's and the access-category Values are already published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions