Distributed Semantic Middleware for Social Robotic Services
0 likes503 views
The document describes a distributed semantic middleware called otsopack that uses triple spaces to enable information sharing in distributed robotic services. It discusses triple spaces and otsopack, and provides examples of its use in two scenarios: a supermarket scenario using a guiding robot and a hospital scenario for patient tracking. The middleware allows decoupled and extensible information sharing between nodes using semantic web technologies.
Distributed Semantic Middleware for Social Robotic Services
- 1. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Distributed Semantic Middleware for Social Robotic Services Eduardo Castillejo1 , Pablo Ordu˜a1 , Xabier Laiseca1 , Aitor n G´mez-Goiri o 1 , Diego L´pez-de-Ipi˜a1 and Sergio F´ o n ınez2 1 DeustoTech - Deusto Institute of Technology, University of Deusto http://www.morelab.deusto.es 2 Treelogic http://www.treelogic.com 1 de diciembre de 2011 1 / 26
- 2. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Index 1 Introduction Distributed Systems Semantic Web 2 Triple Spaces Middleware 3 Scenarios Supermarket Hospital 4 Conclusions 5 Acknowledgments 6 References 2 / 26
- 3. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Contents 1 Introduction Distributed Systems Semantic Web 2 Triple Spaces Middleware 3 Scenarios Supermarket Hospital 4 Conclusions 5 Acknowledgments 6 References 3 / 26
- 4. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Distributed Systems Pros & Cons. Pros Concurrency Scalability Workload distribution Etc. Cons Data flow management Storage decissions Nodes crashing recovery Dynamic response to nodes additions and crashes Etc. 4 / 26
- 5. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Semantic Web The Semantic Web in short I The vision of the Semantic Web is to extend principles of the Web from documents to data. Data should be accessed using the general Web architecture using, e.g., URI-s; data should be related to one another just as documents (or portions of documents) are already. This also means creation of a common framework that allows data to be shared and reused across application, enterprise, and community boundaries, to be processed automatically by tools as well as manually, including revealing possible new relationships among pieces of data. http://www.w3.org/RDF/FAQ 5 / 26
- 6. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Semantic Web The Semantic Web in short II The Semantic Web is about two things. It is about common formats for integration and combination of data drawn from diverse sources, where on the original Web mainly concentrated on the interchange of documents. It is also about language for recording how the data relates to real world objects. That allows a person, or a machine, to start off in one database, and then move through an unending set of databases which are connected not by wires but by being about the same thing. http://www.w3.org/2001/sw/ 6 / 26
- 7. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Semantic Web Why? The Semantic Web aims to offer machine-understandable persisten data for embracing the machine-centered approach. Ok, then... Knowledge representation! 7 / 26
- 8. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Semantic Web How? On the Semantic Web, vocabularies define the concepts and relationships (also referred to as “terms”) used to describe and represent an area of concern. Vocabularies are used to classify the terms that can be used in a particular application, characterize possible relationships, and define possible constraints on using those terms. In practice, vocabularies can be very complex (with several thousands of terms) or very simple (describing one or two concepts only). http://www.w3.org/standards/semanticweb/ontology 8 / 26
- 9. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Contents 1 Introduction Distributed Systems Semantic Web 2 Triple Spaces Middleware 3 Scenarios Supermarket Hospital 4 Conclusions 5 Acknowledgments 6 References 9 / 26
- 10. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Middleware Triple Spaces basics TS computing is a coordination paradigm on which nodes can share information in a decoupled way. It is a distributed shared semantic space between nodes which join it. How does it work? RDF Triples “instead of” tuples Storage data structure: RDF graphs Primitives: write, read, take and query 10 / 26
- 11. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Middleware Otsopack Our TS solution is called otsopack (http://code.google.com/p/otsopack/) It has been used for several scenarios: A supermarket scenario A hospital scenario 11 / 26
- 12. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Middleware Why otsopack? Different actors concurrently communicating with each other and sharing information. The amount of required network dependent information (e.g. IP addresses) should be maintained as low as possible. The management of the mutability of the nodes. The need of accessing information using network-independent addresses. Information flow needs to be asynchronous. 12 / 26
- 13. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Middleware Benefits Time autonomy. Reference autonomy. Focused on Semantic Web technologies. Some benefits from Tuple Space: Location and space autonomy. Reference autonomy. Time autonomy. TS gathers both techniques, Tuple Spaces and the Semantic Web, contributing with data schema autonomy, following the RDF specification making it independent of nodes internal data schema. 13 / 26
- 14. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Contents 1 Introduction Distributed Systems Semantic Web 2 Triple Spaces Middleware 3 Scenarios Supermarket Hospital 4 Conclusions 5 Acknowledgments 6 References 14 / 26
- 15. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Supermarket Scenario A: Supermarket Scenario main purpose: to increase user experience and to ease their interactions while shopping, thanks to TICO. Developed use cases using the otsopack middleware Guiding robot use case: TICO + an Android app. + otsopack Marketing robot use case: TICO + supermarket servers + otsopack View some pictures 15 / 26
- 16. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Hospital Scenario B: Hospital Scenario main goals: To facilitate the tracking of patients’ memory progressions To allow caregivers and relatives to participate in the treatment To ease the use of non-pharmacological treatments on patients with cognitive impairments View some pictures 16 / 26
- 17. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Contents 1 Introduction Distributed Systems Semantic Web 2 Triple Spaces Middleware 3 Scenarios Supermarket Hospital 4 Conclusions 5 Acknowledgments 6 References 17 / 26
- 18. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Conclusions & Future work Back to the benefits of using TS TS benefits every scenario on which semantics and a distributed architecture is needed Transparent integration for all components TS provides is a decoupled and easily extensible platform for sharing information between nodes Keep improving otsopack! 18 / 26
- 19. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Contents 1 Introduction Distributed Systems Semantic Web 2 Triple Spaces Middleware 3 Scenarios Supermarket Hospital 4 Conclusions 5 Acknowledgments 6 References 19 / 26
- 20. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Acknowledgments This work has been supported by project grant TSI-020301-2009-27 (ACROSS), funded by the Spanish Ministerio de Industria, Turismo y Comercio. 20 / 26
- 21. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Contents 1 Introduction Distributed Systems Semantic Web 2 Triple Spaces Middleware 3 Scenarios Supermarket Hospital 4 Conclusions 5 Acknowledgments 6 References 21 / 26
- 22. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References References Castillejo, E. and Ordu˜a, P. and Laiseca, X. and G´mez-Goiri, n o A. and L´pez-de-Ipi˜a, D. and F´ o n ınez, S. Distributed Semantic Middleware for Social Robotic Services Fensel, D. Triple Space computing: Semantic web services based on persistent publication of information In: Intelligence in Communication Systems, pp. 43-53. Springer Berlin / Heidelberg (2004) Nixon, L.J.B. and Simpler, E. and Krummenacher, R. and Martin-Recuerda, F. Tuplespace-based computing for the semantic web: A survey of the state-of-the-art. In: The Knowledge Engineering Review. Vol. 23, Num. 2, pp. 181-212. Cambridge Univ Press (2008) 22 / 26
- 23. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References More bibliography Web Ontology Language. Mike Dean et al. http://www.w3c.org/2004/OWL/ Pellet: the OWL2 reasoner for Java. http://www.clarkparsia.com/pellet/ Common Object Request Broker Architecture. http://www.corba.org/ Resource Description Framework. http://www.w3c.org/RDF/ Intelligent Semantic Middleware for Embedded Devices. http://www.tecnologico.deusto.es/projects/ismed/ JXTA P2P middleware https://jxta.dev.java.net/ Worl Wide Consortium. W3c semantic web faq, August 2011 23 / 26
- 24. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Morelab at Twitter Follow us in Twitter! @morelab ud @DeustoTech http://www.morelab.deusto.es 24 / 26
- 25. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Scenario A: Supermarket Back 25 / 26
- 26. Introduction Triple Spaces Scenarios Conclusions Acknowledgments References Scenario B: Hospital Back 26 / 26