[Warning]This blog post contains technical information, apologies to those who read my blog for the more personal posts[/Warning]
What is ODS?
ODS or OpenLink Data Spaces is a Virtuoso powered web application, it can be seen as an implementation of something similar to what Jon Udell calls the Fourth Platform. It is a distributed system that has been developed with a social/collaborative mindset. It has its own blogging, wiki, photo gallery and bookmarking components, and also integrates with WordPress and MediaWiki. ODS can also grab information from services such as del.icio.us and facebook.
The clever thing about ODS is that it opens all of these components and integrations to the Semantic Web. You can write SPARQL queries to look through the various components and integrations of the system, yep, you can SPARQL your own WordPress blog! This has been enabled by using Semantic vocabularies: SIOC, SKOS and FOAF - in addition to some innovative use of technologies such as XBEL, OpenID, OPML, ATOM, RSS and SyncML etc etc etc.
More details about what ODS is can be seen: (HERE) and (HERE)
So you’d think that all of the user interface is going to be a big mess of complexity - well OpenLink have done a good job of clearing up the UI, and they have plans to improve it further. So how do we use it.
How to use ODS
Well, I have been exploring ODS (and Virtuoso and OAT) for only two days and there is a lot more to it all that I haven’t seen yet. But the interface for ODS is simple, we are provided with the components at the top of the web app, and by clicking on any one of them you have the option to create the a new instance of that component (or application as it is called within the system - quite reminiscent of systems like Facebook who have apps and Google who have widgets).
One of the cool parts of ODS is the briefcase, which brings all of the other components together into one area ready for some data crunching using SPARQL (for example) and easy navigation by the user.
By looking into briefcase a little more you start to realise that you are actually centralising all of your data… we have a central endpoint. Centralised yet distributed.
Centralised Endpoint - Useful Simple URIs
By centralising everything we have one simple way of accessing data using URIs.
For example, my personal myopenlink URI is:
https://myopenlink.net/dataspace/danieljohnlewis#this
And everything is accessible through:
https://myopenlink.net/dataspace/danieljohnlewis#this
When I say everything I mean you can use it for FOAF, SIOC, SKOS etc etc.
Meshups
So as you can see we are “meshing” these things together which would previously have been separate entities with potentially different identities. We mesh these things together and provide one uniform identity (and this identity is in the form of a URI and an OpenID - same value). Clever.
Once these things are meshed, you can now see that you can compare information from these different entities (or components) and see things that you previously couldn’t. E.g. You could ask “what websites have I bookmarked, and talked about on my blog, that are to do with some type of computer”. These things are possible. Linked Data.
Power and Scalability
So we have some clever stuff, but we need the power and the storage. ODS has been developed with this in mind, and is installable on Amazon EC2. ODS + Amazon EC2 = A Powerful, Speedy, Scalable, Social Data Web Cloud.
“A Data Space in the Clouds”
Finally
Of course ODS is only one way of implementing “Linked Data”/ “Meshing”/”Cloud Data”/”Cloud Computing” and no doubt there will be more attempts by various people and organisations - and not necessarily in the same ways… and its going to be interesting to see how these things occur - and - themselves, mesh together to form a larger “Data Web”.
I am still learning about all the services provided by ODS, OAT and Virtuoso - but I am liking what I am seeing.
Technorati Tags: openlink, ods, ec2, linkeddata, meshup