Ad-hoc terms use DefinedTerm/Class/Property #232
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://schema.org/DefinedTerm is better than http://schema.org/Thing for pre-existing URIs that are semantic artefacts or concepts. Somewhat equivalent to skos:Concept. This will then be consistent with https://www.researchobject.org/ro-crate/1.2-DRAFT/profiles that also mentions http://schema.org/DefinedTermSet.
For simplification with the profiles,
rdf:Property
/rdfs:Class
types now optional, so we can stay in schema.org land for lightweight properties using their equivalent http://schema.org/Property and http://schema.org/Class. The RDFS variants are needed to dordfs:subPropertyOf
orrdfs:subClassOf
but not I think needed for just adding a few terms to JSON-LD.The part about
@context
and ad-hoc terms will still need to be updated to show that a RO-Crate Profile Crate could be used directly as a@context
to use its terms there.Also fixed some bugs in the expanded RDFS code from #208 (as
@id
is needed for object references in our JSON-LD).