[
https://issues.apache.org/jira/browse/JCRVLT-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515555#comment-16515555
]
Julian Reschke edited comment on JCRVLT-303 at 6/18/18 10:15 AM:
-----------------------------------------------------------------
IMHO: calling this situation a "namespace conflict" is misleading. The only
only only semantically relevant part is the namespace URI. Period.
Rewriting namespace prefixes when they already exist in the system and map to a
different namespace URI absolutely is the right thing to do.
was (Author: reschke):
IMHO: calling this situation a "namespace conflict" is misleading. The only
only only semantically part is the namespace URI. Period.
Rewriting namespace prefixes when they already exist in the system and map to a
different namespace URI absolutely is the right thing to do.
> Register namespace under a unique prefix in case of clash
> ---------------------------------------------------------
>
> Key: JCRVLT-303
> URL: https://issues.apache.org/jira/browse/JCRVLT-303
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging, vlt
> Affects Versions: 3.1.44
> Reporter: Timothee Maret
> Priority: Major
>
> With AEM DAM system, some parts of XMP metadata are backed by JCR namespaces.
> An asset may contain metadata which namespace conflicts with already
> registered JCR namespace.
> Those conflict prevent content packages to be imported, which is a functional
> issue for DAM system aiming at ingesting any asset.
> This issue is about mitigating namespace conflicts, by generating new
> namespaces when they occur.
> Assuming a namespace with prefix {{N1}} and URI {{U1}} is already registered.
> When importing a content package containing a conflicting namespace with
> prefix {{N1}} and URI {{U2}}, instead of failing, we would import the content
> with a new namespace prefix {{N1_1}} and URI {{U2}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
