rest/rex-proposal

(Difference between revisions)

Jump to: navigation, search
(Challenge #2: Only Two Verbs)
(DUHPER: A Dual-Use HTML Profile Expressing REST)
Line 2: Line 2:
== The 0.8% Solution for Web Services ==
== The 0.8% Solution for Web Services ==
==== October 18th, 2005 ====
==== October 18th, 2005 ====
 +
"Something better than a diaper-soundex" naming content: XOX-REST = XOXR (SHOCKER)
= Web Services: The Opportunity =
= Web Services: The Opportunity =

Revision as of 14:54, 18 October 2005

Contents

DUHPER: A Dual-Use HTML Profile Expressing REST

The 0.8% Solution for Web Services

October 18th, 2005

"Something better than a diaper-soundex" naming content: XOX-REST = XOXR (SHOCKER)

Web Services: The Opportunity

Web Services: The Problem

The Answer(?): REST vs. RPC

Advantages of REST over RPC

Challenges of REST

Discoverability
No standard way to find services
Interoperability
Too many incompatible ways to encode links, data
Extensability
What if your schema isn't 100% right?
Comprehensability
What the heck does "state transfer" mean?

Proposal: A Dual-Use (X)HTML Profile

Three Challenges

Challenge #1: Machine-Parseability

What Are Microformats?

Kinds of Microformats

Example: hCard

<div class="vcard">
 <a class="url fn" href="http://tantek.com/">
  Tantek Çelik
 </a>
 <div class="org">Technorati</div>
</div>

Example: eXtensible Open XHTML Outlines

<dl class='xoxo'> <-- Dictionary -->
 <dt>Key #1<dt>
 <dd><ol> <-- Array -->
       <li>subitem #1</li>
       <li>subitem #2</li>
 </ol></dd>
</dl>

Challenge #2: Only Two Verbs

Challenge #3: Key-Value Data

The 0.8% Solution for Web Services

Advantages

Implications

For More Information

rest/rex-proposal was last modified: Wednesday, December 31st, 1969

Views