The XMLHttpRequest Object comments

http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/Overview.html?content-type=text/html;%20charset=utf-8

== 1.2 Conformance ==

[[
XML

    Implementations should support some version of XML. If they don't
support some version of XML responseXML must always be null. [XML]
[XMLNS]
]]

Does it mean a conformant implementation could support NO version of XML ?

The version implied by the text is the version of XML. So "1.0" and
"1.1". There must be a reference to XML 1.1 specification in that
respect

What is not clear is about support XML 1.0 or XML 1.0 with Namespaces
: what is the expected behavior if the filename send is
[[
<?xml version="1.0"?>
<::/>
]]
which is a valid XML 1.0 file but not a valid XML 1.0 with Namespaces ?

Please clarify the behaviour regarding this

== 1.2.2. Terminology ==
[[
There is a case-insensitive match of strings a and b if after
lowercasing both strings (by mapping A-Z to a-z) they are identical.
]]

I would prefer to read

[[
There is a case-insensitive match of strings s1 and s2 if after
upercasing both strings (by mapping a-z to A-Z) they are identical.
]]
s1 and s2 because there is less confusion with letter a and b
uppercasing because it is used latter in the spec for method


==References==
[[
[RFC2617]
    HTTP Authentication: Basic and Digest Access Authentication, ...
]]
should be
[[
[RFC2617]
    HTTP Authentication: Basic and Digest Access Authentication, P.
Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. Luotonen, L.
Stewart, editors. IETF,
June 1999
]]

Warning for next step : Reference to "Window Object" and "Document
Object Model (DOM) Level 3 Events Specification" are Working Draft

==Typo==
s/reqeust/request/
s/resonse/response/

Mohamed Zergaoui
-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €

Received on Monday, 7 May 2007 15:06:10 UTC