[
https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473543
]
Jukka Zitting commented on JCR-727:
-----------------------------------
Thanks for the terminology update! The devil's in the details...
The XML namespace spec says: "An XML namespace is identified by a URI reference
[RFC3986]", meaning both full URIs and relative URI references. The current
version adds a note that deprecates the use of relative URI references.
The JCR spec somewhat vaguely says: "Namespacing in a content repository is
patterned after namespacing in XML. As in XML, the prefix is actually shorthand
for the full namespace, which is a URI."
It seems fair to interpret this as meaning that only full URIs are allowed as
JCR namespaces.
> 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.
