-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Corentin spotted some issues with tests 3, 11, and 31; their behavior is confusing.
There are two issues at play here. One (and this is true for most test cases) the baseIRI (either attached to the triples map, or given to the engine as a parameter) is not specified. From tests 11 and 31, one could think that the base IRI of the mapping is http://, but that should be specified. This explains why:
- for 11,
VENUSis not an absolute IRI and the engine tests whetherhttp://+VENUSis an absolute IRI - for 31,
WWW.EXAMPLE.COMis not an absolute IRI and the engine tests whetherhttp://+WWW.EXAMPLE.COMis an absolute IRI
A second issue is that the function toUpperCaseURL has no specification. How is it different from toUpperCase? It is not related to yielding an error if no valid URL is passed, because that would have then failed on VENUS and WWW.EXAMPLE.COM. And, if people are not careful, they might think that the function prepends http:// in lowercase if it is missing.
Proposed solutions:
- Make base IRIs explicit in the mapping.
http://for minimal changes, ideally something better. - Provide a specification of
toUpperCaseURL(in the README of the test case) OR use a different function.