- From: Steve K Speicher <sspeiche@us.ibm.com>
- Date: Tue, 25 Sep 2007 05:29:47 -0400
- To: public-webapi@w3.org
- Cc: " CDF WG" <member-cdf@w3.org>
These comments are regarding the 18-June-2007 XMLHttpRequest WD [1] and a bit delayed but hopefully still useful. 1) #conformance for "Comforming user agent", it states: "If the user agent does not support XML (including support for namespaces) the XML response entity body must (always) be null." Is this stating that a server responding to an XMLHttpRequest load or such, must know if the user agent supports XML (including support for namespaces) and respond with null or is it up to the conforming user agent to decide if it supports XML and whether to always sets the response to null? 2) #dependencies for "DOM", "Window", "HTTP": I find the phrasing of: "must support some version of DOM Events and DOM Core " to be very confusing. Then there is a reference (normative?) to DOM3 Core and Events. So the "some version" really DOM Level 3 or is DOM Level 0 ok, as it is *some verson* of DOM? This wording exists for: DOM, Window, HTTP which seems a bit vague. I'd suggest that it clearly define a minimum level to support: say DOM Level 3 Core, etc. 3) #terminology In what context is this matching scheme used or needed? This section seems to discuss string casing and equivalency of characters in ASCII only charsets, it seems that is should consider matching defined by some internationalized context [2] 4) #xmlhttprequest This section uses terms such as "successfully invoked" and "user agent successfully acknowledged the request", though was unable to find definitions of how success was defined. Thanks, Steve Speicher [1] http://www.w3.org/TR/2007/WD-XMLHttpRequest-20070618/ [2] http://www.w3.org/TR/charmod-norm/#sec-IdentityMatching
Received on Tuesday, 25 September 2007 09:30:05 UTC