1 / 47

Towards a Multimedia Content Marketplace Implementation Based on Triplespaces

This paper discusses the implementation of a multimedia content marketplace based on triplespaces, providing an overview of the prototype architecture and requirements. It explores the challenges faced in the DAM marketplace and the benefits of using triple spaces for computing. The paper also presents the TripCom implementation and its logical and physical architectures.

bkathy
Download Presentation

Towards a Multimedia Content Marketplace Implementation Based on Triplespaces

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Towards a Multimedia Content Marketplace Implementation Based on Triplespaces David de Francisco (Telefónica R&D), Lyndon JB Nixon (Free University of Berlin), Germán Toro (Telefónica R&D) 7th International Semantic Web Conference (ISWC ’08), Karlsruhe

  2. Outline • Introduction • Context, prototype overview and requirements • Triple Space Computing and Platform • TSC Paradigm, TripCom implementation • Prototype Implementation • Prototype architecture, Triple Space integration • Conclusions and References

  3. Outline Introduction Context, prototype overview and requirements Triple Space Computing and Platform TSC Paradigm, TripCom implementation Prototype Implementation Prototype architecture, Triple Space integration Conclusions and References

  4. Business Context Isolated data islands • Use of proprietary technologies • Custom applications vs. configurable applications • Redundant information • Communication protocols must be agreed • Lack of scalability • Reusing processes is difficult • Lack of process flexibility Over rigid processes Time to market difficulties High integration costs

  5. Digital Content: Overview • Collaborative scenario between • Dynamic scenario where • Ad-hoc business relationships are often changed • Users will evaluate and influence the services • Strong dependenciesbetween actors • A service is a bundle of contents and added services

  6. DAM Marketplace Challenges Development simplicity • Quick development (time to market requirements) • Flexible and decoupled solution • Tackle heterogeneity issues • Provision of a business mediation in which actors can rely on • Take advantage of available information • Size of information and number of actors are unpredictable • Keep a good balance between marketplace size and functionality Value added provision Scalability

  7. DAM Marketplace Requirements • Unified Catalogues • Common vocabulary. • Persistent storage and co-coordinated access • Provision of added value information • Service Management • Users are able to subscribe and evaluate services • Business Mediation • Simplify the business negotiation • Asynchronous and secure auctions • Automatically notification of auction events • Contracts • Confidentiality • Service unavailability -> service re-design • Dependencies between actors

  8. Outline Introduction Context, prototype overview and requirements Triple Space Computing and Platform TSC Paradigm, TripCom implementation Prototype Implementation Prototype architecture, Triple Space integration Conclusions and References

  9. Triple Space Computing • Temporal decoupling • Spatial decoupling • Reference decoupling • Schema decoupling

  10. TripCom: Physical Architecture

  11. TripCom: Logical Architecture

  12. Outline Introduction Context, prototype overview and requirements Triple Space Computing and Platform TSC Paradigm, TripCom implementation Prototype Implementation Prototype architecture, Triple Space integration Conclusions and References

  13. CP 3 Auction Marketplace Model SP1 SP2 SPN … SP: Service Provider CP: Content Provider 1. Asynchronous Content offers Triple Space 6. Best offer notification 5. Auction messages 4. Asynchronous notification to CPs 3. Catalogue checking 2. Content request publication Contains public information from CP’s offers Content catalogue CP 1 CP 2 CP 3 CP N …

  14. What Triple Spaces offer Semantics • Provide a shared vocabulary to data sources • Allows the inference of added value information • Retrieval of information from several sources (joint queries) through SPARQL • Enables the retrieval of information which is not available when the query is made • Solves many communication patterns by using subscribe-notify mechanisms • Coordination in the access to information • Support for current most extended SOAimplementations companies may have • Improvement of the interoperability of services among companies Communication and Coordination Web services support Semantic Web services support Agile and flexible development of the use case

  15. Prototype Architecture

  16. Use Case Ontology • Gets business knowledge from EDIFACT ontologies • Reasoning and expressivity • RDFS expressivity • Use of R-entailment rules • Makes use of the TRREE reasoner integrated in the storage component

  17. Catalogue Management (I) CP 1. Enter the Create Catalogue Menu DAM Marketplace Application TripCom Infrastructure 2. Get current catalogues from CP Root Space Catalogues Root Space 3. Get catalogues ParamountCatalogues CP<X> Catalogues CP<Y> Catalogues <C2> <C1>

  18. Catalogue Management (II) CP 1. Enter the Create Catalogue Menu DAM Marketplace Application 2. Crete a new subspace 4. Get catalogues 3. Security Policies TripCom Infrastructure Root Space 5. Catalogues Info Catalogues Root Space ParamountCatalogues CP<X> Catalogues CP<Y> Catalogues <C2> New <C1>

  19. Outline Introduction Context, prototype overview and requirements Triple Space Computing and Platform TSC Paradigm, TripCom implementation Prototype Implementation Prototype architecture, Triple Space integration Conclusions and References

  20. Conclusions • Triple Spaces provide a semantic middleware which facilitates the prototype development • Decouples the communication • Takes care of notification (pubsub) • Takes care of security issues • Marketplace Implementation provides added value • Semantic information allows a better catalogue integration • Scalability allows a flexible deployment, depending on the marketplace’s size

  21. Next Steps • Validation of the marketplace implementation • Scalability tests • how much information can we store in catalogues and what is the retrieving performance? • Concurrent access tests • How many content providers can simultaneously compete in an auction using our implementation? • Further uses of semantic information • Integration of recommendations • Customer profiling • Towards the automation of business transactions

  22. References and Links • Triple Space Computing: • Fensel, D.: Triple-Space Computing: Semantic Web Services Based on Persistent Publication of Information. Proc. of the IFIP Int'l Conf. on Intelligence in Communication Systems. Volume 3283 of Lecture Notes in Computer Science., Springer-Verlag (November 2004) pp: 43-53. • Riemer, J., Martín-Recuerda, F., Ding, Y., Murth, M., Sapkota, B., Krummenacher, R., Shaq, M.O., Fensel, D., Kühn, E.: Triple space computing: Adding semantics to space-based computing. In: The Semantic Web - ASWC 2006, Volume 4185 of Lecture Notes in Computer Science., Springer Verlag (September 2006) pages: 300-306. • TripCom project: • http://www.tripcom.org • http://sourceforge.net/projects/tripcom/ • Digital Content Marketplace information • http://www.tripcom.org/docs/del/D8A.1.pdf • Deliverable 8A.2 to be published on the same page soon

  23. Thanks for your attentionQuestions?

  24. Space Paradigm: Publication Humanity: storytelling books Internet: email web Distrib. computing: messaging spaces

  25. Problem Statement Distributed systems dominated by messaging Web services / SOAP CORBA / RPC / RMI / MOM Agents Web architecture different Persistent publicationas the main principle Uniform interface Uniform addressing Web clearly scales to a large size

  26. Message-based Communication

  27. Direct Messaging

  28. Spaces: Indirection

  29. Decoupling in Location Nodes can move:

  30. Decoupling in Reference Nodes can even multiply: …or be anonymous.

  31. Decoupling in Time out rd out rd

  32. Reliability out rd rd out rd

  33. Space-based Communication out space rd in

  34. Origins of Spaces • Coordination language Linda • Mid-1980s • Tuple Spaces • Decoupling in time, space, reference • Simplifies distributed programming • Shared associative memory • Criticized for slowness • Many implementations • JavaSpaces (used in JINI), GigaSpaces etc.

  35. Space Operations • Out ( Tuple, [TimeToLive] ) • Read ( Template, [Timeout] ) + ReadMulti • In ( Template, [Timeout] ) + InMulti • Because sometimes, delete just is a good idea • Subscribe ( Template ), Unsubscribe() • Adds asynchrony between client and space • Transaction management

  36. Templates • Tuple spaces: Templates by values, types Template: <"request", integer, string> Data: <"request", 1, "apple"> <"unitRequest", "apple"> <"request", 2, "apple", "today"> <"Anfrage", "Apfel", 1> <"response", 1, "apple", 0.75, "Euro">     

  37. Triplespace Uses Semantics • Triple spaces: queries for reasoner Query:{ ?x a Request; quantity ?y; product ?z } Data: {a1 a Request; quantity 1; product Apple .} {a2 a UnitRequest; product Apple .} {a3 a Request; quantity 1; product Apple; date today .} {a4 a Anfrage; Anzahl 1; Artikel Apfel .} {b1 a Response; request a1; price 0.75^^Euro .}     

  38. Outline Introduction Context, prototype overview and requirements Triple Space Computing Spaces vs. messaging, semantics in TSC Triple Space Platform Architecture Prototype Implementation Prototype architecture, Triple Space integration Conclusions and References

  39. Triple Space Global infrastructure Singular view on complex system Applications use the "Triple Space" Triple Space client client

  40. Triple Space: System Connect to one Triple Space kernel Read/Write semantic data via Triple Space API Interact/coordinate with other clients Triple Space TS-kernel client TS-kernel TS-kernel client TS-kernel

  41. Triple Space: Structure Composed of singular, but layered spaces logical entity, addressed via URI distributed over one or more co-authoringkernels organized in hierarchies Triple Space TS-kernel client TS-kernel TS-kernel client TS-kernel

  42. Triple Space: Access Triple Space coordination primitives out, rd: address a particular triplespace („with target“) rd can also address the Triple Space („without target“) p s o Triple Space out client out rd client rd

  43. Triple Space: Distribution Triple Space distribution the global infrastructure is distributed over kernels and spaces discovery in the global Triple Space via DHT p s o Triple Space TS-kernel client TS-kernel TS-kernel rd client TS-kernel

  44. Triple Space: Distribution Triple Space distribution the global infrastructure is distributed over kernels and spaces discovery in the global Triple Space via DHT p s o Triple Space TS-kernel client TS-kernel TS-kernel rd client TS-kernel

  45. Triple Space Kernel Architecture Kernel is built from self-contained components connected via coordination middleware: JavaSpaces Handling of external communication with clients:Triple Space API with adminstrator: Management API with other kernels: Distribution Manager

  46. Triple Space Kernel Components Implementing internal functionality storing the semantic data:Triple Store Adapter security constraints checking: Security Manager semantic mediation: MediationManager knowledge about Triple Space: Metadata Manager preprocessingsemantic queries: Query Processor handling transactions: Transaction Manager

  47. Triple Space as a communication layer (grounding) for Web services Components implementing Web service functions Web Service Invocation Web Service Discovery Web Service Registry Triple Space for Web Services

More Related