<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://dashes.com/anil/2002/02/weblog-api.html" />
  <link rel="self" type="application/atom+xml" href="http://dashes.com/anil/atom.xml" />
  <id>tag:dashes.com,2009:/anil//1/tag:www.dashes.com,2002:/anil//1.1193-</id>
  <updated></updated>
  <title>Comments for weblog api</title>
  <subtitle>A Blog About Making Culture</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.3-en</generator>
  <entry>
    <id>tag:www.dashes.com,2002:/anil//1.1193</id>
    <link rel="alternate" type="text/html" href="http://dashes.com/anil/2002/02/weblog-api.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://dashes.com/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=1193" title="weblog api" />
    <published>2002-02-26T07:07:34Z</published>
    <updated>2005-08-12T06:49:38Z</updated>
    <title>weblog api</title>
    <summary>Following up on the concept of mindshare and market domination via APIs, I finally found a common XML-RPC API for weblogs, which seems relatively well-designed....</summary>
    <author>
      <name>Anil</name>
      <uri>http://anildash.com/</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://dashes.com/anil/">
      <![CDATA[<p>Following up on the concept of <a href="http://www.dashes.com/anil/index.php?blogarch/2002_01_01_archive.php#9177215">mindshare and market domination via APIs</a>, I finally found a <a href="http://techno-weenie.com/articles/rfc/weblog_api_1.shtml" title="from techno-weenie">common XML-RPC API for weblogs</a>, which seems relatively well-designed. There's also a <a href="http://techno-weenie.com/articles/rfc/weblog_api_2.shtml">completely rearchitected API</a> that's incompatible, which of course I like slightly better. Naturally the existing API doesn't support versioning of the messages being received. I'm of the belief that the API in general would be improved by a tool-neutral name, a higher level of abstraction and extensibility, and a design more informed by some of the concepts (but not necessarily the weighty implementation) of <a href="http://www.webdav.org/" title="Web-based Distributed Authoring and Versioning">WebDAV</a>.</p><p>Show-stopper omissions in the API as proposed are a lack of time-based functions, including get/set post or comment time, and editing or deleting posts/comments by time or date range. This seems to be more fleshed out in the <a href="http://wasabii.org/root/">Wasabii</a> spec. More discussion, as ever, in the relevant <a href="http://groups.yahoo.com/group/weblog-devel">Yahoo Group</a>.</p>]]>
      
    </content>
  </entry>

</feed>
