<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <author>
    <name>danm</name>
    <uri>http://www.freebase.com:80/view/user/danm</uri>
  </author>
    <generator uri="http://www.freebase.com/">Freebase Atom Feed Generator</generator>
    <id>http://www.freebase.com:80/view/internet/api</id>
    <link rel="self" href="http://www.freebase.com:80/feed/discuss/all/internet/api"/>
    <title>API</title>
    <updated>2008-08-21T16:01:30Z</updated>
  <entry>
    <author>
    <name>alexbl</name>
    <uri>http://www.freebase.com:80/view/user/alexbl</uri>
  </author>
    <content type="html">&lt;p&gt;&lt;p&gt;The properties presented by this schema don't seem to reflect an API as much as a Web API.&lt;/p&gt;&lt;p&gt;In particular, the Site property isn't appropriate for a normal API. One could rename the site property provided_by, or one could rename this type.&lt;/p&gt;&lt;p&gt;&amp;nbsp;Protocol is also problematic for a normal API, since it tends to suggest some method of transport used (XML, JSON, etc).&amp;nbsp; &lt;/p&gt;&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f80000000086426fe</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f80000000086426fe" title="API: API is-a Web API"/>
    <summary type="html">The properties presented by this schema don't seem to reflect an API as much as a Web API. In...</summary>
    <title>API: API is-a Web API</title>
    <updated>2008-06-14T20:36:40.0012Z</updated>
  </entry><entry>
    <author>
    <name>skud</name>
    <uri>http://www.freebase.com:80/view/user/skud</uri>
  </author>
    <content type="html">&lt;p&gt;Interesting that you should ask.&amp;nbsp; I'm working on some &lt;a href="/view/domain/user/skud/metaweb_api_docs"&gt;Metaweb API documentation&lt;/a&gt; which you can see in my private area which is quite similar to this, and Nick Thompson (nix) was working on something that he hoped would be a generalised kind of API doc schema -- see his &lt;a href="/view/user/nix/apiary"&gt;apiary&lt;/a&gt; domain.&amp;nbsp; So yeah, I reckon it could be useful to do what you suggest.&amp;nbsp; Perhaps work up some examples of what you're thinking of, so we can check it out?&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006f49a83</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006f49a83" title="Python: Common Python idioms and basic programs?"/>
    <summary type="html">Interesting that you should ask.&amp;nbsp; I'm working on some Metaweb API documentation which you can...</summary>
    <title>Python: Common Python idioms and basic programs?</title>
    <updated>2008-01-17T01:23:25.0000Z</updated>
  </entry><entry>
    <author>
    <name>hammer</name>
    <uri>http://www.freebase.com:80/view/user/hammer</uri>
  </author>
    <content type="html">&lt;p&gt;Hey, would it be useful to put common python idioms and some simple example programs somewhere?&amp;nbsp; If so, where is the right place?&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006f2c2d3</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000006f2c2d3" title="Python: Common Python idioms and basic programs?"/>
    <summary type="html">Hey, would it be useful to put common python idioms and some simple example programs somewhere?...</summary>
    <title>Python: Common Python idioms and basic programs?</title>
    <updated>2008-01-15T22:29:01.0034Z</updated>
  </entry><entry>
    <author>
    <name>jeffwheeler</name>
    <uri>http://www.freebase.com:80/view/user/jeffwheeler</uri>
  </author>
    <content type="html">&lt;p&gt;I'm not sure the best way to do this, but I feel that the previously listed XML, PHP, and JS &amp;#8220;protocols&amp;#8221; were incorrect, as none of these are protocols. They do not define the method by which the data is transferred, as a protocol must; instead, they are the formatting for the data itself. Obviously, here HTTP is used as the protocol, although I do not think this is the intended meaning of the Protocol field (as almost all APIs are over HTTP).
&lt;br /&gt;
&lt;br /&gt;
Perhaps the field needs to be renamed Data Transfer Types?
&lt;/p&gt;</content>
    <id>http://www.freebase.com:80/view/guid/9202a8c04000641f8000000005453fc6</id>
    <link rel="alternate" type="text/html" href="http://www.freebase.com:80/view/guid/9202a8c04000641f8000000005453fc6" title="Digg API: Protocols"/>
    <summary type="html">I'm not sure the best way to do this, but I feel that the previously listed XML, PHP, and JS &amp;#8220...</summary>
    <title>Digg API: Protocols</title>
    <updated>2007-07-07T03:19:40.0012Z</updated>
  </entry>
</feed>