JSON-LD Contexts¶

JSON-LD contexts map short property names in credential JSON to full IRIs, enabling semantic interoperability. The SimpulseID context is generated from LinkML schemas and composed with upstream contexts.

Context Composition¶

Every SimpulseID credential uses a stack of four contexts:

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://w3id.org/gaia-x/development#",
    "https://w3id.org/reachhaven/harbour/core/v1/",
    "https://w3id.org/reachhaven/harbour/gx/v1/",
    "https://w3id.org/ascs-ev/simpulse-id/v1/"
  ]
}

Context	Purpose
W3C VCDM v2	Base credential vocabulary (`issuer`, `validFrom`, `credentialSubject`, etc.)
Gaia-X	Gaia-X 25.11 compliance terms (`gx:LegalPerson`, `gx:registrationNumber`, etc.)
Harbour	Credential envelope terms (`HarbourCredential`, `CRSetEntry`, `evidence`, etc.)
SimpulseID	Domain-specific terms (`Participant`, `legalForm`, `duns`, etc.)

Contexts are processed in order — later contexts can override earlier ones. The SimpulseID context is always last, so its @vocab acts as the default namespace for any terms not defined by upstream contexts.

Generated Context¶

The SimpulseID context is generated from linkml/simpulseid-core.yaml and written to artifacts/simpulseid-core/simpulseid-core.context.jsonld.

Default Namespace¶

"@vocab": "https://w3id.org/ascs-ev/simpulse-id/v1/"

Any bare term not explicitly mapped (e.g., duns, hash) resolves to the SimpulseID namespace.

Prefix Definitions¶

Prefix	IRI	Usage
`simpulseid`	`https://w3id.org/ascs-ev/simpulse-id/v1/`	Domain types and slots
`harbour`	`https://w3id.org/reachhaven/harbour/core/v1/`	Harbour base types
`harbour.gx`	`https://w3id.org/reachhaven/harbour/gx/v1/`	Harbour Gaia-X credential types
`gx`	`https://w3id.org/gaia-x/development#`	Gaia-X Trust Framework types
`sdo`	`http://schema.org/`	Schema.org terms (note: `http` not `https`)
`cred`	`https://www.w3.org/2018/credentials#`	W3C credentials vocabulary
`xsd`	`http://www.w3.org/2001/XMLSchema#`	XML Schema datatypes

Schema.org Namespace

The generated SimpulseID and harbour contexts consistently use the https://schema.org/ namespace and expose it under the sdo: prefix. This avoids collisions with LinkML's built-in schema: prefix, which still points to http://schema.org/ in some imported material.

Term Mappings¶

String Properties¶

JSON Term	Maps To
`name`	`sdo:name`
`givenName`	`sdo:givenName`
`familyName`	`sdo:familyName`
`email`	`sdo:email`
`programName`	`sdo:programName`
`duns`	`simpulseid:duns` (via `@vocab`)

URI Properties¶

These are typed as xsd:anyURI:

JSON Term	Maps To
`harbourCredential`	`simpulseid:harbourCredential`
`baseMembershipCredential`	`simpulseid:baseMembershipCredential`
`member`	`sdo:member`
`memberOf`	`sdo:memberOf`
`hostingOrganization`	`sdo:hostingOrganization`
`url`	`sdo:url`

Date Properties¶

JSON Term	Maps To	Datatype
`memberSince`	`schema:memberSince`	`xsd:date`
`validFrom`	`cred:validFrom`	`xsd:dateTime`
`validUntil`	`cred:validUntil`	`xsd:dateTime`

Type Alias¶

"type": "@type"

This alias is added by the generator as a post-processing step because LinkML cannot emit it without declaring a type slot that would conflict with the W3C VCDM v2 context's @protected definition.

Regenerating¶

The context is regenerated with:

make generate

The generator (src/generate_artifacts.py) uses linkml.generators.jsonldcontextgen.ContextGenerator and applies a post-processing step to add the "type": "@type" alias.