use slash not hash

[VladimirAlexiev]

@nissimsan Related to #531, #734:

I think the current choice of delimiter is hash. However, that is not appropriate for large semantic collections like traceability: slash is better.

To give an example from #577:
<https://w3id.org/traceability#TransportMode-Air>

A client sends to the server only the part before the hash i.e. <https://w3id.org/traceability>.
So the server should collect and send data about ALL of traceability, all its modules, lookup lists, etc.
I think that's too much data: we had a similar discussion re UNCEFACT LOD.

So a better choice of delimiter is slash, and the URL above would look like this:
<https://w3id.org/traceability/TransportMode/Air>
This follows good practices from the Data Patterns book:

• hierarchical, eg lookup values are in a "folder" below the respective enumeration
• hackable, i.e. given https://w3id.org/traceability/TransportMode/Air one can explore https://w3id.org/traceability/TransportMode and get reasonable data.

[BenjaminMoe]

Is this a pattern that should be applied globally to https://w3c-ccg.github.io/traceability-vocab/contexts/traceability-v1.jsonld? Such as https://w3id.org/traceability#SIMASteelImportLicense to https://w3id.org/traceability/SIMASteelImportLicense? Is this a copy and replace that should applied to all instances or only some of them?

[VladimirAlexiev]

@BenjaminMoe Yes!

[TallTed]

@VladimirAlexiev — There were three questions in the last comment from @BenjaminMoe, to which comment you have posted a single answer, which I think could reasonably be applied to the first two questions (as they are "yes-or-no" questions) but does not satisfactorily answer the "either/or" of the third question. Would you please clarify to which question(s) your "Yes!" answer applies, and/or provide a clear answer that maps to each question?

[VladimirAlexiev]

Yes. Yes. Yes.

@BenjaminMoe the last question is a bit ambiguous:

copy and replace that should applied to all instances

I think you mean here "all Traceability ontology terms (classes and props)".
Instance URLs are the responsibility of Traceability users (and by the same token, they should use slash not hash).