/* Google Analytics ----------------------------------------------- */

Wednesday, April 7, 2010

Liquid data best example: doyoubuzz.com

doyoubuzz.com is theperfect example of service that should have been invented sooner. You already have an account in Linkedin or Viadeo then, in few clicks, you can build your own Web Resume and then spend hours in playing with colors and layout.
What's interesting here is that data is automatically moved from one service to the other. That's for me the perfect example of liquid data. But this is a proprietary interface (as far as I know).

Microsoft is working on a new protocol called Open Data Protocol (OData). "The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores." OData is being used to expose and access information from a variety of sources including, but not limited to, relational databases, file systems, content management systems and traditional Web sites. So that could be a good opportunity for implementing liquid data across cloud services.

Another approach is to use the Content Management Interoperability Services (CMIS), a proposed standard for improving interoperability between Enterprise Content Management systems. It proposes a data model plus a set of generic services and several protocol bindings for these services, including: SOAP and Representational State Transfer (REST)/(Atom). Using CMIS you can implement an unique client application that can manipulate contents with all the repositories that support this new standard. Apache Chemistry is an effort to provide aOpen Source CMIS implementation API and xCMIS is an open source, server side Java CMIS implementation created by exoplatform team (now building GateIn) that is able to expose the content in existing content repositories according to the protocols defined in the CMIS spec.

My main issue is now, as usual, to be able to get an end to end vision of my information flow moving from nodes to nodes. For example, imagine that you use you HR tool to describe a new job position. This information could then be "pushed" to multiple job boards. Candidates could then answer with a URL instead of sending a word document. This URL will be used to gather the data, integrate them in the HR recruitment tool and eventually could be sent in parallel to a eReputation service that will compute your profile. Based on your age, gender and location, it can also propose the average salary for your position.

Frightening or Cool? Not sure yet.