EclipseCon 2013 Learn and share about integrations using Eclipse Lyo, OSLC and Linked Data
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


EclipseCon 2013 Learn and share about integrations using Eclipse Lyo, OSLC and Linked Data






Total Views
Views on SlideShare
Embed Views



34 Embeds 964 310 177 95 82 38 37 34 28 23 23 16 15 14 10 8 8 7 7 5 4 4 3 3 2 2 1 1 1 1 1 1 1 HTTP 1 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

EclipseCon 2013 Learn and share about integrations using Eclipse Lyo, OSLC and Linked Data Presentation Transcript

  • 1. Leveraging W3C Linked Data, OSLC, and Open Sourcefor Loosely Coupled Application Integrations Steve Speicher OSLC Core Lead W3C Linked Data Platform Workgroup IBM Rational @sspeiche Michael Fiedler OSLC Automation Lead Eclipse Lyo Project Lead and Committer IBM Rational @mffiedler © 2013 IBM Corporation
  • 2. Software Development Tools : Year 2000 - point products Software Build automation Configuration & management Management Test automation Requirements Work item & management & management bug tracking User complaints – Need tools to work better – Need tools to work together © 2013 IBM Corporation
  • 3. Year 2005 – ALM V1 Software Configuration Management Build automation & management Test automation Requirements & management Work item & management bug tracking ALM Solution •  Developer complaints •  Mixed Tool Environments –  Clumsy integrations –  Open-source offerings with –  Want best-of-breed choice DIY integration •  Management complaints –  3rd party ALM suites –  Need governance, metrics, reports, … © 2013 IBM Corporation
  • 4. Year 2010 – Linked Data and OSLC – A major breakthrough Software Configuration Build automation Management & management Test automation & management Requirements management Work item & bug tracking Learned to integrate with open REST-based protocols instead of glue @ © 2013 IBM Corporation
  • 5. Linked Data – Defined by Tim Berners-Lee1. Use URIs as names for things2. 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 © 2013 IBM Corporation
  • 6. Linked Data – What is it? TestCase 14 is blocked by Issue 973 http://srv/qm/tc/14 qm:blockedBy Joe is a committer for Apache doap:committer Issue 973 depends on Bug 318 cm:dependsOn id=7172318 Issue 973 is owned by Joe dc:contributor © 2013 IBM Corporation
  • 7. OSLC – Based on Linked Data <http://cm/bugs/2314>Tool Lifecycle Common Resource Definitions a oslc_cm:ChangeRequest ; Service Management Change dcterms:relation <http://cm/bugs/1235>; Help Desk Management oslc_cm:implementsRequirement <http://rm/req/56> . <http://rm/req/56> a oslc_rm:Requirement ;Lifecycle Tool dcterms:title “Online shopping cart”;Requirements oslc_rm:validatedBy <http://qm/tc/17> .Management Lifecycle Tool Quality Management Delegated Dialogs Service Management Deployment Link Preview © 2013 IBM Corporation
  • 8. OSLC Specifications: Layered Cake and Independently Adoptable New domains as needed Domains Performance Monitoring Automation Keep scope Change Management Quality Management simple, learn and iterate OSLC Core Common Provides common and REST W3C Linked Data core needs © 2013 IBM Corporation
  • 9. Evolution of W3C Linked Data§  2006: Tim Berners-Lee introduced Linked Data as four design principles in an article§  May 2011: IBM and W3C agreed that standardization is necessary to accelerate industry adoption and enhance interoperability§  Dec 2011: IBM Sponsored W3C Workshop on Linked Enterprise Data Patterns – Participating organizations included EMC, Elsevier, IBM, Nokia, Oracle – Workshop recommended W3C produce a standard “which defines a Linked Data Platform”, leveraging RDF§  March 2012: IBM Submitted Linked Data Basic Profile 1.0 proposal to W3C – Base the Linked Data Platform foundation on OSLC Core technology and experience – Co-submitters: – Supporters:§  June 2012: W3C launched the Linked Data Platform (LDP) Working Group – Membership spans over 50 participants from 30 organizations – Arnaud J Le Hors (IBM) and Erik Wilde (EMC) as co-chairs © 2013 IBM Corporation
  • 10. W3C Linked Data Platform (LDP)§  WG is chartered to produce a W3C Recommendation:–  For HTTP-based (RESTful) application integration patterns using read/write Linked Data–  It 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.■ LDP defines a set of rules that clarify and extends Tim Berners-Lees four basic rules focusing on the following concepts:–  LDP Resources (LDPR) –  HTTP and RDF techniques to read and write linked data–  LDP Containers (LDPC) –  A LDPR to which you POST to create new things, GET to find existing things –  Similar to what AtomPub does for XML–  Paging –  A mechanism to get the content of a LDPC in chunks–  Ordering –  A mechanism to specify the order in which the content of a LDPC is sorted§  WG currently on target to deliver a W3C Candidate Recommendation by the end of 2013.Details @ © 2013 IBM Corporation
  • 11. W3C Linked Data Platform (LDP)■  Published 1st Public Working Draft of Use Case and Requirements on January 31■  Published 2nd Public Working Draft of Linked Data Platform 1.0 spec on March 7■  2nd Face-to-Face meeting March 13-15 Cambridge, MA ■  14 in attendance in all (out of 50 members) ■  Worked on key issues (IBMs issues identified via SWGAB Linked Data WG and OSLC) ■  Covered topics of required deliverables: specification, use case and requirements, test suite, and access control requirements.■  Key issues ■  Binary resources and metadata – agreement on direction, editor to make changes ■  Partial update of resources – agreed on direction in line with OSLCs approach. ■  Composition and aggregation models for containers – working on a new proposal to address various concerns with the status quo.§  Last Call specification most likely to slip from May to June.§  3rd Face-to-Face meeting scheduled for June to address any remaining issues.§  WG still on target to deliver a W3C Candidate Recommendation by the end of 2013.§  Details @ © 2013 IBM Corporation
  • 12. 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? © 2013 IBM Corporation
  • 13. LDP Resource – GET a simple example Request GET /container1/member1 HTTP/1.1 Host: Accept: text/turtle container1 member1 member2 Removed HTTP headers to save some space member3 @prefix dcterms: <>. @prefix rdfs: <>. @prefix ldp: <>. <> a o:Cash; dcterms:title “ACME Bank savings account”; Response o:value 45.00. © 2013 IBM Corporation
  • 14. 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? © 2013 IBM Corporation
  • 15. ldp:Container – GET a simple example Request GET /container1 HTTP/1.1 Host: Accept: text/turtle container1 member1 member2 Removed HTTP headers to save some space member3 @prefix dcterms: <>. @prefix rdfs: <>. @prefix ldp: <>. <> a ldp:Container; dcterms:title "A very simple container"; rdfs:member <>, <>, Response <>. © 2013 IBM Corporation
  • 16. OSLC’s Big Picture Tests, Libraries, Samples, Examples, The Resource Reference Implementations for OSLC Implementers Futu r OSL e Home o C Sp ec D f ev LINKED DATA PLATFORM WORKING GROUP Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web Scenario-driven & Solution-oriented Leading choice for strategic integration technology Generally applicable: specs available for many domains covering ALM, DevOps, ISM, and PLM Inspired by the web Free to use and share Changing the industry OSLC: Proven Open Innovative © 2013 IBM Corporation
  • 17. 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 Impl of LDP that can be extended and deployed easily by orgs who want to publish data or build custom apps SDK and supporting tools to help the community to adopt OSLC specifications and build compliant toolsOSLC4Net OSLC SDKs and tools for the .NET development community © 2013 IBM Corporation
  • 18. Eclipse Lyo•  Provide tools to enable adoption of OSLC and Linked Data specifications•  SDKs –  OSLC4J, OAuth, Lyo::OSLC for Perl –  OSLC provider and consumer development•  Test Suites –  Assessment reports OSLC implementations –  Coverage for Core + Change, Requirements, Quality, Asset and Automation. Performance Management tests under development.•  Sample implementations, workshops, tutorials –  Provider and consumer samples. –  Updated tutorial:•  Project update –  1.1 available in February (Client SDK, OAuth libraries, other enhancements) –  2.0 planned for June (new spec support, new samples, non-Java libs) © 2013 IBM Corporation
  • 19. ü  OSLC – http://open-services.netü  Eclipse Lyo –ü  W3C Linked Data Platform – © 2013 IBM Corporation