Alfresco first introduced its Web Services for Content Management back in July 2005, almost two years ago. In those two years the software world has radically changed. Think back to July 2005. Google Maps API had only just been released, the whole Web 2.0 thing had only just started to roll, Mark Baker and company were way ahead of the curve while the rest of us believed in SOAP, and had you heard of the Arctic Monkeys? Today, it's all about mash-ups, rich applications, scripting and the network as the platform. And of course, you can't ignore the current REST Fest, now we've all caught up - could it be that SOAP slips away to be replaced with what was already there.
Given this trend, ECM should rethink the way it provides Web Services. Imagine being able to expose your enterprise content resources (folders, documents, searches, categories, versions, discussions, workflows etc) to your network with the minimum of effort; distributed resources that can be retrieved, managed, mashed by any part of your enterprise software suite. Imagine being able to build custom content services specifically for your domain and application needs without Java knowledge, tooling, compilation, stub generation or XSD.
Here's an example of how such a resource (a folder) might be exposed (as an ATOM feed) via a HTTP URL:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.