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

Re: Chameleon schemas <include>ing chameleon schemas

• To: Paul Spencer <ps@b...>
• Subject: Re: Chameleon schemas <include>ing chameleon schemas
• From: "Chiusano Joseph" <chiusano_joseph@b...>
• Date: Tue, 01 Jul 2003 07:09:20 -0400
• Cc: xml-dev@l...
• Organization: BAH
• References: <lif2gvgaissoqvpp2l36ftbfbasm7e307r@4...>

<Quote>
At least two suppliers of XML tools have different interpretations of
this. My solution is therefore to avoid the problem by making target
namespaces explicit,
</Quote>

This is an oft-misinterpreted aspect of W3C Schema. Because of that, it
may be best to make target namespaces explicit as you mention above,
especially so that XML artifacts are not inadvertently included in a
given namespace. Of course, there are advantages to the chameleon
approach if you intend that behavior to occur (that XML artifacts are
automatically assigned to the target namespace of the including schema)
- but if not, I find it's best to always specify a targetNamespace.

Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton

Paul Spencer wrote:
> 
> I frequently come across the case where a schema document with no
> targetNamespace attribute (call this one simpleTypes.xsd) is
> <include>d in another schema document with no targetNamespace
> attribute (say, contactTypes.xsd), which is, in turn, <include>d in a
> schema document with a targetNamespace attribute (say, main.xsd having
> a targetNamespace attribute value of "apd"). (I am using "apd" as a
> URI here to save typing.)
> 
> Clearly, any data type defined in contactTypes.xsd will exist in the
> "apd" namespace. What about data types defined in simpleTypes.xsd? Do
> they exist in the "apd" namespace, or do they have no target
> namespace?
> 
> At least two suppliers of XML tools have different interpretations of
> this. My solution is therefore to avoid the problem by making target
> namespaces explicit, but my enquiring mind would love a definitive
> statement on which interpretation is correct. Perhaps the tool vendors
> will then take note.
> 
> I hope this is clear. I have examples if anyone wants them.
> 
> Regards
> 
> Paul Spencer
> 
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> 
> The list archives are at http://lists.xml.org/archives/xml-dev/
> 
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>

begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@b...
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard

• References:
  • Chameleon schemas <include>ing chameleon schemas
    • From: Paul Spencer <ps@b...>

• Prev by Date: RE: Chameleon schemas <include>ing chameleon schemas
• Next by Date: Re: Attributes in XML
• Previous by thread: Chameleon schemas <include>ing chameleon schemas
• Next by thread: XSLT vs. CSS (Re: Indexing)
• Index(es):
  • Date
  • Thread