ericstephan commented on issue #2007:
URL: https://github.com/apache/jena/issues/2007#issuecomment-1708982985

   > Base is not a prefix - it has to be a legal URI and then follows the URI 
resolution rules.
   > 
   > "urn:uuid:" is an illegal URN. Jena checks some URI schemes for the scheme 
specific rules , including urn:uuid
   > 
   > A URN has three parts `urn:NSS:NID`, none of which can be omitted.
   > 
   > The urn:uuid sub-scheme additionally must have a legal UUID string for the 
NID part.
   > 
   > xml:base="urn:uuid:810ee1ae-4cd0-11ee-be3e-5776e9cc7a4e"
   > 
   > however, to use URNs as a base combined with a relative URI is tricky 
because URNs are not hierarchical (no "/" path) or rather the whole of the NID 
is "the path" and resolving base "abc" on "xyz" is "xyz" or in full 
"urn:NSS:abc" on "xyz" is "urn:NSS:xyz"
   > 
   > "abc" on "#xyz" is "abc#xyz"
   > 
   > "urn:uuid:810ee1ae-4cd0-11ee-be3e-5776e9cc7a4e" and "c" is "urn:uuid:c" 
and illegal. (It is appears to be a legacy quirk of the RDF/XML parsing this is 
a ERROR)
   > 
   > Try:
   > 
   > `xml:base="http://example/"`
   > 
   > For use in RDF about:
   > 
   > `rdf:about="urn:uuid:810ee1ae-4cd0-11ee-be3e-5776e9cc7a4e"` should work.
   
   @afs Thank you so much for the clarification.  As unusual as the example I 
provided below appears this does clear any warnings or errors.
   
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; 
xml:base="urn:uuid:810ee1ae-4cd0-11ee-be3e-5776e9cc7a4e">
   <Station rdf:about = "urn:uuid:810ee1ae-4cd0-11ee-be3e-5776e9cc7eee"/>
   </rdf:RDF>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to