On 06/01/2025 19:14, zPlus wrote:
But we need one form for URI matching otherwise "file:/path" does not
match "file:///path"
Why does Jena need to match "file:/path" and "file:///path"? Shouldn't it be
left to the user to choose one form or the other in their data?
There is no "right" answer for file: URLs.
Having one normalized form means the same name is for data producer
(load database) and data consumer (SPARQL query) whether they write it
file:/ or file:/// or a mixture; or when multiple sources of data are
combined. And across operating systems.
There isn't "the user".
https://datatracker.ietf.org/doc/html/rfc8089.html#appendix-B
"""
o A traditional file URI for a local file with an empty authority.
This is the most common format in use today. For example:
* "file:///path/to/file"
"""
And on Windows ...
C:/path is the "C:" URI scheme.
file:C:/path is going to be interpreted different on Windows and linux/Mac.
The whole thing is messy.
Andy
