Introduction¶
The Seed ontology describes the credentials of the Seedbed demonstration dataspace, operated by DataSpaceLab. It is a copy of the D4NX 1.2 ontology (Gaia-X participants and the Gaia-X ICAM semantic model), in its own namespace, so that demonstrations never depend on a production dataspace.
What the ontology covers¶
- Gaia-X participants (module
seed-gaiax): the Gaia-X LoireLegalPerson, with its postal addresses and one of the six registration number types (VatID,LeiCode,EORI,EUID,TaxID,LocalRegistrationNumber). - Gaia-X 22.10 compatibility (module
seed-gaiax-2210): the formerLegalParticipant. - Gaia-X ICAM semantic model, not published in the Gaia-X ontology yet, so defined in the Seed
namespace:
- trust (module
seed-trust):TrustedDigitalIdentityCredential,TrustScopeCredential,TrustRelationCredential; - party credentials (module
seed-party):PartyCredentialand its specialisations (NaturalPersonPartyCredential,EmployeeCredential,LegalPersonPartyCredential,SupplierPartyCredential,DelegatedSupplierPartyCredential,ServicePartyCredential,MembershipPartyCredential), and the access credentials (AccessEntitlementCredential,AdminPartyCredential); - assertions (module
seed-assertion):AssertionCredential,SignedAgreementCredential.
- trust (module
- Membership (module
seed-membership): the subject of the membership attestation issued by the attestation service of Seedbed (namespacehttps://schema-registry.dataspacelab-demo.org/seed-conformity/).
The Seedbed scenario¶
The examples follow the supplier scenario of the ICAM specification:
| Actor | Identifier | Role |
|---|---|---|
| Seedbed | did:web:seedbed.operator.dataspacelab-demo.org |
operator: issues the supplier Trust Scope and appoints the suppliers |
| BeanLabs | did:web:beanlabs.provider.dataspacelab-demo.org |
supplier (SupplierPartyCredential, projects harvest and roasting) |
| Bloom | did:web:bloom.provider.dataspacelab-demo.org |
subcontractor of BeanLabs (DelegatedSupplierPartyCredential) |
| Drip | did:web:drip.provider.dataspacelab-demo.org |
subcontractor of Bloom, project roasting; its credential carries an ODRL policy restricting further delegation to human-controlled holders |
| Jack | his wallet (did:key:…) |
employee of Drip (EmployeeCredential), delegated by Drip (DelegatedSupplierPartyCredential, controller: Human, not delegatable) |
Writing a credential¶
- The type of the credential is carried by its
credentialSubject; the type of the credential itself staysVerifiableCredential. The shapes apply to the typed node: a type repeated at the level of the credential would make them check the envelope, and fail. - Embedded objects carry their type, for example a
holder:"type": "TrustedDigitalIdentity". The shapes are closed and check the class of each value. - A trusted digital identity is identified by its key, not by the party: in full, its
idis its verification method (publicKeyId); as a reference, itsidis itsTrustedDigitalIdentityCredential, with itsdigestSRI.
{
"@context": [
"https://www.w3.org/ns/credentials/v2",
"https://schema-registry.dataspacelab-demo.org/seed/v1.0/seed.context.jsonld"
],
"type": ["VerifiableCredential"],
"issuer": "did:web:drip.provider.dataspacelab-demo.org",
"validFrom": "2026-11-19T16:00:00Z",
"credentialSubject": {
"type": "DelegatedSupplierPartyCredential",
"id": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK",
"holder": {
"type": "TrustedDigitalIdentity",
"id": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK#z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK",
"controller": "Human",
"level": "Scoped",
"publicKeyId": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK#z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK"
},
"trustScope": "did:web:seedbed.operator.dataspacelab-demo.org:scopes#suppliers",
"delegatable": false,
"identityRoles": ["Reader"],
"projects": ["roasting"],
"parentPartyCredential": "https://bloom.provider.dataspacelab-demo.org/credentials/delegation-drip",
"parentPartyCredentialDigest": "sha384-…"
}
}
The line alias (v1.0) always serves the latest patch of the line; a patch never changes the
meaning of the terms. A credential is a Seed credential only if its Seed context is served by
the schema registry for an official line. Every published version also stays available on the
schema provider, under its exact version (https://schema-provider.dataspacelab-demo.org/seed/v1.0.0/…).
SD-JWT VC¶
Each credential type is also an SD-JWT VC type: its Type Metadata are served at its vct,
https://schema-registry.dataspacelab-demo.org/seed/v1.0/vct/<Class> (for example
…/vct/EmployeeCredential), with the integrity value to put in vct#integrity listed by the
registry (/lines). Personal data (givenName, surname, email, nationality) is always
selectively disclosable; the claims that establish trust or the delegation chain never are.
Identifiers¶
The terms specific to the dataspace, including the ICAM terms, are identified per line of
versions: https://schema-registry.dataspacelab-demo.org/seed/v1.0# for every version 1.0.z.
The Gaia-X terms keep the Gaia-X namespace (https://w3id.org/gaia-x/development#), the
membership terms the namespace of the Seedbed attestation service, ODRL policies the ODRL
namespace, and digestSRI the term of the W3C credentials context.