W3C home > Mailing lists > Public > xmlschema-dev@w3.org > September 2011

Re: What aspects of a schema depend on the schema that included, imported, or redefined it?

From: Michael Kay <mike@saxonica.com>
Date: Mon, 19 Sep 2011 09:37:24 +0100
Message-ID: <4E76FF44.1040900@saxonica.com>
To: xmlschema-dev@w3.org
On 18/09/2011 17:56, Costello, Roger L. wrote:
> Hi Folks,
>
> Suppose a schema has no targetNamespace. What is the namespace of elements or attributes that are declared in that schema?
>
> As you know, it depends. Due to the Chameleon effect, if a no-targetNamespace schema A is included or redefined by schema B then the namespace depends on B's namespace.
>
> So the "namespace" of a schema is one aspect that depends on including or redefining schemas.
>
> What other aspects are dependent on including or redefining schemas?
>
> Is there any aspect of a schema that is dependent on the schema that imports it?
>
> /Roger
>
>
This is probably not a complete list.

Lax/strict wildcards: when you use <xs:any processContents="strict">, 
this will match any element that has a global declaration in "the 
schema", where the schema includes all components regardless what schema 
document they are defined in.

Substitution groups: when a content model contains <xs:element ref="b">, 
this permits any element in the substitution group of b, which may well 
be an element defined in an importing schema document.

Types derived by extension: when an element is defined by 
<xs:complexType ref="c">, then it also permits types derived by 
extension from c, which may well be defined in an importing schema document.

Michael Kay
Saxonica
Received on Monday, 19 September 2011 08:50:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 19 September 2011 08:50:59 GMT