svandenhoek commented on issue #2062:
URL: https://github.com/apache/jena/issues/2062#issuecomment-1781920916

   Hello @afs,
   
   Thank you for the fast response!
   
   The source file is an internally generated one (which I was using in GraphDB 
and didn’t have any issues with). The main reason I ran it through riot was due 
to a different external file causing issues with loading into GraphDB and I 
ended up validating all Turtle files I needed to load.
   
   The URN specification does seem to state the following:
   [RFC 8141 Section 
2.3](https://datatracker.ietf.org/doc/html/rfc8141#section-2.3):
   
   > This specification includes three optional components in the URN syntax.  
They are known as r-component, q-component, and f-component [...] each of these 
components has a distinct role that is independent of any given URN and its URN 
namespace. It is intended that clients will be able to handle these components 
uniformly for all URNs. These components MAY be used with URNs from existing 
URN namespaces, whether or not a URN namespace explicitly supports them.
   
   [RFC 8141 Section 
2.2](https://datatracker.ietf.org/doc/html/rfc8141#section-2.2):
   
   > The NSS is a string, unique within a URN namespace, that is assigned and 
managed in a consistent way and that conforms to the definition of the relevant 
URN namespace.
   
   [Section 2](https://datatracker.ietf.org/doc/html/rfc8141#section-2):
   
   > Rules not defined here (specifically: alphanum, fragment, and pchar) are 
defined as part of the URI syntax 
[[RFC3986](https://datatracker.ietf.org/doc/html/rfc3986)]
   
   While indeed [RFC 4122](https://datatracker.ietf.org/doc/html/rfc4122) does 
not allow them, my assumption would be that [RFC 
4122](https://datatracker.ietf.org/doc/html/rfc4122) (and others) simply 
describe what is allowed in the “Namespace Specific String” for that specific 
"Namespace Identifier". The f-component would therefore be out-of-scope for 
[RFC 4122](https://datatracker.ietf.org/doc/html/rfc4122) and is defined in 
[RFC 8141](https://datatracker.ietf.org/doc/html/rfc8141) (which refers to [RFC 
3986](https://datatracker.ietf.org/doc/html/rfc3986) for the f-component).
   
   
   
   


-- 
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