links for 2006-11-30

Filed in Uncategorized 3 Comments

links, rest

links for 2006-11-28

Filed in Uncategorized Leave a comment

links, rest

links for 2006-11-27

Filed in Uncategorized Leave a comment

links

links for 2006-11-25

Filed in Uncategorized Leave a comment

links, rest

links for 2006-11-24

Filed in Uncategorized Leave a comment

links, rest

REST is a CLM?

Filed in Uncategorized Leave a comment

According to Steve Jones, REST is a career limiting move;

But as with any technical discuss there is another thing that should drive you when you look to your decisions. This is whether you want to get fired for a decision when something goes wrong, and whether you want your skills to be relevant in 3 years time.

That would be funny if it weren’t so sad; completely accurate, yet aimed entirely in the wrong direction 8-(

rest, softarch, web, webservices

links for 2006-11-23

Filed in Uncategorized Leave a comment

links, rest, soap

links for 2006-11-22

Filed in Uncategorized Leave a comment

links

The trouble with “binding”

Filed in Uncategorized 9 Comments

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.

rdf, rest, semanticweb, softarch, sparql, web

links for 2006-11-21

Filed in Uncategorized Leave a comment

  • “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.

links, rest, soap

TOP