- From: Rich Salz <rsalz@datapower.com>
- Date: Wed, 13 Apr 2005 23:49:20 -0400 (EDT)
- To: Paul Grosso <pgrosso@arbortext.com>
- cc: "public-xml-core-wg@w3.org" <public-xml-core-wg@w3.org>
John, I know about the "#define prefix" hack, but for me the killer
is not that it prevents prefix re-use, but that it prevents default
prefix re-use, which I think is much more common.
> > With xml:id, your application can enforce ID uniqueness constraints
> > independent of validation.
But that uniqueness is only for all xml:id attributes, not for all
ID attributes, right? (Since you only get the "all" with a DTD. Or
is xml:id somehow grandfathered into XML Schema?)
> > What does validity mean separate from DTDs? Do you only mean enforcing
> > ID uniqueness constraints, or do you have more in mind?
I didn't do a full analysis, but a quick skim through the 3rd ed
shows that many validity constraints are independant of a DTD.
Some of the validity constraints are constraints on the DTD:
Unique Element Type Declaration
No Duplicate Types
ID Attribute Default
Unique Notation Name
and some are constraints on the "XML document" itself:
Element Valid
Attribute Value Type
One ID per Element
Name token
Enumeration
Required attribute
Fixed Attribute Default
If my document is fully defined by schema, our *out of band
knowledge* then there is no reason why these constriants require
a DTD.
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
Received on Thursday, 14 April 2005 03:49:23 UTC