Publishing the ontology to a persistent URL

[calummackervoy]

Hello!

I notice that the interoperability vocabulary is currently published here: https://solid.github.io/data-interoperability-panel/specification/interop.ttl

based on the (WIP) Inrupt vocabulary guidelines (https://github.com/inrupt/public-documentation/pull/10/files) and the other solid vocabularies I think that it will probably end up being published to a http://www.w3.org/ domain ?

[ericprud]

If we want to make this change, it's probably less of a burden to do this sooner than later (less code will point to the scratch location). We'll probably want to keep iterating <https://solid.github.io/data-interoperability-panel/specification/interop.ttl> while we refine the spec and get implementations. The hard part is figuring out the namespace (@timbl).

http://www.w3.org/ns/solid/ has a couple permanent redirects (301): app.ttl -> https://solid.github.io/vocab/solid-app.ttl (source) terms.ttl -> https://solid.github.io/vocab/solid-terms.ttl (source)

As a strawman, I've added another: interop.ttl -> https://solid.github.io/data-interoperability-panel/specification/interop.ttl (source)

If we decide we like this namespace (<http://www.w3.org/ns/solid/interop>), we should:

1. migrate any code that uses the github.io address to point to w3.org/ns .
2. add a BASE directive to make it so it defines only one set of URLs (i.e. parsing it won't emit github.io URLs).
3. root around in other solid repos for related issues.

[csarven]

Solid process for vocabulary management: https://github.com/solid/process/#vocabulary-management

I agree on iterating at the current interop.ttl location until a change is necessary. The specs that are using the vocabs needs to be part of the ecosystem ie. PR against solid/specification. After the review process, interop.ttl can be PR'd to solid/vocab and managed from there.