rest/examples: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
= XHTML-REST Examples = | = XHTML-REST Examples = | ||
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. | |||
== The Problem == | == The Problem == | ||
' | |||
Quoting the wikipedia [http://en.wikipedia.org/wiki/Representational_State_Transfer#REST_versus_RPC REST] article: | |||
: 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 | |||
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. | |||
== Participants == | == Participants == | ||
* | * [mailto:drernie@opendarwin.org Dr. Ernie Prabhakar] | ||
* [mailto:luke.arno@gmail.com Luke Arno] | |||
* [mailto:dimitri.glazkov@gmail.com Dimitri Glazkov] | |||
== Real-World Examples == | == Real-World Examples == | ||
''Links to public web pages, either popular or insightful'' | ''Links to public web pages, either popular or insightful'' | ||
=== [Example #1 (url)] === | === [Example #1 (url)] === | ||
http://ietf.org/internet-drafts/draft-sayre-atompub-protocol-basic-03.txt | |||
pre | pre | ||
escaped <tags> | escaped <tags> | ||
| Line 23: | Line 34: | ||
* ''Link to related pages as they become available'' | * ''Link to related pages as they become available'' | ||
** [[rest-brainstorming]] | ** [[rest-brainstorming]] | ||
[http://www.opendarwin.org/~drernie/rest-api.html] | |||
** - proposal | ** - proposal | ||
** -microformat | ** -microformat | ||
== See Also == | == See Also == | ||
* | * [[forms-examples]] | ||
* [http://en.wikipedia.org/wiki/OpenSearch OpenSource search aggregation] | |||
* ''Normative references for tags used'' | * ''Normative references for tags used'' | ||
Revision as of 18:37, 13 October 2005
XHTML-REST Examples
These are some examples of how people are currently implementing REST web services (usually in XML), to provide some context for how best to implement them in XHTML.
The Problem
Quoting the wikipedia REST article:
- 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
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.
Participants
Real-World Examples
Links to public web pages, either popular or insightful
[Example #1 (url)]
http://ietf.org/internet-drafts/draft-sayre-atompub-protocol-basic-03.txt
pre escaped <tags>
[Example #2 (url)]
pre escaped <tags>
Existing Practices
- Summary of common patterns discovered
- Other attempts to solve The Problem
Proposal
- Early drafts
- Link to related pages as they become available
- - proposal
- -microformat
See Also
- Normative references for tags used