You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ontology things are still work in progress (read: are somewhat a mess) but just for reference here:
Currently it is possible to download the v0 of the DraCor ontology at https://dracor.org/ontology. To make this system more useful and adhere to LOD principles, there should be a way to have URIs for classes and properties that are dereferencable.
There are probably two options:
easier, but uglier: use Hash-URIs for concepts, e.g. https://dracor.org/ontology.rdf#play_name then a HTTP request (not requesting RDF maybe) should display the ontology (as RDF)? A browser might point a user to the right place in the RDF file, maybe.
better integrated option: Use RestXQ and have a resolver at .../ontology/ and evaluate an URL parameter .../ontology/{local-id}, e.g. https://dracor.org/ontology/play_name. This would allow to do proper content negotiation, i.e. return RDF in different serializations (optional); provide a human readable view of a class or a property. This is more work but could maybe lead to better results.
The text was updated successfully, but these errors were encountered:
The ontology things are still work in progress (read: are somewhat a mess) but just for reference here:
Currently it is possible to download the v0 of the DraCor ontology at https://dracor.org/ontology. To make this system more useful and adhere to LOD principles, there should be a way to have URIs for classes and properties that are dereferencable.
There are probably two options:
The text was updated successfully, but these errors were encountered: