search

skohub-io / skohub-vocabs

A lightweight tool to publish SKOS Vocabularies
https://skohub.io/
Apache License 2.0
34 stars 25 forks source link

Information missing in vocabs with hash URIs #122

Closed acka47 closed 1 year ago

acka47 commented 3 years ago

Originates from https://github.com/skohub-io/skohub-vocabs/pull/120#issuecomment-765678384

As only the ConceptScheme JSON is built in case of a hash URI vocab and only few fields are considered there (id, notation, prefLabel, narrower), information like broader, related or altLabel is missing (see e.g. https://github.com/acka47/nwbib-spatial/commit/00703e03d78eb0cfd3a0c3d398459b448bd37fe1 & https://test.skohub.io/acka47/nwbib-spatial/heads/master/nwbib.de/spatial.json).

We should think about how to add this to the ConceptScheme JSON of a hash URI vocab without blowing up the ConceptSchem JSON of a slash URI (where all the Concept information can be found at the repective URI for the Concept).

sroertgen commented 1 year ago

@acka47 Which kind of information do you think should be given for Hash URI concepts?

Currently it is:

Should it be totally the same as for hashURIs? Then we have to do quite some changes in the build process I think. But should be possible.

acka47 commented 1 year ago

Should it be totally the same as for hashURIs?

This was the general approach, yes.. But I think it is ok to prioritize this low as we apparently don't have people using SkoHub Vocabs with Hash URIs. We might as well think about requiring the use slash URIs...

sroertgen commented 1 year ago

Do we want to close this then in favor of #236 ? We could add a note in the README that if somebody has the requirement for hash URIs, you should open a ticket?

acka47 commented 1 year ago

Do we want to close this then in favor of https://github.com/skohub-io/skohub-vocabs/issues/236 ?

+1

We could add a note in the README that if somebody has the requirement for hash URIs, you should open a ticket?

+1