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/4/2007 12:36:00 PM In article <OL-dnZy_z9FdUS7bnZ2dnUVZ_tmhnZ2d@c...>, Joe Kesselman <keshlam-nospam@c...> wrote: >There are arguably multiple states: Not validated (well-formed only, not >tested), invalid (DTD validation attempted and failed), valid (DTD >validation attempted and succeeded), True, but the XML spec says that validating parsers must report violations of validity constraints, and a document without a DTD will violate at least one. >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. Yes, the Infoset doesn't address validity except in the cases where invalidity prevents an item from having a value (notably the [references] property of attributes). >Apparently detecting validation success >or failure was left to whatever mechanism you use to invoke the parser >and/or validator. All that's required is there must be such a mechanism for a validating parser. -- Richard -- "Consideration shall be given to the need for as many as 32 characters in some alphabets" - X3.4, 1963. | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
