Open tpluscode opened 3 years ago
Hey @lanthaler. Have you had a chance to look at the above?
I can set it up but would advice against it and instead just create a single namespace for extensions. It quickly becomes very hard to remember which term is in which namespace and would be overly confusing if the same term is used in different namespaces with different meanings... yes, I do regret having created a separate core
namespace ;-)
I am also looking at w3id.org which may be better suited so that we don't have to rely on w3.org setup which is out of our control.
About you suggestion to have a single NS, that would in fact be similar to how DASH (datashapes.org) which is spread over multiple specs but all of the vocabulary is a single RDF document
https://w3id.org/hydra-ex#
perhaps for the vocab? And https://w3id.org/hydra-ex/shacl
for the documents
@alien-mcl @pietercolpaert
I’m ok with that!
I think w3id is OK for extensions
As for the Url, I'd like to have it readable in the url, i.e. https://w3id.org/hydra/extension/in-owl
or https://w3id.org/hydra/extension/in-shacl
or https://w3id.org/hydra/extension/shacl
(making it readable as hydra extension in owl, hydra extension in shacl or hydra extension shacl).
Alternatively with hash notation, i.e. https://w3id.org/hydra#in-owl
Ok, I think we're getting somewhere.
To wrap up, I propose as follows:
https://w3id.org/hydra/extension/shacl
as a canonical link (redirect) to the SHACL extension spechttps://w3id.org/hydra/extension
negotiated redirect to either
/hydra/in-owl
or /hydra/is-shacl
which may not make sense to combine with the "Extension Vocabulary" itself.I noticed that https://w3id.org/hydra/
is already a thing. @lanthaler would you like to keep it redirecting to your page or maybe rewire it to redirect to the core spec?
The Hydra Core vocabulary has the namespace
http://www.w3.org/ns/hydra/core#
I would propose to have analogous structure for each extensions, so that the
core
segments is replaced with a specific name:The repository would thus follow this analogous structure, with each extension at least having a readme (until we decide to adopt respec/bikeshed/other for publishing) and a turtle with actual vocabulary
@lanthaler would it be possible to set up publishing the URLs above from this repo, so that we get content negotiation of the RDF. How is that done for the core?