1. 1 IST-4-027324-STP Start: April 2006

2. 2 Facts & Figures Start date:April 2006 End date:March 2009 Duration:36 month Number of partners:9 Number of countries:7 (AUT, BUL, ESP, FIN, GER, IRL, ITA) Number of work packages: 11 Number of deliverables: 46 Number of person*month:623 Budget total:€4‘661‘110.- EC funding:€3‘650‘000.-

3. 3 Email Human net Machine net MessagePublishing The Concept Triple Space Web So-called Web Services "TripCom will change the Internet usage for computers just as the Web revolutionized the Internet usage for humans"

4. 4 “Persistently publish and read semantic data that is denoted by unique identifiers” Communication platform for Semantic Web services based on Web principles: Fundamentals: Space-based computing – sharing information, knowledge RDF triples of the form: URI – Uniform Resource Identifier The Concept (2)

5. 5 The Vision Semantic Web (Triple) Technology + Ontologies Tuple Space Technology Web Service Technology Triple Space Service Technology

6. 6 Tuple Space Technology Asynchronous Communication by persistent publication in a shared Space without the need of a single central coordinator 3fold decoupling of dimensions of information exchange: 1.Processes do not need to address their communication partner, i.e., are completely decoupled in reference. 2.Communication is asynchronous since the space guarantees persistent storage of data, i.e., processes are completely decoupled in time. 3.The processes run in completely different computational environments as long as they can access the same space, i.e., processes are completely decoupled in space.

7. 7 Semantic Web Technology Shortcomings of the current Tuple Space models: lack of namespaces lack of unique identifiers lack of semantics (how do tuples relate in the space) structures (ontologies) for describing the information content of the tuples RDF/RDFS, WSMO! Graphs of -triples make up a structured Triple Space!

8. 8 Web Service Technology Current Web Services technologies (WSDL, SOAP, UDDI) are not so much about the Web They mainly use (synchronous) message exchange over Web protocols Process and application integration is inflexible How did the Web revolutionize human communication? By persistent publication, and searching information put by others on the Web  This is much closer to TupleSpaces than to RPC-Style Web Service Technologies around WSDL and SOAP!

9. 9 A Convergence of Technologies Semantic Web + Web Services Semantic Web Services Semantic Web + Tuple Spaces Triple Space Semantic Web Services + Triple Space

10. 10 Triple Spaces Triple Spaces provide a communication paradigm for anonymous, asynchronous information exchange that ensures the persistency and unique identification of the communicated semantic, semi-structured data.

11. 11 Triple Space Communication

12. 12 Basic entities: Triples  The semantic data exchanged or shared Triple Space  The space used to exchange or share triples Triple Space server  The infrastructure / server hosting Triple Spaces Triple Space Communication

13. 13 Triple Space Communication Triple Space architecture: Communication protocol for data exchange Communication interfaces e.g., write(triples) and read(query) over HTTP Triple Space operations layer Query handling Reasoner bindings Triple Space management (delete, empty, create…) Data Store management (resource bindings…) Storage component RDF Store, file system…

14. 14 1.Improve the ideas of Tuple Space computing by adding semantics 2.Integration of Web service infrastructure with the newly emerging Triple Space 3.Establishing a novel Semantic Web service paradigm 4.Address the lack of standardized business data ontologies 5.Scalable and linkable Triple Space storage 6.Security and trust mechanisms Core Objectives from the Proposal

15. 15 History Semantic Web + Web Services Semantic Web Services A Conceptual Model for SWS A Formal Language for WSMO Execution Environment for WSMO

16. 16 History (2) Semantic Web + Tuple Space Triple Space D. Fensel: Triple-space computing: Semantic Web Services based on persistent publication of information, Proc. of IFIP Int'l Conf. on Intelligence in Communication Systems, Bangkok, Thailand, November 2004: 43-53. R. Krummenacher, M. Hepp, A. Polleres, Ch. Bussler, and D. Fensel: WWW or What is Wrong with Web Services, Proc. 3rd European Conf. on Web Services ECOWS2005, Växjö, Sweden, November 2005: 235-243. Triple Space Computing (TSC) funded by FFG Austria

17. 17 History (3) Semantic Web Services + Triple Space Strengthen expertise in the fields of: Semantic Web (RDF) Web services (WS-* Standards) Linda/Tuple Spaces (extensions towards Semantic Web) Applications in Industry and Public Sector

18. 18 Selected Previous Collaborations UIBK, TUW: ongoing Austrian FFG project: "Triple Space Computing" TUW, UniS: research cooperation "BPEL and Space Based Computing" NUIG, FUB, UIBK: ongoing network of Excellence "KnowledgeWeb" UIBK, Ontotext, NUIG, SAP: ongoing integrated project "dip" UIBK, Ontotext, Profium: ongoing EU project "InfraWebs" CEFRIEL and partners in the WSMO+WSMX working groups: implementing a WSMO/L/X compliant discovery engine which is deployed within the COCOON project

19. 19 Main Project Output Reference Architecture (D6.1) Reference Implementation (D6.4, D2.3, D3.4) High-Performance RDF repositories (D1.3) Solutions to security & trust in distributed systems (D5.4) Integration with WSMO/L/X (D4.5) Ontologized version of selected EDI standards (D7.2) Realization in two concrete use cases (D8A.2, D8B.2) Standardization impact (D9.5) in Semantic Web, Semantic Web Services, Coordination Systems

20. 20 SEKT (Semantically-Enabled Knowledge Technologies) http://sekt.semanticweb.org/ DIP (Data, Information and Process with Semantic Web Services) http://www.nextwebgeneration.org/projects/dip/ Knowledge Web http://knowledgeweb.semanticweb.org/ Dissemination Channels Other Related efforts/projects: Super under negotiation Cocoon http://www.cocoon-health.com/ Infrawebs http://www.infrawebs.org/ Target Standardization Bodies: World Wide Web consortium (W3C) Organization for the Advancement of Structured Information Standards (OASIS) http://www.sdk-cluster.org

21. 21 Exploitation Strategy 1.Enhance existing products of the commercial partners of TripCom, e.g. Telefonica 1.Leverage TripCom implementations of semantically enhanced service interaction patterns 2.Target BPEL Standardization 3.Incubator programme for "Serviceoutsource.com" 4.Target public sector as early adopter 2.Identify new business possibilities / raise venture capital for new start-ups, e.g. CEFRIEL 3.Address other companies via our dissemination strategy