- From: Rich Salz <rsalz@datapower.com>
- Date: Sat, 23 Apr 2005 09:18:31 -0400 (EDT)
- To: Richard Tobin <richard@inf.ed.ac.uk>
- cc: "public-xml-core-wg@w3.org" <public-xml-core-wg@w3.org>
> So what we need to know now is what you mean by "valid", that isn't
> "conforms to the DTD". You've mentioned ID uniqueness, but is that
> it?
Well, I really meant all of validity. If you remove DTD's then some of
the validity constraints become not relevant, but you don't have to remove
them since there's never any way to not meet them.
I initially mentioned ID uniqueness for a couple of reasons:
1. it's the constraint I am most interested in (as is the
entire Web Services community :),
2. it already has a non-DTD technology (schema) that starts to
address the issue
3. It seemed the simplest to understand and talk about
I was trying to use a simple example to focus discussion, not to dominate
and become the discussion. Sorry if I never made things clear enough.
Look at
http://lists.w3.org/Archives/Public/public-xml-core-wg/2005Apr/0033.html
for a rough list.
> Can you rephrase your question without using the word valid?
How about this -- a concrete change request.
Replace the definition of validity at
http://www.w3.org/TR/2004/REC-xml-20040204/#dt-valid
with this:
[Definition: An XML document is *valid* if the document complies with
the constraints expressed here. If the document has a DTD associated
with it, a validating XML processor would report no constraint
violations.]
/r$
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
Received on Saturday, 23 April 2005 13:18:40 UTC