Application integration with the W3C Linked Data standards Día W3C en España December 18 th, 2013

Transcription

1 Application integration with the W3C Linked Data standards Día W3C en España December 18 th, 2013 Nandana Mihindukulasooriya Universidad Politécnica de Madrid

2 2 Evolution of Application Integration Pointto-Point Message Broker Service Bus Shared Files Shared Databases RPC Web Services

3 3 Linked Data Connecting data distributed across the Web Similar to how documents are connected using hyperlinks to set up an hypertext web Based on four rules defined by Tim Berners Lee [1]: 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 [1] [2] Linking Data cloud diagram, by Richard Cyganiak and Anja Jentzsch.

4 4 Why Linked Data? Global identifiers that are dereferenceable Easily accessible data using HTTP Reconciliation of duplicate data Avoid data silos Use of standards Interoperability Flexible graph based RDF data model Easy to merge data from different sources No silver Multiple schemas can live together bullets Easy to evolve Typed links between data from different sources Ability to traverse through data to find more information and context Richer knowledge representation and modeling Mappings without complex transformations By adding more information rather than converting data

5 5 Linked Data specifications Domain Protocol Data model Serializations Query Specification HTTP RDF(S) RDF/XML Turtle TriG RDFa JSON-LD SPARQL Advanced modeling OWL W3C Linked Data Platform

6 6 Linked Data Platform RESTful protocol for Read / Write Linked Data Extensions to HTTP protocol Pagination, ordering, partial updates, introspection, creation factories, collections Standardization focused of interoperability Developed by W3C Linked Data Platform Working Group 54 participants from 32 organizations Industry: IBM, Oracle, EMC, Fujitsu, Link Software, Base22, Academia: Universidad Politécnica de Madrid, University of Oxford, DERI, Université de Lyon, INRIA, Progress: Several public working drafts are available On its way to a Candidate Recommendation Current and potential implementations: Link Virtuoso, Eclipse Lyo, ALM istack middleware, Apache Marmotta, Callimachus, Tabulator, rdflib.js, RWW.IO,

7 An example: BugLinks An LDP-enabled bug tracker 7 OPTIONS OPTIONS

8 8 Looking up for the project GET /bug-tracker/alm-istack HTTP/1.1 Host: example.org Accept: text/turtle; charset=utf-8 HTTP/ OK Content-Type: text/turtle; charset=utf-8 Link: < rel="type" ETag: dcterms: ldp: bt: < </bug-tracker/alm-istack> a ldp:simplecontainer, bt:productdescription; dcterms:title "A collection of bug reports on ALM istack project"; bt:developer </user/johndoe>; ldp:contains </bug-tracker/alm-istack/bug3>; ldp:contains </bug-tracker/alm-istack/bug4>.

9 9 Looking up for the project with many bugs (Paging) GET /bug-tracker/buggy-product HTTP/1.1 Host: example.org Accept: text/turtle; charset=utf-8 HTTP/ See Other Location: /bug-tracker/buggy-product?firstpage Link: < rel="type"

10 10 Looking up for the project with many bugs (Paging) II GET /bug-tracker/buggy-product?firstpage HTTP/1.1 Host: example.org Accept: text/turtle; charset=utf-8 HTTP/ OK Content-Type: text/turtle; charset=utf-8 Link: < rel="type Link: </bug-tracker/buggy-product?secondpage>; rel='next' ETag: ldp: bt: < Under discussion <bug-tracker/buggy-product> a ldp:simplecontainer,bt:productdescription; ldp:contains </bug-tracker/alm-istack/bug1>; ldp:contains </bug-tracker/alm-istack/bug200>.

11 11 Creating a new bug report POST /bug-tracker/alm-istack HTTP/1.1 Host: example.org Content-Type: dcterms: bt: < <> a bt:bugreport; dcterms:title "Server crashed"; dcterms:creator </user/janedoe>. HTTP/ Created Location: /bug-tracker/alm-istack/bug5 Link: < rel="type" ETag: W/" " Content-Length: 0

12 12 Looking up for a project (again) GET /bug-tracker/alm-istack HTTP/1.1 Host: example.org Accept: text/turtle; charset=utf-8 HTTP/ OK Content-Type: text/turtle; charset=utf-8 Link: < rel="type" ETag: W/ dcterms: ldp: bt: < </bug-tracker/alm-istack> a ldp:simplecontainer, bt:productdescription; dcterms:title "A collection of bug reports on ALM istack project"; ldp:contains </bug-tracker/alm-istack/bug3> ; ldp:contains </bug-tracker/alm-istack/bug4> ; ldp:contains </bug-tracker/alm-istack/bug5>.

13 13 Looking up for a bug report GET /bug-tracker/alm-istack/bug5 HTTP/1.1 Host: example.org Accept: text/turtle; charset=utf-8 HTTP/ OK Content-Type: text/turtle; charset=utf-8 Link: < rel="type" ETag: dcterms: ldp: bt: < </bug-tracker/alm-istack/bug5> a bt:bugreport; dcterms:title "Server crashed"; dcterms:creator </user/janedoe>; dcterms:created " T10:00"^^xsd:dateTime; bt:state bt:new..

14 14 ALM istack Project Objective: To evaluate and foster the adoption of Linked Data technologies as the means for facilitating real-time Application Lifecycle Management tool integration in enterprise-grade environments.

15 15 Architecture of the Proof-of-Concept

16 16 Enterprise readiness TRANSACTIONS PROVENANCE PARTIAL RETRIEVALS & UPDATES VALIDATION TESTING VOCABULARY MANAGEMENT SECURITY IDENTITY MANAGEMENT APPLICATION MODELS VERSIONING DESIGN PATTERNS & ANTI-PATTERNS PERFORMANCE OPTIMIZATION DISCOVERY & INTROSPECTION

17 17 Final remarks Linked Data can be a good approach when the integrations are data intensive Service orientation vs. Data / Resource orientation Linked Data Platform as a standard RESTful protocol for read/write Linked Data Supported by the industry OSLC / IBM Rational Jazz EU projects (PPP/FP7): CESAR, ifest, CRYSTAL Some work to be done on enterprise Quality of Service requirements

18 Thank You! Application integration with the W3C Linked Data standards Raúl García Castro, Miguel Esteban Gutiérrez, Nandana Mihindukulasooriya