Two new articles: how Linked Data formed the basis of OSLC and two sample applications

Two articles about OSLC went up recently that you all might find interesting.

First up, Arnaud Le Hors and Steve Speicher discuss why Linked Data was the perfect framework to use to build OSLC specifications:

We wanted an architecture that is minimalist, loosely coupled, had a standard data representation, kept the barriers to entry low and could be supported by existing applications implemented with many implementation technologies. We realized that one such solution already existed: Linked Data.

Linked Data, as defined by Tim Berners-Lee, builds on the same principles that have made the World Wide Web so successful: it works in terms of protocols and resource formats rather than application specific interfaces. The web of documents uses HTTP and HTML. Linked Data uses HTTP and RDF. Both use URIs to identify resources allowing to easily express arbitrary linkage between resources, independently of their domain.

Applying Linked Data to the ALM domain integration problem meant thinking in terms of domain specific resources, such as requirements, change requests, and defects, and access to these resources rather than in terms of tools. We stopped thinking of the applications as being the central concept of the architecture and instead started to focus on the resources.

(Aside: I don’t know why the URL for that article has “2001”, but it is in fact from this month.)

Next, Vijay Kalangumvathakkal posted two example OSLC applications that you can set up and tinker with. The GenericProvider application provides a template for creating an OSLC ServiceProvider, and the PreviewDemo application demonstrates User Interface previews (it also doubles as a handy debugging tool to confirm that the XML output from an OSLC provider conforms to the specification).

Both sample applications require Python and a Tivoli Directory Integrator Assembly (there are sample scripts). Check the readme.txt with each application for more details.