Support local namespaces

[acka47]

It would be great to just publish a SKOS vocab on GitHub and then be able to have all the functionality in SkoHub without setting up a redirect.

Background

I wanted to publish https://github.com/tawahle/destatis_faecherklassifikation/blob/master/faecherklassifikation.rdf with SkoHub for interested parties to inspect the vocabulary. Everything worked quite well, the classification was shown as expected. However, clicking on a concept made a problem of course, because the concept URIs (namespace https://onto.tib.eu/destf/cs/) do not redirect to SkoHub (in fact, they do not go anywhere).

As I am not in control of the domain and did not want to use another HTTP namespace where I'd have to setup a redirect myself, I tried to use a local namespaces. This did not work, and in fact sometimes even broke the other Skohub-published vocab in the repo:

• @prefix : <#> . did not work and broke https://test.skohub.io/acka47/skos/w3id.org/class/hochschulfaecher/scheme.html (acka47/skos@592f076)
• @prefix : <faecherklassifikation#> . & @prefix : </faecherklassifikation#> . did not break the other vocab but did not work. (acka47/skos@4abe0c6)
• @base </faecherklassifikation/> . same as the previous. (acka47/skos@27a5dfe)
• @base <faecherklassifikation/> . also broke https://test.skohub.io/acka47/skos/w3id.org/class/hochschulfaecher/scheme.html (acka47/skos@f75a835)

[literarymachine]

+1

I had the same issue when publishing https://test.skohub.io/literarymachine/skos/purl.org/dcx/lrmi-vocabs/educationalAudienceRole/

[acka47]

Hmm, but it does work for https://test.skohub.io/literarymachine/skos/purl.org/dcx/lrmi-vocabs/educationalAudienceRole/. What did you do differenly?

[literarymachine]

Hmm, but it does work for https://test.skohub.io/literarymachine/skos/purl.org/dcx/lrmi-vocabs/educationalAudienceRole/. What did you do differenly?

What I meant is that I published it using a purl.org namespace without redirect configuration to skohub. What was different though, is that in my case the tree navigation used relative links. There was a bug preventing this for https URIs which I fixed in 4951621:

https://test.skohub.io/literarymachine/skos/onto.tib.eu/destf/cs/

[acka47]

Ok, this fixes the problem I had. Leaving the issue open nonetheless although the priority is not very high by now.

[sebilasse]

tree navigation used relative links

workaround:
if we publish to github pages we can change pathPrefix in gatsby-config to the name of the repo, example

module.exports = {
  siteMetadata: {
    title: `SkoHub-Vocabs`,
    description: `Static site generator for Simple Knowledge Management Systems (SKOS)`,
    author: `@gatsbyjs`,
  },
  pathPrefix: `/vocab/`,
  ...
}

[sroertgen]

This is possible with #272

You can provide a customDomain in the config file and it will be used to build your vocabulary.

[acka47]

Actually, I am not sure whether this really works. Reopening until I see a running example.

The use case it this:

• I want to publish a vocab on skohub.io, e.g. https://test.skohub.io/acka47/testing-skohub-vocabs/heads/master/w3id.org/kim/hochschulfaechersystematik/scheme.html
• I want to use this namespace in my turtle file: prefix : <#> (or something like @base </>) so that the URI where a concept is published in the end is the same as the one in the turtle.

I tried this at https://github.com/acka47/testing-skohub-vocabs and the build won't work. Did I do something wrong?

[acka47]

The original use case is covered with #271 & skohub-io/skohub-pages#21. Closing this ticket now.