See also: API Draft

Discuss any changes or extensions for the API. Sketch out recommendations or examples. You can see the Editing Help page for information on using mediawiki syntax or embedded code snippets. Here's an XML example:

<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>W3C News</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/" />
    <link rel="self" type="application/atom+xml" href="http://www.w3.org/News/atom.xml" />
    <id>tag:www.w3.org,2008-09-29://4</id>
    <updated>2010-04-13T15:23:57Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.261</generator>

<entry>
    <title>Widget Updates Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8765" />
    <id>tag:www.w3.org,2010://4.8765</id>

    <published>2010-04-13T15:23:26Z</published>
    <updated>2010-04-13T15:23:26Z</updated>

    <summary>The Web Applications Working Group has published a Working Draft of Widget Updates. This specification defines a process and a document format to allow a user agent to update an installed widget package with different version of a widget package....</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />

    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2008/webapps/">Web Applications Working Group</a> has published a Working Draft of <a href="/TR/2010/WD-widgets-updates-20100413/">Widget Updates</a>. This specification defines a process and a document format to allow a user agent to update an installed widget package with different version of a widget package. A widget cannot update itself; instead, a widget relies on the user agent to manage the update process. A user agent can perform an update over HTTP and from non-HTTP sources (e.g., directly from a device's memory card or hard disk). Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>
</feed>

RPC vs Rest

I think you should point out that you are using RPC here. As clearly some things like CREATE on GET violate the rest architecture. Drozzy 16:01, 17 April 2010 (UTC)