JavaOne2012 _linkeddata_oslc

Leveraging W3C Linked Data for Loosely Coupled
Application Integrations

JavaOne 2012 Session CON5213
Steve Speicher
Linked Lifecycle Data and OSLC
Chief Architect
IBM Rational

@sspeiche

sspeiche@gmail.com

© 2012 IBM Corporation

Agenda

Linked Data


Software Development Tools : Year 2000 - point products

Software
Configuration Build automation
Management & management

Work-item & defect
Test automation Requirements
tracking (aka Change
& management management
Management)

User complaints
– Need tools to work better
– Need tools to work together


Year 2005 – ALM V1

Software Build automation
Configuration & management
Management

Work-item & defect
Test automation Requirements
& management management
Management)

ALM Solution

• Developer complaints • Mixed Tool Environments
– Clumsy integrations – Open-source offerings with DIY
– Want best-of-breed choice integration
– 3rd party ALM suites
• Management complaints
– Need governance, metrics,
reports, …


Year 2010 – Linked Data and OSLC – A major breakthrough

Software Build automation
Configuration & management
Management

Requirements
Test automation management
& management
Work-item & defect
Management)

Learned to integrate with open protocols instead of glue


Healthcare – Reporting of drug trial and adverse effects

 Often requires custom data collection techniques at many
office, clinic and mobile locations
 Need to report to drug producer as well as government
regulatory agencies
 Valuable data as input in diagnosing a patient’s condition


Healthcare – Adverse Event Reporting Landscape

Government
Drug
Regulatory Producer
Agency

For each of these 3, need:
•Custom protocol
•Custom format
•Custom schema
•Custom security


Linked Data – Defined by Tim Berners-Lee

1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those names.
3. When someone looks up a URI, provide useful information,
using the standards (RDF*, SPARQL)
4. Include links to other URIs. so that they can discover more
things.

He concludes this with: “Simple.”

Reference: “Linked Data”, Tim Berners-Lee, 2006-07-27


Linked Data – What is it?

TestCase 14 is blocked by Issue 973
http://srv/qm/tc/14 qm:blockedBy http://apache.org/jira/HTTPCLIENT-973

Joe is a committer for Apache
http://joecoder.me doap:committer http://apache.org

Issue 973 depends on Bug 318
http://apache.org/jira/HTTPCLIENT-973 cm:dependsOn http://bugs.sun.com/? id=7172318

Issue 973 is owned by Joe
http://apache.org/jira/HTTPCLIENT-973 dc:contributor http://joecoder.me


Linked Data – What is it? Show me a picture

blo
cke
dB
y
TestCase
14 contributor co
m
m
it t
Joe er

Issue
973

n
sO
nd Apache
pe
de
Bug
318


Linked Data – Bridging separate data sources (but with meaning)

Source: http://lod-cloud.net Sept 2011

v
er
S
OSLC – Based on Linked Data
<http://cm/bugs/2314> Common Resource Definitions
a oslc_cm:ChangeRequest ;
dcterms:relation <http://cm/bugs/1235>;

t
en
oslc_cm:implementsRequirement <http://rm/req/56> .

e n em
ym g
lo n a

t
D Ma
ic e
<http://rm/req/56>

ep
rv
Se
a oslc_rm:Requirement ;
dcterms:title “Online shopping cart”;
ol

oslc_rm:validatedBy <http://qm/tc/17> .
To
M Ch cle
ge ge

t
en
cy
na an

em l
ag o o
m
a

t
fe

en
T
Li

M le
a

lity yc
an
ua fec
L
Q
Li
Delegated Dialogs
m nts l
o
a ir e na em T o
l
ge e

t
eq yc

en
c
fe

Link Preview
M u
Li
R

http://open-services.net © 2012 IBM Corporation

Linked Data – state of the art

 Typically focused on exposing data with relationships
 No support for update and creation of granular data
 Data updated, created and deleted by receiving new dataset dumps
 Often an export transformation and dump of data
 Many different publications on anti-patterns and best practices
– They don’t all align
– Often different based on specialized usage

 Provides great value for many use cases as shown above
 Interoperable solutions are limited due to no agreement on anti-
patterns and best practices
 Leads to most applications support least common denominator or
hacks for different situations

Evolution of W3C Linked Data

 W3C Linked Data
 Four design principles proposed by Tim Berners-Lee in a 2006 article
 Standardization will accelerate industry adoption and enhance interop
 IBM Sponsored W3C Workshop on Linked Enterprise Data Patterns (Dec 2011)
– Participating organizations included EMC, Elsevier, IBM, Nokia, Oracle
– Workshop recommended W3C produce a standard “which defines a Linked Data
Platform”, leveraging RDF
 IBM Submitted Linked Data Basic Profile 1.0 proposal to W3C (March 2012)
– Base the Linked Data Platform foundation on OSLC Core technology and experience
– Co-submitters:
– Supporters:


W3C Linked Data Platform (LDP) Working Group

 Workgroup membership spans 45 participants from 27 organizations
 IBM and EMC as co-chair
 Working towards defining a clear definition of “Linked Data”, in the form of a W3C
Recommendation
– Based on Tim Berners-Lee four principles of Linked Data
 Chartered to produce a “Linked Data Platform” specification that:
– HTTP-based (RESTful) application integration patterns using read/write Linked Data
– Will complement SPARQL and will be compatible with standards for publishing
Linked Data, bringing the data integration features of RDF to RESTful, data-oriented
software development.

 On target to deliver a W3C Candidate Recommendation in 2013

Details @ http://www.w3.org/2012/ldp


Linked Data Platform - Resource

 What resource formats should be used?
 What literal value types should be used?
 Are there some typical vocabularies that should be reused?
 How is optimistic collision detection handled for updates?
 What should client expectations be for changes to linked-to
resources, such as type changes?
 What can servers do to ease the burden of constraints for resource
creation?


LDP Resource – GET a simple example

GET /container1/member1 HTTP/1.1
Request

Host: example.org
Accept: text/turtle container1

member1

member2
Removed HTTP headers to save some space
@prefix dcterms: <http://purl.org/dc/terms/>. member3

@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix ldp: <http://w3.org/ns/ldp#>.
Response

http://example.org
<http://example.org/container1/member1>
a o:Cash;
dcterms:title “ACME Bank savings account”;
o:value 45.00.


Linked Data Platform - Container

 To which URLs can I POST to create new resources?
 Where can I GET a list of existing resources?
 How is the order of the container entries expressed?
 How do I get information about the members along with the
container?
 How do I GET the entries of a large container broken up into pages?
 How can I ensure the resource data is easy to query?


ldp:Container – GET a simple example
Request

GET /container1 HTTP/1.1
Host: example.org

member1

member2
member3
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix ldp: <http://w3c.org/ns/ldp#>.
Response

<http://example.org/container1>
a ldp:Container;
dcterms:title "A very simple container";
rdfs:member
<http://example.org/container1/member1>,
<http://example.org/container1/member3>.


ldp:Container – create resource and add

POST /container1 HTTP/1.1
Host: example.org
Content-type: text/turtle container1
Content-length: 324
member1
Request

@prefix o: <http://example.org/ontology/>.
member3
<> +member4
a o:Stock;
dcterms:title “ACME Co.”;
o:value 100.00. http://example.org
Response

HTTP/1.1 201 CREATED
Content-Location: http://example.org/container1/member4


ldp:Container – get updated

GET /container1 HTTP/1.1
Request

Host: example.org

member1

Removed HTTP headers to save some space member2
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>. member4
Response

<http://example.org/container1>
a ldp:Container;
dcterms:title "A very simple container";
rdfs:member
<http://example.org/container1/member4>.


ldp:Container – Net worth example

Disclaimer: picture only in UML, does not follow UML constraints


ldp:Container – slightly more complex example

# The following is the representation of
# http://example.org/netWorth/nw1

<http://example.org/netWorth/nw1>
a o:NetWorth;
o:asset
<http://example.org/netWorth/nw1/assetContainer/a1>,
<http://example.org/netWorth/nw1/assetContainer/a2>.

<http://example.org/netWorth/nw1/assetContainer>
a ldp:Container;
dcterms:title "The assets of JohnZSmith";
ldp:membershipSubject <http://example.org/netWorth/nw1>;
ldp:membershipPredicate o:asset.

• Membership predicate is something other than rdfs:member (o:asset)
• Subject for members is something other than the container


Ldp:Container – Member Information

# chopped @prefix
a o:NetWorth;
o:asset

a ldp:Container;

<http://example.org/netWorth/nw1/assetContainer/a1>
a o:Stock;
o:value 10000.
a o:Bond;
o:value 20000.

• Statements about the member resources included with container representation response


ldp:Container – Only data about it, no members
Request

GET /netWorth/nw1?non-member-properties HTTP/1.1
Host: example.org
Accept: text/turtle; charset=utf-8


Response

a o:NetWorth.
# Members omitted

a ldp:Container;


ldp:Container – Paging (first page)
# Request-URI: http://example.org/netWorth/nw1?firstPage
# omitted @prefix
a o:NetWorth;
o:asset

a ldp:Container;
bp:membershipSubject <http://example.org/netWorth/nw1>;
bp:membershipPredicate o:asset.

<http://example.org/netWorth/nw1/assetContainer?firstPage>
a ldp:Page;
ldp:pageOf <http://example.org/netWorth/nw1/assetContainer>;
ldp:nextPage <http://example.org/netWorth/nw1/assetContainer?p=2>.

a o:Stock;
o:value 100.00.
a o:Cash;
o:value 50.00.

• New ldp:Page resource
• Members of containers are paged, not HTTP responses © 2012 IBM Corporation

ldpContainer – Paging (last page)
# Request-URI: http://example.org/netWorth/nw1/assetContainer?p=2
# omitted @prefix
a o:NetWorth;
o:asset

a bp:Container;
bp:membershipSubject <http://example.org/netWorth/nw1>;
bp:membershipPredicate o:asset.

<http://example.org/netWorth/nw1/assetContainer?p=2>
a ldp:Page;
ldp:nextPage rdf:nil.

a o:Stock;
dcterms:title "Big Co.";
o:value 200.02.

• Last page indicated by rdf:nil

ldp:Container – Paging (ordering)
# Request-URI: http://example.org/netWorth/nw1/assetContainer?firstPage
# omitted @prefix
a o:NetWorth;
o:asset

a ldp:Container;

<http://example.org/netWorth/nw1/assetContainer?firstPage>
a ldp:Page;
ldp:containerSortPredicates (o:value).

a o:Stock;
o:value 100.00.
a o:Cash;
o:value 50.00.

• Order indicated by ldp:containerSortPredicate
• No ordinal predicate introduced, leverage domain model © 2012 IBM Corporation

Open Source Linked Data projects

Simple yet solid framework for building RESTful Web
services based on JAX-RS

RDF Java API and Fuseki provides REST-style
SPARQL HTTP interface

Easily develop semantic web apps by providing tools to
manipulate RDF data, create RESTful Web Services

Extend traditional content management systems with
semantic services

SDK and supporting tools to help the community to
adopt OSLC specifications and build compliant tools


Handling Linked Data requests - GET


Handling Linked Data requests – HTTP POST

@OslcCreationFactory ( resourceTypes = {“http://open-services.net/ns/cm#ChangeRequest”} )

@POST

@Consumes({“application/rdf+xml”, “application/xml”, “application/json”})

@Produces({“application/rdf+xml”, “application/xml”, “application/json”})

public Response addChangeRequest(@Context final HttpServletRequest httpServletRequest,
@Context final HttpServletResponse httpServletResponse,
final ChangeRequest changeRequest)
throws URISyntaxException

{

// ... create magic happens here ...

return Response.created(about).entity(changeRequest).build();

}


Annotating Classes for RDF


Conclusion

 Linked Data space is actively evolving and maturing
 Loosely-coupled application integrations have benefited
 Good alignment with REST applications
 Further standardization will help the cause

May 8, 2012 © 2012 IBM Corporation

Questions?


BACKUP


Open Services for Lifecycle Collaboration (OSLC)
Working to improve the way software lifecycle tools share data

Open Services for Lifecycle Collaboration
Lifecycle integration inspired by the web

 Community driven and governed
 400+ registered community members
 Workgroup members from 34+ organizations
Automation

 Wide range of interests, expertise, & participation
 Open specifications for numerous disciplines
 Defined by scenarios – solution oriented
 Implementations from IBM, BPs, and Others Monitoring

 Based on Linked Data

Inspired by the web Free to use and share Changing the industry
Proven Open Innovative


JavaOne2012 _linkeddata_oslc

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to JavaOne2012 _linkeddata_oslc (20)

More from Steve Speicher (10)

JavaOne2012 _linkeddata_oslc

Editor's Notes