Hi Sandor!
Could this be because you have omitted the final slash in the uriSpace
setting? Try setting it to "
http://www.statistik.at/oefos2012/" instead.
> Regarding the URN using for URI instead of an URL (which is a more
> important issue to me) I have tried to write the URN to the namespace in
> the effected vocabulary like that:
> @prefix oefos: <urn:x-vocab:at:oefos:2015/> .
> but after that Skosmos display just the Vocabulary information sheet,
> displaying the Terms count by language, but nothing else.
It's quite likely that Skosmos is checking for URIs that start with
'http' or 'https' in some places in the code. If you want to have URNs
supported, please open an issue on GitHub and provide a full example file.
> If I want to use embedded URN, as you did, what should I do for it?
We are just prefixing the URNs with "
http://urn.fi/", the URL of the URN
resolver operated by the National Library of Finland. We have set up the
resolver to handle URNs like that by redirecting them to Finto using
HTTP content negotiation and the 303 See Other convention.
You can use any kind of HTTP URIs in your data, including embedded URNs
like this, but if you want them to be resolvable, you will need to have
a URN resolver service that understands those identifiers. Plain URNs
are generally not resolvable (there is no single official mechanism to
resolve them, but a number of URN resolvers exist, including our
urn.fi
and the resolver operated by the German national library) so if you use
them in your SKOS data, others will not be able to dereference your
concept identifiers. HTTP URIs are generally preferred in Linked Data
(see Linked Data principle #2: "Use HTTP URIs so that people can look up
those names.").
-Osma