- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Mon, 18 Apr 2005 12:45:17 -0400
- To: public-xml-core-wg@w3.org
- Cc: Rich Salz <rsalz@datapower.com>
- Message-id: <878y3ghw4i.fsf@nwalsh.com>
/ Rich Salz <rsalz@datapower.com> was heard to say: [...] | 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. I'm really confused. Do you want to standardize the format of "out of band knowledge"? If not, then what sort of general purpose validator could you write? It seems to me that you'd just have some application constraints. If you do want to standardize it, what format do you have in mind? Here's an XML document: <para partno="3fourfive"/> Is that document valid? How can you tell? If you know that partno is supposed to be a NAME, you know its invalid, but how did you know that? Be seeing you, norm -- Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc. NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Received on Monday, 18 April 2005 16:45:12 UTC