[ 
https://issues.apache.org/jira/browse/XERCESJ-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Glavassevich resolved XERCESJ-1474.
-------------------------------------------

    Resolution: Invalid

The conclusions you are drawing are incorrect.  Please review the section of 
the schema specification on attribute default values [1].  Only a [local name] 
and [namespace name] are contributed to the PSVI.  There is no prefix.  XML 
Infosets can be constructed in other ways than by parsing (see synthetic 
infosets [2]) and may not be consistent with those that were constructed 
directly from an XML document.  Your application should be relying on the 
namespace name not the prefix.

[1] http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.html#d0e8328
[2] http://www.w3.org/TR/xml-infoset/#intro.synthetic

> Defaulted attributes with attributeForm="qualified"
> ---------------------------------------------------
>
>                 Key: XERCESJ-1474
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1474
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: SAX, XML Schema 1.0 Structures
>    Affects Versions: 2.10.0
>            Reporter: Thomas Mäsing
>            Assignee: Michael Glavassevich
>            Priority: Critical
>         Attachments: dc.xsd, rdf.xsd, schedul.xsd, test.XML, test_new.XML, 
> xlink.xsd
>
>
> Dear Sirs,
> I have attached an example using the xlink namespace (xlink.xsd). There are 
> some defaulted attributes. These are reported without a namespace prefix 
> although the
> XML Schema declares attributeForm"qaulified". To check the namespace 
> awareness I added on of this attributes with a prefix to source document.
> Best regards
> Thomas Mäsing

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to