[
Lists Home |
Date Index |
Thread Index
]
Michael Champion wrote:
> Well, they do say right up front: "VTD-XML is a non-validating,
> 'non-extractive" XML processing software API implementing Virtual
> Token Descriptor. Currently it only supports built-in entity
> references(" &s; ' > <).' Arguably an XML
> processing API doesn't have to be a real XML parser *if* the subset it
> supports is clearly stated. I would have to agree that in principle
> "XML" should be used to refer only to the full spec, but that battle
> was lost years ago -- SOAP implicitly subsets XML, RSS is often not
> well-formed (and thus not "XML"), but this distinction is lost on the
> vast majority of XML technology users who do not subscribe to xml-dev.
Which is why it's absolutely critical that those of us who do hang out
on xml-dev, and do know all the nooks and crannies of the various specs,
do not mislead and bamboozle the general populace about what is and is
not XML. In particular, tool vendors have a responsibility to the
community to ensure that their tools handle XML strictly according to
spec because tool users rely on this. People use tools so they don't
have to know every last detail of the relevant specs. If the tools start
lying to them, then where they can turn? A few will become experts
themselves and stop using unreliable tools. Most will sadly remain mired
in misunderstanding and confusion, not knowing which tool to trust. Some
will accept vendor lockin to their tool of choice. Others will ditch XML
completely.
--
Elliotte Rusty Harold elharo@metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim
|
