W3C home > Mailing lists > Public > xmlschema-dev@w3.org > April 2001

Re: Mixing schemaLocation and noNamespaceSchemaLocation?

From: Ian Stokes-Rees <ijs@decisionsoft.com>
Date: Sun, 22 Apr 2001 09:08:15 +0100 (BST)
To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
cc: "Arnold, Curt" <Curt.Arnold@hyprotech.com>, "'xmlschema-dev@w3.org'" <xmlschema-dev@w3.org>
Message-ID: <Pine.LNX.4.21.0104220847510.24815-100000@tugela.dsl.net>
> > Assertion #4: One schema document may define a subset of at most one
> > namespace. (that subset may be the entire namespace, or may be no
> > namespace, in the case of "null namespace" schema documents).
> 
> Yes, although your choice of words is odd.  A schema only addresses
> the syntax of elements and attributes in a namespace, there are lots
> of other things that might be defined about a namespace.

I have been reflecting on this comment with respect to the
"form" attribute.  Is it true that anything with
form="unqualified" (whether from an explicit form attribute or
inherrited from the xxxxxFormDefault attribute on the schema element) is
being defined into the null namespace rather than into the target
namespace of the schema?

If this is the case, then is it correct to say that a single schema
document may define elements and attributes into the null namespace, the
target namespace of the schema document, or both?

Finally, for globally declared elements and attributes there is no concept
of "form" since they can only be defined into the target namespace,
although that target namespace may be the null namespace.  Similarly,
globally declared types and groups can only ever be defined into the
target namespace.

Ian.
Received on Sunday, 22 April 2001 04:09:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:20 GMT