<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>DOM Scripting comments: XHR on W3C</title>
        <link>http://domscripting.com/blog/display/60</link>
        <description>The XMLHttpRequest object is on its way to become a standard.</description>
        <language>en</language>
        <item>
            <title>Jeremy Keith</title>
            <link>http://domscripting.com/blog/display.php/60#comment317</link>
            <content:encoded><![CDATA[<p>Personally, I never use the term Ajax as an acronym (note the lower-case spelling). It’s a very, very useful term, but quite an inaccurate acronym. AJAX the acronym (Asynchronous JavaScript and XML) doesn’t accurately describe Ajax the methodology.</p>

<p>XMLHttpRequest, on the other hand, is a perfectly valid technical term but it&#8217;s a bit long-winded. Hence my use of the abbreviation XHR in the title.</p>

<p>You&#8217;re right about the acronyms PHP and URL. Here&#8217;s another one: RSS.</p>
]]></content:encoded>
            <pubDate>Wed, 12 Apr 2006 21:41:21 GMT</pubDate>
        </item>
        <item>
            <title>mindmaker</title>
            <link>http://domscripting.com/blog/display.php/60#comment304</link>
            <content:encoded><![CDATA[<p>All these acronyms are so confusing. Ajax apparently means Asynchronous JavaScript and XML. PHP used to mean Personal Home Page, but then it got redefined. There ought to be some Naming Standards, so that acronyms like URL mean one thing and one thing only &#8212; either Uniform or Universal Resource Locator, but not both simultaneously.</p>
]]></content:encoded>
            <pubDate>Wed, 12 Apr 2006 10:57:57 GMT</pubDate>
        </item>
   </channel>
</rss>