Skip to content

DataService.servesDataset is not in the JSON-LD context, so it produces no triples #277

Description

@SimonStier

Bug Report

Describe the Bug

Type: normative

servesDataset is defined in the JSON Schema but has no term in either shipped context, so it is dropped on JSON-LD expansion.

Expected Behavior

A property the schema defines maps to dcat:servesDataset and appears in the expanded graph.

Observed Behavior

artifacts/src/main/resources/catalog/dataset-schema.json defines it on DataService:

"servesDataset": { "type": "array", "items": { "$ref": "#/definitions/Dataset" }, "minItems": 1 }

The term is absent from context/dspace.jsonld, from context/odrl.jsonld, and from the published context at https://w3id.org/dspace/2025/1/context.jsonld. A schema-valid catalogue that populates it expands to no triple for it, silently.

Writing dcat:servesDataset does produce the triple, since the dcat prefix is defined, but that spelling is not the one the schema constrains, and no schema in the repository sets additionalProperties or unevaluatedProperties, so both spellings validate.

Possible Implementation

"servesDataset": { "@id": "dcat:servesDataset", "@type": "@id", "@container": "@set" }

Activity

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