Altova Mailing List Archives>Archive Index >comp.text.xml Archive Home >Recent entries >Thread Prev - Re: If DTD is unspecifed XML should not parse >Thread Next - Re: If DTD is unspecifed XML should not parse Re: If DTD is unspecifed XML should not parseTo: NULL Date: 8/3/2007 8:48:00 PM > The word "valid" is used in various ways, but the XML spec use it to > mean valid with respect to the DTD referred to in the document. If it > doesn't refer to a DTD, it's invalid. There are arguably multiple states: Not validated (well-formed only, not tested), invalid (DTD validation attempted and failed), valid (DTD validation attempted and succeeded), schema-invalid and schema-valid. (The latter two are distinguished only in the Post-Schema-Validation infoset, not in the basic infoset.) As far as I can tell, the basic XML Infoset doesn't actually included any indication of these states as part of its information content. There are pieces of information which are only available when a document is valid, or when it was at least processed with a validating parser, but that's the closest I can find. Apparently detecting validation success or failure was left to whatever mechanism you use to invoke the parser and/or validator. -- () ASCII Ribbon Campaign | Joe Kesselman /\ Stamp out HTML e-mail! | System architexture and kinetic poetry | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
