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

Mike Beckerle commented on DAFFODIL-2917:
-----------------------------------------

Hmmm. If a path step or any reference to an element name, is unqualified, and 
there is a default namespace defined, then I think that path step is always a 
default namespace reference. I don't know why we would ever interpret that 
situation as noNamespace. 

In order to reference something in noNamespace, you have to use an unqualified 
path step and not have a default namespace. 

So I think there is no need for a tunable, nor property, except... for backward 
compatibility with our current behavior.

Right now an unqualified path step is assumed to be no namespace, regardless of 
whether there is a default namespace defined. I think this is incorrect, but it 
is the default behavior of unprefixedPathStepPolicy tunable. 

 

>  tunable unqualifiedPathStepPolicy seems unnecessary - deprecate it
> -------------------------------------------------------------------
>
>                 Key: DAFFODIL-2917
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2917
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Front End
>    Affects Versions: 3.8.0
>            Reporter: Mike Beckerle
>            Priority: Major
>
> The tunable unqualifiedPathStepPolicy seems unnecessary
> This policy can be based on the elementFormDefault of the lexically enclosing 
> schema where the path appears.
> If the elementFormDefault is unqualified, then a path step with no prefix 
> should be assumed to have no namespace.
> If the elementFormDefault is qualified, then a path step with no prefix 
> should be assumed to be in the default namespace (if defined) and 
> no-namespace if no default namespace is defined.
> These correspond to the unqualifiedPathStepPolicy values of noNamespace, and 
> preferDefaultNamespace respectively.  The default for 
> unqualifiedPathStepPolicy is noNamespace which would correspond to the 
> elementFormDefault default value of "unqualified". 
> The third value of unqualifiedPathStepPolicy, which is "defaultNamespace" is 
> problematic because the schema may have none. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to