Linking your data into the mix: writing providers/consumers
JohnArwe 120000CAW7 Visits (1467)
One of the promises of Linked Data is that it's open: your data can participate on an equal footing with what others expose. Doing that requires either buying or writing code (sorry - no free lunch). A number of our products now expose linked data, especially where we know there is a need to integrate with other products and other parts of the ecosystem, and more are coming (just look at the open betas). Business partners and clients can play as well; half of our Pulse 2013 integration center spots were partners. All of us have in-house applications too, and we'd like them to play - here's how.
Part of that is making some implementation choices. Depending upon your platform, you might be able to exploit one or more of the open
By the way, most of our product linked data implementations are using the OSLC4J SDK hosted inside Eclipse Lyo. The ones that aren't are products with little or no Java code in their base, so they preferred to RYO and keep a single language code base. One of the reasons we're attracted to linked data generally is that it's focused on the wire interface (HTTP) not the SDK interface; so if you want to use a new or "unusual" implementation language, nothing gets in your way.