Information missing in vocabs with hash URIs

[acka47]

Originates from #120 (comment)

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. acka47/nwbib-spatial@00703e0 & 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]

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

Currently it is:

• id
• notation
• prefLabel
• altLabel
• narrower

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]

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]

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]

Do we want to close this then in favor of #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