All URIs are beautiful, it's just that some of them cause problems in VB

[Joeli Takala]

Hi,

Sometimes I run into problems where valid but slightly unusual URIs are not parsed completely by different LOD software. Today my issue has been with URN references wrapped in URL in VB+SemanticTurkey+GraphDB. If that sounds strange, referencable URNs were supposed to be a thing in the Internet using a resolver layer caller URC that would work like a DNS, in a way, but this was dropped (by accident?) when they were building the damn thing. So we have a work-around for the missing URC by using a national URN resolver that understands URIs like:

http://urn.fi/URN:NBN:fi:au:mts:m4958

And this is in line with the 2005 spec for URIs, see examples in 1.1.2 https://www.rfc-editor.org/rfc/rfc3986.txt (Or just paste the URI in a validator, like https://0mg.github.io/tools/uri/ )

But then the problems start. If I set up a vocabulary project with http://urn.fi/URN:NBN:fi:au:mts: as the base URI, VB will save it in project.info as:
 - Base URI http://urn.fi/URN:NBN:fi:au:mts:
- Default namespace http://urn.fi/URN:NBN:fi:au:mts:#

- VB GUI will show concept namespace/local name for the concept view as http://urn.fi/ | URN:NBN:fi:au:mts:m4958

So it's inconsistent but at least one out of three was correct. The more worrying issue is with GraphDB lucene plugin failing to parse these URIs. I have observed quite a few entries in the GraphDB error.log like this:
Failed executing lucene query 'http://urn.fi/URN:NBN:fi:au:mts:m4958' on index 'vocbenchLabel' org.apache.lucene.queryParser.ParseException: Cannot parse 'http://urn.fi/URN:NBN:fi:au:mts:m4958': Encountered " ":" ": "" at line 1, column 17.

Out of the three problems, the failure of the Lucene plugin to parse these URIs seems pretty severe. Is it possible for me to disable the plugin in a VB project like this (so that the plugin is still in use with other vocabulary projects in the same VB instance)? Any tips?

_______
Joeli