[
https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469519
]
Jukka Zitting commented on JCR-727:
-----------------------------------
> A related question is what our expectation is for JCR implementations. Are
> they
> allowed to reject something that doesn't parse as a URI according to RFC3986?
I don't recall the JCR spec saying anything about this, but since XML namespace
(http://www.w3.org/TR/REC-xml-names/) names are RFC 3986 URIs, I think it would
be perfectly OK for a repository implementatino to only allow valid URIs. One
concrete benefit of such a policy would be the avoidance of invalid namespace
names in XML exports. In fact we may even want to consider enforcing this in
Jackrabbit.
PS. The "www.apache.org/..." name can actually be interpreted as a relative
URI, and is only deprecated but not strictly prohibited by the current XML
namespace spec.
> NamespaceRegistryTest uses an invalid URI as namespace URI
> ----------------------------------------------------------
>
> Key: JCR-727
> URL: https://issues.apache.org/jira/browse/JCR-727
> Project: Jackrabbit
> Issue Type: Bug
> Components: test
> Reporter: Julian Reschke
> Priority: Trivial
>
> The test cases use "www.apache.org/..." as a namespace URI, but this is not a
> URI.
> Suggest to fix by using a proper URI, such as by prefixing with "http://";.
> A related question is what our expectation is for JCR implementations. Are
> they allowed to reject something that doesn't parse as a URI according to
> RFC3986?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
