HashURIs have some drawbacks that prohibit SkoHub Vocabs from rendering them in full beauty.
It basically boils down to hashURIs being all in one document, whereas slash URIs can be modularized. Because of the way SkoHub Vocabs makes use of the URIs when rendering vocabularies we would either have to blow up the conceptScheme's JSON document to put all necessary info (all definitions, scope Notes etc) in there or establish a separate build process for hashURIs.
sroertgen
commented
1 year ago
HashURIs have some drawbacks that prohibit SkoHub Vocabs from rendering them in full beauty.
It basically boils down to hashURIs being all in one document, whereas slash URIs can be modularized. Because of the way SkoHub Vocabs makes use of the URIs when rendering vocabularies we would either have to blow up the conceptScheme's JSON document to put all necessary info (all definitions, scope Notes etc) in there or establish a separate build process for hashURIs.
See also here for comparison of hash and slash URIs: https://www.w3.org/wiki/HashVsSlash