Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: xs:include changing targetNamespace

From: "Michael Kay" <mhk@---.--.-->
To: "'Henry S. Thompson'" <ht@---.--.--.-->
Date: 10/5/2004 12:33:00 PM
>  1) The <xs:element ref="A"/> and the declaration of A are in the
>     <include>d schema document.  In that case, the reference has been
>     resolved during the construction of "the .schema components. of
>     I", and clause 3.2.1 will change the TNS of A, a top-level
>     component, to the <includ>ing TNS.

OK, that seems consistent with the spec: though it seems to rely on a model
of the sequence of events by which names are resolved "as early as possible"
which isn't explicit in the spec.

This approach of creating components and then modifying the components
appears to have some problems implicit in phrases such as "where the absent
target namespace name would have appeared", and "whose [form] was
qualified": it seems to require that information is retained in the schema
component about its history, beyond the information that's explicitly part
of the component.

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.

Similarly the phrase "Where the absent target namespace name would have
appeared" seems to suggest that I should distinguish ##targetNamespace and
##local in a wildcard: in the case of ##targetNamespace, the target
namespace "would have appeared" if there had been one, in the case of
##local, it would not. But again, the schema components don't retain this
history.

Presumably though, the absent namespace is not replaced by the new target
namespace in places where the target namespace would never have appeared,
for example in QName-valued enumeration facets and fixed/default values. But
what about Notation-valued enumeration facets? These can be regarded as
references to schema components, so presumably they are renamed.

I seem to be inventing the rules as I go along... Help!

Michael Kay
http://www.saxonica.com/


From mike@s... Tue Oct 05 14:09:25 2004
Received: from lisa.w3.o


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