-
Notifications
You must be signed in to change notification settings - Fork 8
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
Modules namespace, slash vs hash #56
Comments
I am pro making the user only remember one prefix as much as possible, but also make each modules accessible independently, so option 3 feels most future-proof (modules can be versioned independently and also still used separately in different contexts). |
Agreed. Note that with option 3, using a single namespace, IRI dereferencing of the ontology(s) using a hash strategy does not afford the ability to distinguish modules. With hash you could only ever serve a single document per namespace. |
As agreed on the Community Group's meeting, we propose to go for option 3 (hybrid) to maintain the same namespace for all concepts but keeping differenciated the modules; and with slash, since with hash it would not be possible to split the modules in different files. If you agree please let us know reacting to this message with 👍 ; else with 👎 -- and explain further why not in a comment below :) |
We have an agreement around slash vs hash for all ontologies. Closing. |
Regarding the decision of which namespace should we use for the RML ontologies (core + modules), there are three options, and they also influence the use of hash or slash:
The text was updated successfully, but these errors were encountered: