[XMLSCHEMA-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: xs:include changing targetNamespace

From: Michael Kay <mike@saxonica.com>
Date: Tue, 5 Oct 2004 15:09:20 +0100
To: "'Michael Kay'" <mhk@mhk.me.uk>, "'Henry S. Thompson'" <ht@inf.ed.ac.uk>
Cc: <xmlschema-dev@w3.org>
Message-Id: <E1CEq0K-0003dH-00@ukmail1.eechost.net>
xs include support for .net

> 
> 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
Received on Tuesday, 5 October 2004 14:09:25 GMT

Subscribe to the Stylus Scoop newsletter for helpful XML tips and tutorials.
Email
First Name
Last Name
Company

Download Stylus Studio 6 XML Enterprise Edition

Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.