Closed mkollenstart closed 10 months ago
blocked by #142
contentwise good and currently no comments, but we have an open issue with the github raw links that need to be resolved first (see #142 )
I've added a commit reverting back to the w3id link for the context references. This will require implementations in the time between having the w3id setup (as discussed in #142) to manually override the context loading of JSON-LD libraries.
This pull request adds an extended JSON-LD context to allow creation of more concise JSON-LD documents while preserving the meaning of the document.
Directives are added (in
/common/schema/context.json
) to:dct:title
dct:issued
,dct:modified
,dct:created
,dcat:byteSize
, anddcat:endpointURL
@id
references fordspace:agreementId
,dspace:dataset
,dspace:transportType
,dspace:state
,dct:publisher
,dct:format
,dct:type
,odrl:assigner
,odrl:assignee
,odrl:action
,odrl:target
,odrl:leftOperand
,odrl:operator
,odrl:rightOperandReference
, andodrl:profile
dspace:reason
,dspace:catalog
,dspace:filter
,dct:description
,dcat:keyword
,dcat:service
,dcat:dataset
,odrl:hasPolicy
,odrl:permission
,odrl:prohibition
,odrl:duty
, andodrl:constraint
Aspect that might need further discussion:
dct:description
) and keywords (dct:keyword
) do not have a default language. Which might give errors in handling those. For example, descriptions in multiple languages can be provided, requiring those to be objects with@language
and@value
properties, while on most scenario's these will be given in english which would allow them to be compacted to plain strings. Having these two options will make (de)serialization more difficult. This could be solved in implementations by using a separate context for compaction that transforms all of these into an object form.dspace:reason
properties are difficult to model in JSON-LD in the current form, as these are free-form types. Which results in the fact that those are not well suitable for JSON-LD processing.The
@context
references tohttps://w3id.org/dspace/v0.8/context.json
are replaced byhttps://raw.githubusercontent.com/International-Data-Spaces-Association/ids-specification/main/common/schema/context.json
to allow JSON-LD algorithms to resolve the context (after this pull request has been merged). This is done for all references to this context, so also in the figures and schemas. This should be reverted to a stable link in the future.Closes #132 Closes #125