Getting closer to a true Web standard for read-write Linked Data
JohnArwe 120000CAW7 Visits (3450)
"Last Call" is an important milestone in the process to becoming a W3C standard (aka Recommendation) - it means the working group has a draft that addresses all the issues from the charter, and it is now mature enough for wide review. Once we address Last Call review comments, implementations will begin in earnest (some are already working ahead on that, as is often the case).
As Tivoli's (er, CSI's) official Linked Data, Loose Coupling, and OSLC maven I get to look across all of the integration scenarios and try to keep the implementations coloring within certain architectural lines. I also get to talk to clients... very much UN-like when I started at IBM (ahem, "a few") years ago, and as a developer literally had to fight to meet one live and in person.
One thing I heard repeatedly at and after Pulse this year was: how do I "take action"? Usually in the context of "that UI preview shows me what's wrong, now how do I fix it?" Music to my ears.
You see, our platform architecture uses something called Linked Data, from our good friends Tim Berners-Lee et al. at the World Wide Web consortium. While TimBL always intended for the Web to be a read-write space, until IBM started to use it in Jazz-based products and CSI's platform architecture Linked Data was in effect read-only (most shopping carts etc use other approaches). It was technically possible to use it for read-write, but it wasn't happening in practice much and certainly not at enterprise scale. Part of the reason was that there were holes in the standards, so "best practice" was 'it' and, like opinions, BPs were common, varied, and sometimes conflicting. IBM started using an open
We got community consensus, we now have read-write linked data implementations with several releases of history, so you can take actions.
Now we need to help this permeate outward, so you can take actions in all your tools using standard Web mechanisms.
OSLC spec and IBM Rational/CSI implementations are not directly affected; that will happen later, and should be backward compatible (always MY goal - grew up on mainframes). The Linked Data Platform actually standardizes at least 50% of what's currently in OSLC Core. Othe
I expect the next version of OSLC Core, 3.0, to be based on the Linked Data Platform spec, and I think it's