[
https://issues.apache.org/jira/browse/JCR-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-5140:
--------------------------------
Description:
There are a few use cases where a new namespace prefix needs to be computed for
a given namespace name (this list may not be exhaustive):
- when mapping expanded names to JCR names when the namespace name (URI) is not
known in the repository (yet)
- when importing content where namespace names (URIs) are known, but no prefixes
- when registering a new namespace, but the specified prefix is already in use
Automatically generating the prefixes has several commons problems:
- consistency: generating prefixes in different places and/or based on previous
state of the registry (incrementing counters until new prefix found) causes
prefix inconsistency across systems for no good reason
- conciseness: for certain namespaces, there are commonly used prefixes (such
as in DC, XMPP etc), and it would be good to just use those when possible
was:
There are a few use cases where a new namespace prefix needs to be computed for
a given namespace name (list may not be exhaustive):
- when mapping expanded names to JCR names when the namespace name (URI) is not
known in the repository (yet)
- when importing content where namespace names (URIs) are known, but no prefixes
- when registering a new namespace, but the specified prefix is already in use
Automatically generating the prefixes has several commons problems:
- consistency: generating prefixes in different places and/or based on previous
state of the registry (incrementing counters until new prefix found) causes
prefix inconsistency across systems for no good reason
- conciseness: for certain namespaces, there are commonly used prefixes (such
as in DC, XMPP etc), and it would be good to just use those when possible
> Improve support for generating namespace prefixes
> -------------------------------------------------
>
> Key: JCR-5140
> URL: https://issues.apache.org/jira/browse/JCR-5140
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr-commons
> Reporter: Julian Reschke
> Priority: Major
>
> There are a few use cases where a new namespace prefix needs to be computed
> for a given namespace name (this list may not be exhaustive):
> - when mapping expanded names to JCR names when the namespace name (URI) is
> not known in the repository (yet)
> - when importing content where namespace names (URIs) are known, but no
> prefixes
> - when registering a new namespace, but the specified prefix is already in use
> Automatically generating the prefixes has several commons problems:
> - consistency: generating prefixes in different places and/or based on
> previous state of the registry (incrementing counters until new prefix found)
> causes prefix inconsistency across systems for no good reason
> - conciseness: for certain namespaces, there are commonly used prefixes (such
> as in DC, XMPP etc), and it would be good to just use those when possible
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
