Open mchlrch opened 5 years ago
Extracted the tooltip part to its own separate issue #24
The problem with rdf-vocabularies
is that the package is already quite big and will only ever grow.
I think this issue will benefit greatly from individual ontology packages (re https://github.com/zazuko/rdf-vocabularies/issues/118). Obviously though, these packages would have to be loaded on demand. Alternatively, XRM can fetch the n-quads from GitHub
For example, having typed
# no braces!
vocabulary schema
Would the proceed to fetch schema.nq
from the web (or local cache)
This method could also allow ad-hoc vocabularies, like
vocabulary ex {
prefix "example" "http://example.com/"
# allow new property with the URL to fetch
source "http://example.com/ontology.xml"
}
By the way, why the cli
label?
Support ontologies from rdf-vocabularies out-of-the-box.
One approach to get this working is to build up the object-model for the vocabularies and then serializing [1] the object-model to rdf-mapping (.xrm) files. The serialized files should end up a in a dedicated project rdf-mapping-dsl-vocabularies publicly shared on github. Mapping users then can clone that project and add it as a dependency to their mapping project.
This approach doesn't require deep integration and no service calls are required at mapping-time. Mapping users can also easily curate their own set of vocabularies, by copy/pasting vocabularies to their own project. It would also allow us to deal with incompatible grammar versions if needed, by having a branch per major version in rdf-mapping-dsl-vocabularies.
1: https://mleduc.xyz/xtext/emf/2018/02/28/xtext-serialization.html