[ 
https://issues.apache.org/jira/browse/DAFFODIL-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413322#comment-17413322
 ] 

Mike Beckerle commented on DAFFODIL-2550:
-----------------------------------------

Sounds like this is the same issue as DAFFODIL-2282, and your well-figured-out 
example that reproduces this issue should inform that bug, and this can be 
closed as a duplicate of that. 

The problem here is the whole use of headOption.

That's assuming right off that it can get away with figuring this out from only 
one enclosing element, but it has to take all enclosing contexts into 
consideration.

Also giving an SDE when this problem is detected, and forcing the user to 
revise namespace usage to avoid the problem would be perfectly fine. We don't 
have to actually be able to fix and tolerate this situation. We could just SDE 
when we detect the issue.

Forcing a user to add a namespace prefix rather than being able to use the 
default namespace (or no namespace) in a new schema they are authoring is 
perfectly acceptable. What we don't want to do is force them to modify a schema 
they are trying to reuse. 

 

> xmlns="" not minimized away in two CLI tests.
> ---------------------------------------------
>
>                 Key: DAFFODIL-2550
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2550
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Middle "End"
>    Affects Versions: 3.2.0
>            Reporter: Mike Beckerle
>            Assignee: Steve Lawrence
>            Priority: Major
>
> Changes in [https://github.com/apache/daffodil/pull/600] clean up things a 
> lot, but there is one mystery change in behavior.
> Two CLI tests now add an xmlns="" to an inner locally-declared element which 
> has a unqualified name. 
> This seems like incorrect namespace binding minimization, possibly. 
> Rather than hold up the merge of PR 600 (which is a big change set, so needs 
> to be merged real soon now) this ticket is to investigate this issue of the 
> two CLI tests and the xmlns="" that seems unnecessary. 
> Note that we've suspected there could be bugs in namespace binding 
> minimization for a while now. 
> The two CLI tests are:
> * test_CLI_Debugger_InfoHidden_1
> * test_CLI_Debugger_InfoHidden_2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to