afs commented on issue #2062: URL: https://github.com/apache/jena/issues/2062#issuecomment-1782870061
Firstly - Jena should change to allow these cases even though the use for Linked Data is not good, especially for UUIDs (IMO). The current IRI code (jena-iri) is somewhat out of date which is why there is [special code in IRIProviderJenaIRI](https://github.com/apache/jena/blob/jena-4.9.0/jena-core/src/main/java/org/apache/jena/irix/IRIProviderJenaIRI.java#L293). There is [newer code in the pipeline](https://github.com/afs/x4ld/tree/main/iri4ld) so the rest of this comment is about finding how to deal with the situation for that new code. May be there should be an informational warning. These already exist e.g. `http://example:80/` is bad practice. I'm still unclear what your usage is - are there ids for a resolution service? another kind of service? or specially the f-component for the client? https://datatracker.ietf.org/doc/html/rfc8141#section-2.3 > However, consistent with the > approach taken in RFC 3986, the behavior of a URN that contains > components that are undefined or meaningless for a particular URN > namespace or resource is not defined. The text above is worrying because other systems may choke on these newer features. Jena is both a consumer and republisher. -- 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]
