[
https://issues.apache.org/jira/browse/DAFFODIL-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Beckerle updated DAFFODIL-2282:
------------------------------------
Description:
Namespace bindings aren't properly computed.
Currently the schema compiler computes them, which assumes that they don't need
to change based on nesting of elements.
Now since DAFFODIL-1444 was fixed, we share more elements, and so the namespace
bindings for an element added as a child can vary depending on which parent
element it is added under.
Now this problem doesn't seem to affect current schemas nor tests. So it's
possible this issue can have a test created to illustrate it, and then be
parked for the future. But just fixing it is preferable.
See design note:
https://daffodil.apache.org/dev/design-notes/namespace-binding-minimization/
was:
Namespace bindings aren't properly computed.
Currently the schema compiler computes them, which assumes that they don't need
to change based on nesting of elements.
Now since DAFFODIL-1444 was fixed, we share more elements, and so the namespace
bindings for an element added as a child can vary depending on which parent
element it is added under.
Now this problem doesn't seem to affect current schemas nor tests. So it's
possible this issue can have a test created to illustrate it, and then be
parked for the future. But just fixing it is preferable.
> namesspace bindings not-properly minimized
> ------------------------------------------
>
> Key: DAFFODIL-2282
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2282
> Project: Daffodil
> Issue Type: Bug
> Components: Back End, Front End
> Affects Versions: 2.5.0
> Reporter: Mike Beckerle
> Priority: Major
> Fix For: 3.0.0
>
>
> Namespace bindings aren't properly computed.
> Currently the schema compiler computes them, which assumes that they don't
> need to change based on nesting of elements.
> Now since DAFFODIL-1444 was fixed, we share more elements, and so the
> namespace bindings for an element added as a child can vary depending on
> which parent element it is added under.
> Now this problem doesn't seem to affect current schemas nor tests. So it's
> possible this issue can have a test created to illustrate it, and then be
> parked for the future. But just fixing it is preferable.
> See design note:
> https://daffodil.apache.org/dev/design-notes/namespace-binding-minimization/
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
