Limited support for IRI in visualization graphs

[pulquero]

This function

graphdb-workbench/src/js/angular/graphexplore/controllers/graphs-visualizations.controller.js

Line 754 in da05b3d

function expandPrefix(str, namespaces) {

supports only http and urn IRIs. Could it not also treat any string enclosed in <, > as an absolute IRI as well? https should also be added to the regex (ideally all well-known protocols too).

[AtesComp]

This seems to be an inherited problem throughout the workbench. For instance, I can import RDF files containing base IRI and IRI references to IRI containing unregistered scheme (or unregistered URN) and even query using the unregistered IRI. If I use Setup -> Namespaces, I can see the unregistered namespaces (examples: xyz://abc#, abc:xyz:mno) but I cannot change it or add new IRI namespaces that do not conform to some registered scheme (http, ftp, etc.). NOTE: It does not recognize the registered "mailto:" scheme either. In visual graph, neither the "Easy graph" or "Advance graph configurations" accepts these IRIs but complains with an "Invalid URI" message (they also annoyingly insist on converting namespace IDs to full IRI text). All of this is a major show stopper.

I don't see why the workbench should check for registered IRI scheme conformance...just check general IRI conformance. Some datasets are purpose build not to conform with registered IRI scheme, reserving that feature to "rdfs:seeAlso" references and similar. Why redundantly use "http://" on every resource when that string space can compact namespaces?

The specifications for IRI (https://tools.ietf.org/html/rfc3987) and URI (https://tools.ietf.org/html/rfc3986) do not necessitate conformance to some registered scheme. Only that when such a scheme is registered, it specifies that the scheme may further restrict the IRI format.

How would the workbench know if a scheme is registered or not? Why would it need to know?