[
https://issues.apache.org/jira/browse/DAFFODIL-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268683#comment-17268683
]
Mike Beckerle commented on DAFFODIL-2457:
-----------------------------------------
The namespace lookup stuff is quite tricky now, because the namespace context
for shared things can be different.
A shared component may have to assume only the intersection of the namespace
context for all points of use.
Discussion of this is in our design notes here:
https://daffodil.apache.org/dev/design-notes/namespace-binding-minimization/.
> xmlns="" incorrectly introduced due to prefixOrNull
> ---------------------------------------------------
>
> Key: DAFFODIL-2457
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2457
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 3.0.0
> Reporter: Olabusayo Kilo
> Assignee: Olabusayo Kilo
> Priority: Major
>
> When thisElementNamespacePrefix was replaced with prefixOrNull, we lost the
> functionality where namespaces prefixes are looked up. And instead relied
> only on the lexical prefix. There's plenty of times when there is no lexical
> prefix, but there is a namespace associated with the element, thus we can
> attempt to look up a prefix. We need to bring back this functionality, fixing
> the incorrect namespaces and incorrect prefixes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
