[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: About namespaces
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: Nicolas LEHUEN <firstname.lastname@example.org>,"'email@example.com'" <firstname.lastname@example.org>
- Date: Thu, 28 Jun 2001 08:54:18 -0500
I note in my last adventure with the Schema IDE,
it took my namespace references and used them
to create and insert an IMPORT statement. If
I didn't enable that, it took every <xhtml:p>
and converted it to < so it could continue
validating. This disturbed me because I wasn't
expecting it to rewrite a file without telling
me it was doing that, but that is also my
unfamiliarity with the tool. However, is this
the strategy everyone expects because it says
when creating an aggregate schema (in this
case, using XTHML for inline <xsd:documentation>
content, one should have access to the schemas
to be used, and the namespace will be resolved,
so the official namespace may not be the one
to use or a catalog mapping is required.
What is the expected behavior?
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Nicolas LEHUEN [mailto:email@example.com]
As far as I know, there is no standard way of binding a schema to a
namespace without a document. The current approach is generally to bind a
document to a namespace using xmlns attributes AND to a schema using
different techniques (e.g. the DTD DOCTYPE element, attributes in a special
namespace for XDR and the W3C XML Schema).