W3C home > Mailing lists > Public > public-webapi@w3.org > June 2007

[XHR] responseXML interfaces

From: Alexey Proskuryakov <ap-carbon@rambler.ru>
Date: Wed, 27 Jun 2007 16:51:25 +0400
To: "Web API WG (public)" <public-webapi@w3.org>
Message-ID: <C2A8460D.3978A%ap-carbon@rambler.ru>


  The current draft specifies the following algorithm for parsing response

3. Parse the response entity body following the rules from the XML
specifications. Let the result be parsed document. If this fails
(unsupported character encoding, namespace well-formedness error et cetera)
terminate these steps return null. [XML] [XMLNS]

4. Return an object implementing the Document interface representing the
parsed document.

  Is it intentional that other interfaces are not mentioned at all? Some
browsers create objects implementing HTMLDocument interface, and it is not
entirely obvious how this should be done.

  Even for plain XML documents, following rules from XML specifications may
not be straightforward, for example, some people are surprised that XSL
transformations are not appiled to responseXML.

  If it is not currently feasible to fully specify the behavior, perhaps a
note mentioning that could be added at least.

- WBR, Alexey Proskuryakov
Received on Wednesday, 27 June 2007 12:51:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:23 UTC