Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: xs:include changing targetNamespace

From: "Michael Kay" <mike@--------.--->
To: "'Michael Kay'" <mhk@---.--.-->, "'Henry S. Thompson'" <ht@---.--.--.-->
Date: 10/5/2004 4:09:00 PM
> 
> In a schema with no target namespace and no default 
> namespace, the schema
> component created by a local element declaration <xs:element 
> name="A"/> is
> identical whether form is qualified or unqualified. The rules 
> suggest that I
> need to distinguish the two cases, yet the schema components are
> indistinguishable.
> 

To follow up on this, running the test attgD035 in the Microsoft part of the
test suite, this contains an attribute declaration

<xsd:attribute name="att" type="xsd:int" fixed="37"/>

and MSXML, XSV, and Xerces are uniformly interpreting this as being an
attribute in no namespace, not an attribute in the target namespace of the
including schema document. But if you add form="qualified" to the attribute
declaration, they are interpreting it as being in the target namespace of
the including schema. Therefore, this appears to be an operation that does
not work solely on the schema components, it relies on the original XML
representation.

Now to discover how they handle ref="" attributes. Empiricism rules.

Michael Kay


From mhk@m... Tue Oct 05 22:31:20 2004
Received: from li


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent