XSchema Spec, Section 3, Draft 1 (Namespaces)

james anderson James.Anderson at mecom.mixx.de
Tue Jun 30 13:57:19 BST 1998


greetings,

i've been following this thread somewhat haphazardly, reading the sections as
they flew by, but only if i had the time. please excuse the question if it's
already been addressed and please point me at the approximate date so i can
pull the answer out of the hyperarchive.

that said, of the remarks and specifications which i've observed regarding
namespaces and schemas, the only two which i would have understood to be
pertinent are:
1.  the standard elects, for expository purposes, the prefix "XSC" for the
namespace identified as "http://www.purl.org/NET/XSchema/v1"
2. a conforming v1 xschema processor is free to ignore all elements for which
the gi's are not in this namespace.

everything else is the responsibility of the parser. what place does it have
in a schema spec?

Simon St.Laurent wrote:
> 
> Section 3 of the XSchema Specification follows.  Note that there are a
> considerable number of questions raised.  One guy with a whiteboard can only
> make so many connections.
> 

> 3.1 The XSchema Namespace
 
yes, (see above)

> 3.2 Interaction with Other Namespaces

why is this needed?
the processor will sit on top of a parser which supports namespace pi's.
if w^3 removes the src attribute, then perhaps.
better would be a parallel mechanism (another pi) since that will be required
anyway by a processor (non-xschema) which wishes to validate the document
against its schema/dtd

> 3.3 Note Regarding Namespace Usage

is all a matter for the parser, not the processor.

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)




More information about the Xml-dev mailing list