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
On 30/04/2019 6:57 am, Semantics Matter wrote:
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
--
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 [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
