- From: David Carlisle <davidc@nag.co.uk>
- Date: Fri, 02 Mar 2012 11:38:41 +0000
- To: Anne van Kesteren <annevk@opera.com>
- Cc: "public-xml-er@w3.org Community Group" <public-xml-er@w3.org>
On 02/03/2012 11:29, Anne van Kesteren wrote: > > Is that really a hard requirement? Well we should decide if it is or not:-) I think it should be. The use case I have personally for xml-er is to put at the start of an xml pipeline so that the data can be processed with xml tools. If the tree has elements in it that don't correspond to xml names, it can't be traversed with xpath or xquery, can't be validated with XSD or Relax Ng, basically it can't be used in any way at all by any XML tools that I have to hand. If the output of xml-er is not guaranteed to be equivalent to the XML parse of some tree, then it can't be dropped in as an alternative parser, there would always have to be a check-if-wellformed-and-fixup stage on the _output_ of xml-er. If you are having to check and apply ad-hoc fix up the output from xml-er then it is hardly meeting its main use case as a standardised xml parser with standardised recovery. David ________________________________________________________________________ The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________
Received on Friday, 2 March 2012 11:39:06 UTC