Is there a case requirement for URIs in EDG?

[Semantics Matter]

Hi,

Since upgrading to V6.1, we are getting an invalid URI error in EDG if we use mixed case in the default URI. Is that a feature or a bug?

Thanks

[Holger Knublauch]

Yes, we had to change the algorithm behind the SPARQL function spif:isValidURI because it was (until 6.1) allowing some invalid URIs that were causing problems down the road. The newer algorithm is based on Jena's IRIResolver.parseIRIex. According to the https://www.ietf.org/rfc/rfc3986.txt spec, the host part of a URI is case-insensitive, which means that http://Aldi.de and http://aldi.de would map to the same address. The RFC therefore strongly recommends to only user lowercase characters in that part except for character escaping. Note this only affects the host part, i.e. between http:// and the first /

Is there a strong need on your end to continue with uppercase host addresses?

Holger

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Semantics Matter]

No, just need to rename some models. Thanks for confirming.

You received this message because you are subscribed to a topic in the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/topbraid-users/5Z_9yXuS8Ao/unsubscribe.
To unsubscribe from this group and all its topics, send an email to topbraid-user...@googlegroups.com.