<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>randomdrake</author><text>Agreed. I came here to post something similar but I was going to mention working with SOAP[1] in addition to what you mentioned. It sounds like the OP is trying to do something which sounded very much like using SOAP and XML to me.&lt;p&gt;To paraphrase the OP, &quot;Since so many APIs can be described in similar terms, why don&apos;t we have some sort of standard that one can look at to identify how to use the API instead of letting the API speak for itself?&quot;&lt;p&gt;When you start going down this track, you&apos;re not only making things complicated on the client&apos;s end of things. On the server side, you&apos;re having to maintain two things for the API now. First: the ruleset, ensuring it&apos;s 100% to spec lest a client fail. Second: the code generating the response in the first place.&lt;p&gt;I&apos;ve built clients and servers for both RESTful and SOAPy APIs and I can say I would take REST any day.&lt;p&gt;[1] - &lt;a href=&quot;http://en.wikipedia.org/wiki/SOAP&quot; rel=&quot;nofollow&quot;&gt;http://en.wikipedia.org/wiki/SOAP&lt;/a&gt;</text><parent_chain><item><author>tommorris</author><text>Substitute &quot;XML&quot; for &quot;JSON&quot; and we&apos;ve now come full circle.&lt;p&gt;The point about REST is that it is self-describing. And ideally should be using the same URIs as the version people clicking around in Firefox or Chrome see. The API is just the XML or JSON or whatever is flavour of the week version of the HTML version.&lt;p&gt;(Or we could use embedded data—microformats, microdata, RDFa—and get rid of that distinction.)</text></item></parent_chain></comment><story><title>Stop Writing REST API Clients</title><url>http://ttezel.github.com/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>steveklabnik</author><text>Yes, we have. &lt;a href=&quot;http://en.wikipedia.org/wiki/Web_Application_Description_Language&quot; rel=&quot;nofollow&quot;&gt;http://en.wikipedia.org/wiki/Web_Application_Description_Lan...&lt;/a&gt;</text><parent_chain><item><author>tommorris</author><text>Substitute &quot;XML&quot; for &quot;JSON&quot; and we&apos;ve now come full circle.&lt;p&gt;The point about REST is that it is self-describing. And ideally should be using the same URIs as the version people clicking around in Firefox or Chrome see. The API is just the XML or JSON or whatever is flavour of the week version of the HTML version.&lt;p&gt;(Or we could use embedded data—microformats, microdata, RDFa—and get rid of that distinction.)</text></item></parent_chain></comment><story><title>Stop Writing REST API Clients</title><url>http://ttezel.github.com/</url></story>