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

Re: Namespaces vs XML doc and template XML doc

From: Bob Schloss <rschloss@us.ibm.com>
Date: Wed, 22 Aug 2001 13:01:13 -0400
To: Daniel Flippance <DFlippance@mpsbc.com>, "'xmlschema-dev@w3.org'" <xmlschema-dev@w3.org>
Message-ID: <OFC3132B8A.13C6D4A9-ON85256AB0.005D4058@pok.ibm.com>

     Your operating system shell may be set so that "double clicking"
launches a particular program based on extension.  If so, I would
understand your motivation. Maybe the shell designers could give a
short-term fix in which foo.xxd launches one thing, but foo.xxt.xxd
launches another program.

     My colleagues and I are currently writing some tools to handle XML
Schemas and I am going out of my way to not depend on anything about the
filename or URI.  If I need to know what something contains, our code looks
in the document and finds the document element
tag-name and (if present) namespace URI and based on that, decides whether
it is of the "type" this tool can read or not.

     I am looking ahead to future W3C recommendations (potentially XForms,
XHTML, etc.) or other initiatives (like WSDL) in which one might nest an
XML element and its children from one namespace as the content of elements
from the namespace which the document element used.  I would like to make
it so that tools which accept the inner vocabulary can process it, even
when it is imbedded inside something else.  I think
that conventions based on XPath or XLink or XPointer will evolve, so that
where-ever one can pass a "simple file name" or a "simple URI" one can
augment it with the path.  As far as I know, the current invocation APIs
for things like DOM and SAX don't let the parser do this work of getting
the inner stuff for you; you have to do it yourself.  This is more complex
than it sounds because the inner stuff might be using a namespace prefix
was declared on outer containing elements, (which you need to understand)
or it might not.


IBM Thomas J. Watson Research Center - Next Gen Web group
Yorktown Heights, New York, USA

Daniel Flippance <DFlippance@mpsbc.com>@w3.org on 07/26/2001 08:39:57 PM

Sent by:  xmlschema-dev-request@w3.org

To:   "'xmlschema-dev@w3.org'" <xmlschema-dev@w3.org>
Subject:  Namespaces vs XML doc and template XML doc

I have an XML document (eg: MyDoc.xxd) and a related schema.
I want to create a template for this type of document (eg: MyTemplate.xxt)
which uses the same schema.

<blah xmlns="http://MyURI/xx">...</blah <http://MyURI/xx>>

<blah xmlns="http://MyURI/xx">...</blah <http://MyURI/xx>>

ie: they are identical (MyDoc.xxd was created by copying MyTempalte.xxt and

I am looking for opinions on whether it is good practise to have different
file types (extensions) which use the same namespace and schema.

Are they any precedents for this kind of use? (Other than .htm, .html)
Received on Wednesday, 22 August 2001 13:02:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:52 UTC