An alternative to an oEmbed API
An argument against oEmbed as a separate API and for using a more RESTful approach (eg, content-type with application/oembed+json on the original URL)
- Web Address: http://www.backdrifter.com/2008/05/09/oembed-fail-represent-restfully/
- Short Name: trukuqurix
-
Short Link: http://ma.gnolia.com/trukuqurix
-
Tags: oembed, data portability
- Saved by Michael Richardson on May 12, 2008.
Bookmark licensed under Creative Commons Attribution Non-commercial Share Alike 2.5.
2 other people have commented on this bookmark
| Name | Title | Rating | When | |
|---|---|---|---|---|
 |
Lachlan | Backdrifter: oEmbed FAIL! Represent RESTfully. |
Not rated yet.
|
May 14, 2008 |
oEmbed is the latest standard to come out of the Web 2.0 developer crowd. While I’m typically a huge advocate of standards, and think much of the prior work has been superb, oEmbed fails on almost every level. So much so, in fac... |
||||
 |
Chris | Backdrifter: oEmbed FAIL! Represent RESTfully. |
Rated stars out of 5.
|
May 13, 2008 |
Decent critical look at oEmbed. |
||||
1 group has this bookmark in their collection
| Name | Title | Rating | When | |
|---|---|---|---|---|
| DiSo Project | Backdrifter: oEmbed FAIL! Represent RESTfully. |
Rated stars out of 5.
|
May 13, 2008 |
Decent critical look at oEmbed. |
||||