-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to clarify what should be in profile crate for additional terms #258
Comments
The reason for adding The move to then use schema.org's types In FAIR-IMPACT we have proposed to evolve the RO-Crate Profile to also work for any Semantic Artefact gathering - in which case it would IMHO stay in soft schema.org land because the artefacts would be fully defined in various ontology languages (e.g. SKOS, OWL2) and imposing So are you @ptsefton then proposing to change/remove the new text in https://www.researchobject.org/ro-crate/1.2-DRAFT/appendix/jsonld.html#add-local-definitions-of-ad-hoc-terms (which suggests |
@stain -- I'm not suggesting anything, still trying to get my head around this issue. At the moment we recommend additional Classes and Properties are use /rdfs?/ prefix and this is coded into the Javascript library and used for looking up term definitions when they are present in the crate.. We are also maintaining a schema (vocabulary) for a major project using the Schema.org Style Schema method (SOSS) where the terms are I understand the idea of |
Then I think some middle ground is to encourage again use of Then we can keep using schema.org's informal (I think I'll add to our profile docs that you use the inverse This would however not permit your tooling to know how to apply these new terms, as it would not know if they are classes, properties or something else -- without parsing its defining ontology which we know from OWL imports can be a massive minefield can of worms, and can be using a myriad of different ontology standards and formats (and defining those explicitly is what I would want to add in the FAIR-IMPACT Semantic Artefact Crate). This was my reasoning for adding lightweight With the loosening in #260 to no longer require to have a known schema.org type, so we can have just BTW, the rdfs namespace is sadly also without a human-readable variant, so http://www.w3.org/2000/01/rdf-schema#Class just gives a Turtle file -- should therefore define these in the Crate profile in which case they would have to be declared as schema.org |
Follow generally Crate-O's mode file to do Schema.org-style schemas:
Avoid too many types. |
This is now implemented in #262 etc. as part of the revamp on Profiles. |
Describe the bug
The profile crate does not work the way I was expecting (may not be a bug, but I want to clarify this)
in the crate-focus section additional schema.org vocab used the Schema.org convention of using rdfs:Class (rather than schema:Class) .
In the profile @stain you have done a few things I was not expecting:
URL
Profile RO-Crate Metadata Document
Suggested fix
I would suggest that:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: