afs commented on issue #1756: URL: https://github.com/apache/jena/issues/1756#issuecomment-1428883535
I see what you want to happen - it's that the RFC that does not support it. `urn:` and `did:` get caught by this as well. Jena isn't making an opinion nor does Jena does implement different URI schemes differently for parsing - it is implementing the grammar and algorithms in the RFC. URI syntax is defined in [Appendix A Collected ABNF for URI](https://www.rfc-editor.org/rfc/rfc3986#appendix-A). > Hierarchy, in the sense of the URI standard, means that parts separated by the general delimiters Sorry - I used "hierarchical URI scheme is old language from RFC 2396 by mistake. One of the parts is "path" and that is further decomposed in [5.2.3 Merge Paths](https://www.rfc-editor.org/rfc/rfc3986#section-5.2.3) - see the second bullet which dropt characters after the last "/". > `[email protected],2023` is not a path, it is an authority name followed by a date. Both mentions of `authority` in the grammar are preceded by "//". After the scheme `tag:`, `[email protected],2023` matches `segment-nz` in `path-rootless`. 'tag://[email protected],2023:' is as below (the ":" is the empty port) because `,` can be part of an authority name via the `reg-name` rule. ``` Scheme|tag| Authority|[email protected],2023:| Host|gmail.com,2023| Port|| Path|| Query|null| Fragment|null| ``` -- 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]
