- From: Norman Walsh <ndw@nwalsh.com>
- Date: Sat, 18 Feb 2012 13:05:00 -0500
- To: W3C XML-ER Community Group <public-xml-er@w3.org>
Received on Saturday, 18 February 2012 18:05:29 UTC
Anne van Kesteren <annevk@opera.com> writes: > processors in our browser, for instance. Or in other words, the code > should be like this > > parseXML(input) > > and not > > if(!parseXML(input)) > parseXMLER(input) Yes, absolutely. All I meant was that I think we should be looking at this as a parsing algorithm that does the right thing with WF XML and also does the right thing with some inputs that aren't WF XML. That we say, for example, that an unmatched close tag is ignored (if that's what we say), doesn't mean that we have to assert this as correction of some specific WF error. If that makes sense, which maybe it doesn't. Be seeing you, norm -- Norman Walsh Lead Engineer MarkLogic Corporation Phone: +1 413 624 6676 www.marklogic.com
Received on Saturday, 18 February 2012 18:05:29 UTC