[jira] [Comment Edited] (DAFFODIL-2236) Need Negative Test that gets unparser namespace ambiguity error

["John Interrante (Jira)" <ji...@apache.org>]

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

John Interrante edited comment on DAFFODIL-2236 at 2/19/21, 7:27 PM:
---------------------------------------------------------------------

Would qualifying names in JSON elements with namespace URIs or prefixes be worth doing (under the control of a tunable to keep backward compatibility with applications)?  Would that allow a negative test (an element name with more than one possibility that differs only by namespace) to pass instead of failing with an unparser namespace ambiguity error?  In JSON, names are enclosed in double quotes and a name like 
{code:java}
"{http://example.com}num"
{code}
 or 
{code:java}
"ex:num"
{code}
 is valid JSON syntax even if applications were expecting to see only local names like 
{code:java}
"num"
{code}



was (Author: interran):
Would qualifying names in JSON elements with namespace URIs or prefixes be worth doing (under the control of a tunable to keep backward compatibility with applications)?  Would that allow a negative test (an element name with more than one possibility that differs only by namespace) to pass instead of failing with an unparser namespace ambiguity error?  In JSON, names are enclosed in double quotes and a name like "{http://example.com}num" or "ex:num" is valid JSON syntax even if applications were expecting to see only local names like "num". 

> Need Negative Test that gets unparser namespace ambiguity error
> ---------------------------------------------------------------
>
>                 Key: DAFFODIL-2236
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2236
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, QA
>    Affects Versions: 2.4.0
>            Reporter: Mike Beckerle
>            Priority: Minor
>              Labels: beginner
>
> When using JSON, because there are no namespaces there are ambiguous situations where the unparser gets an element name, but it doesn't know what element to synthesize in the infoset because it has more than one possibility that differ only by namespace.
> No test elicits this message.
> The message string (you can search for) is:
> "Found multiple matches for element %s because infoset implementation ignores namespaces"
>  



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