-
“ACM has three distinct member grades to recognize the professional accomplishments of our members”
-
My thoughts *exactly*
Danny notes that I chimed in with some Web architectural advice for those considering SPARQL updates.
On that page, he asks;
I’d like to hear more from Mark about what he sees as problematic about the current notion of binding. Although the spec seems unusual, the end result does seem to respect WebArch
It does respect Web architecture, but only because it’s read-only. As soon as you need to add mutation support, or indeed any other operation on the same resource, the process fails and what results is not Web-friendly. This is because “operation on the same resource” doesn’t work if the operation is part of the resource name; if the operation changes, the name changes, and therefore the resource-identified changes.
This is the same problem that APIs such as Flickr and del.icio.us suffer from; Web-friendly for read-only, horribly broken for updates.
Making something Web-friendly means mapping your data and services into a set of inter-linked resources. Application-specific APIs works directly against that.
And FWIW, from a REST POV the constraint that’s being disregarded in these scenarios is commonly resource identification.
-
“with REST, this turns out to be easy to fix”. I have to disagree that this is a quality of REST. One could easily build that capability into specs looking a whole lot like SOAP/WS-*, but you’d still have a crappy architecture.
-
I’m speechless.
-
Yeah! 8-) (via Libby Miller)
-
You’ll always be invited to my parties, Nelson 8-)
-
“Which brings to mind that it was ten years ago at that same conference (different name then) […]” I think it’s due another name change; “Web Data 2007” anyone?
-
Will wonders never cease?
-
“When requests for new features overwhelmed Last.FM’s small staff, the company made the bold decision to create open interfaces to the site, and soon independent developers began piling in with enhancements.” Nice.
-
Using all the right buzzwords, and avoiding all the wrong ones. Sounds like fun.
-
Robin gets indoctrinated?
-
Apparently he finds karma.
-
Good interview, including a good anti-complexity anti-WS-* bit. (@16:30).
-
“OpenLayers makes it easy to put a dynamic map in any web page.”. v2.2 released.
-
Mark falls a peg on my respect-o-meter.(not to worry Mark, you’re still way up there 8-)
-
OMG, this would be hilarious if weren’t so true. “Well, this new style isn’t actually written down anywhere.” Bingo! ROTFL!
Sanjiva gave a talk at Google on Web services, which also touched on REST. Unfortunately there’s a lot of misinformation in there about REST, including a statement to the effect of “If you want to sign your message, you can’t use REST” (I don’t think I’m taking that out of context), plus a slide (@ 25:00) that includes the following;
REST vs. WS-* is the wrong battle - WS-* is used to create Service Oriented Architecture - REST is used to create Resource Oriented Architecture
When taken together with some other comments, it appears as though Sanjiva sees REST as an alias for HTTP (or perhaps HTTP/URI), which it isn’t of course. He’s certainly entitled to his own beliefs, but I think he would do well to spend a couple of days with his nose buried deep in Roy’s dissertation… and not just chapter 5. Until that happens, I’d personally avoid trying to make conclusions about how these different approaches may or may not relate, or may or may not compete.
-
“Please do not play this game. We cannot stress this enough” 8-)
-
“When I first met Web fundamentalists, I found them irritating, because they would not debate on technical grounds. However, they have ultimately proved to be entertaining.” I aim to please! 8-O