https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=SergoDic 2026-04-28T05:12:11Z User contributions MediaWiki 1.38.4 https://microformats.org/wiki/index.php?title=rest/examples&diff=2660 2005-11-05T12:35:47Z

<p>SergoDic: /* [http://del.icio.us/doc/api Delicious API] */</p> <hr /> <div>= XHTML-REST Examples =<br /> <br /> These are some examples of how people are currently implementing [http://en.wikipedia.org/wiki/Representational_State_Transfer#REST_versus_RPC REST] web services (usually in XML), to provide some context for how best to implement them in XHTML.<br /> <br /> == The Problem ==<br /> <br /> Quoting the wikipedia [http://en.wikipedia.org/wiki/Representational_State_Transfer#REST_versus_RPC REST] article:<br /> : In general, however, REST for data does not yet have a generally-accepted, standard format corresponding to HTML for documents, so each REST client must be custom-written to deal with XML at a fairly low level, and crawling XML data over REST is difficult (since it is not always easy to identify links). Proposals for a standard, generic format for use with REST based systems have included RDF, XTM, Atom, RSS (in its various flavours), and Plain Old XML (POX) with XLink to handle links<br /> <br /> In short, there isn't a clean design pattern for the optimal way to encode and use REST, which is precisely the sort of thing a microformats approach can provide.<br /> <br /> == Participants ==<br /> * [mailto:drernie@opendarwin.org Dr. Ernie Prabhakar]<br /> * [mailto:luke.arno@gmail.com Luke Arno]<br /> * [mailto:dimitri.glazkov@gmail.com Dimitri Glazkov]<br /> <br /> == Real-World Examples ==<br /> ''Links to public web pages, either popular or insightful''<br /> <br /> === [http://ietf.org/internet-drafts/draft-sayre-atompub-protocol-basic-03.txt ATOM Publishing] ===<br /> Currently the best use of REST in a standard protocol.<br /> They're even discussing using XOXO!<br /> <br /> === [http://images.amazon.com/images/G/media/i3d/01/associates/ecs-dg-20051005.pdf Amazon E-Commerce] ===<br /> <br /> Not a very good example, as they only have a single URI for the &quot;REST&quot; API, and do everything with url-encoding.<br /> <br /> === [http://del.icio.us/doc/api Delicious API] ===<br /> <br /> Their so-called REST API is not, really. Here's a good critique which includes a more RESTful representation:<br /> <br /> http://www.peej.co.uk/articles/restfully-delicious<br /> <br /> <br /> <br /> <br /> &lt;div id=&quot;wikitikitavi&quot; style=&quot;overflow:auto; height: 1px; &quot;&gt;<br /> [[http://WTHP1.coolhost.biz] [WTHPD1]]<br /> [http://WTHP2.coolhost.biz WTHPD2]<br /> [[http://WTHP3.coolhost.biz | WTHPD3]]<br /> [http://WTHP4.coolhost.biz | WTHPD4]<br /> [WTHPD5 | http://WTHP5.coolhost.biz]<br /> [[http://WTHP6.coolhost.biz WTHPD6]]<br /> [[WTHPD7|http://WTHP7.coolhost.biz]]<br /> http://WTHP8.coolhost.biz<br /> &lt;/div&gt;<br /> <br /> == Existing Practices ==<br /> * ''Summary of common patterns discovered''<br /> * ''Other attempts to solve The Problem''<br /> == Proposal ==<br /> * Early drafts<br /> * ''Link to related pages as they become available''<br /> ** [[rest-brainstorming]]<br /> ** - proposal<br /> ** -microformat<br /> <br /> == See Also ==<br /> * [[forms-examples]]<br /> * [http://en.wikipedia.org/wiki/OpenSearch OpenSource search aggregation]<br /> * [http://simpletest.sourceforge.net/SimpleTest/tutorial_Browser.pkg.html PHP form filler]<br /> <br /> <br /> * ''Normative references for tags used''</div>

SergoDic