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
Should we add options to the script to control this? For example:
--resource-url-mas-hash: use <MAS>#_<uuid> for resources (current default)
--resource-urn: use urn:uuid:<uuid> URNs for resources
--resource-url-dash: use dash not hash, and remove parasitic underscore
--resource-url-base: use <base>/<uuid> (explicitly given base instead of MAS) for resources
--model-urn: use urn:uuid:<uuid> for models (current default)
--model-url-mas: use <MAS>/<uuid> URLs for model
--model-url-base: use <base>/<uuid> (explicitly given base instead of MAS) for model
It would enable experimentation with various scenarios, but will hardly promote interoperability. Assigning to Svein to decide, then cancel or reassign to me.
The text was updated successfully, but these errors were encountered:
(More general than #143)
The
cim-trig.pl
script currently does the bare minimum with URIs and emits them as follows:<MAS>#_<uuid>
urn:uuid:<uuid>
But https://github.com/Sveino/Inst4CIM-KG/tree/develop/rdf-improved#cim-uris-and-resolvability describes more considerations. In particular:
Should we add options to the script to control this? For example:
--resource-url-mas-hash
: use<MAS>#_<uuid>
for resources (current default)--resource-urn
: useurn:uuid:<uuid>
URNs for resources--resource-url-dash
: use dash not hash, and remove parasitic underscore--resource-url-base
: use<base>/<uuid>
(explicitly given base instead of MAS) for resources--model-urn
: useurn:uuid:<uuid>
for models (current default)--model-url-mas
: use<MAS>/<uuid>
URLs for model--model-url-base
: use<base>/<uuid>
(explicitly given base instead of MAS) for modelIt would enable experimentation with various scenarios, but will hardly promote interoperability. Assigning to Svein to decide, then cancel or reassign to me.
The text was updated successfully, but these errors were encountered: