distributed semantic middleware for social robotic services
TRANSCRIPT
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Distributed Semantic Middleware for SocialRobotic Services
Eduardo Castillejo1, Pablo Orduna1, Xabier Laiseca1, AitorGomez-Goiri1, Diego Lopez-de-Ipina1 and Sergio Fınez2
1DeustoTech - Deusto Institute of Technology, University of Deustohttp://www.morelab.deusto.es
2Treelogic http://www.treelogic.com
1 de diciembre de 2011
1 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Index
1 IntroductionDistributed SystemsSemantic Web
2 Triple SpacesMiddleware
3 ScenariosSupermarketHospital
4 Conclusions
5 Acknowledgments
6 References
2 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Contents
1 IntroductionDistributed SystemsSemantic Web
2 Triple SpacesMiddleware
3 ScenariosSupermarketHospital
4 Conclusions
5 Acknowledgments
6 References
3 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Distributed Systems
Pros & Cons.
ProsConcurrencyScalabilityWorkload distributionEtc.
ConsData flow managementStorage decissionsNodes crashing recoveryDynamic response to nodesadditions and crashesEtc.
4 / 26
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 Webfrom documents to data. Data should be accessed using thegeneral Web architecture using, e.g., URI-s; data should berelated to one another just as documents (or portions ofdocuments) are already. This also means creation of a commonframework that allows data to be shared and reused acrossapplication, enterprise, and community boundaries, to beprocessed automatically by tools as well as manually, includingrevealing possible new relationships among pieces of data.
http://www.w3.org/RDF/FAQ
5 / 26
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 commonformats for integration and combination of data drawn fromdiverse sources, where on the original Web mainly concentratedon the interchange of documents. It is also about language forrecording how the data relates to real world objects. Thatallows a person, or a machine, to start off in one database, andthen move through an unending set of databases which areconnected not by wires but by being about the same thing.
http://www.w3.org/2001/sw/
6 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Semantic Web
Why?
The Semantic Web aims to offer machine-understandablepersisten data for embracing the machine-centered approach.
Ok, then...
Knowledge representation!
7 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Semantic Web
How?
On the Semantic Web, vocabulariesdefine the concepts and relationships(also referred to as “terms”) used todescribe and represent an area ofconcern. Vocabularies are used toclassify the terms that can be used in aparticular application, characterizepossible relationships, and definepossible constraints on using thoseterms. In practice, vocabularies can bevery complex (with several thousands ofterms) or very simple (describing one ortwo concepts only).
http://www.w3.org/standards/semanticweb/ontology
8 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Contents
1 IntroductionDistributed SystemsSemantic Web
2 Triple SpacesMiddleware
3 ScenariosSupermarketHospital
4 Conclusions
5 Acknowledgments
6 References
9 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Middleware
Triple Spaces basics
TS computing is a coordination paradigm on which nodes canshare information in a decoupled way. It is a distributed sharedsemantic space between nodes which join it.
How does it work?
RDF Triples “instead of” tuplesStorage data structure: RDF graphsPrimitives: write, read, take and query
10 / 26
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 scenarioA hospital scenario
11 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Middleware
Why otsopack?
Different actors concurrently communicating with each otherand 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-independentaddresses.Information flow needs to be asynchronous.
12 / 26
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 RDFspecification making it independent of nodes internal data schema.
13 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Contents
1 IntroductionDistributed SystemsSemantic Web
2 Triple SpacesMiddleware
3 ScenariosSupermarketHospital
4 Conclusions
5 Acknowledgments
6 References
14 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Supermarket
Scenario A: Supermarket
Scenario main purpose: to increase user experience and toease their interactions while shopping, thanks to TICO.Developed use cases using the otsopack middleware
Guiding robot use case: TICO + an Android app. + otsopackMarketing robot use case: TICO + supermarket servers +otsopack
View some pictures
15 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Hospital
Scenario B: Hospital
Scenario main goals:
To facilitate the tracking of patients’ memory progressionsTo allow caregivers and relatives to participate in the treatmentTo ease the use of non-pharmacological treatments on patientswith cognitive impairments
View some pictures
16 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Contents
1 IntroductionDistributed SystemsSemantic Web
2 Triple SpacesMiddleware
3 ScenariosSupermarketHospital
4 Conclusions
5 Acknowledgments
6 References
17 / 26
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 adistributed architecture is needed
Transparent integration for all components
TS provides is a decoupled and easily extensible platform forsharing information between nodes
Keep improving otsopack!
18 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Contents
1 IntroductionDistributed SystemsSemantic Web
2 Triple SpacesMiddleware
3 ScenariosSupermarketHospital
4 Conclusions
5 Acknowledgments
6 References
19 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Acknowledgments
This work has been supported by project grantTSI-020301-2009-27 (ACROSS), funded by the Spanish Ministeriode Industria, Turismo y Comercio.
20 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Contents
1 IntroductionDistributed SystemsSemantic Web
2 Triple SpacesMiddleware
3 ScenariosSupermarketHospital
4 Conclusions
5 Acknowledgments
6 References
21 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
References
Castillejo, E. and Orduna, P. and Laiseca, X. and Gomez-Goiri,A. and Lopez-de-Ipina, D. and Fınez, S.Distributed Semantic Middleware for Social Robotic Services
Fensel, D.Triple Space computing: Semantic web services based onpersistent publication of informationIn: Intelligence in Communication Systems, pp. 43-53. SpringerBerlin / Heidelberg (2004)
Nixon, L.J.B. and Simpler, E. and Krummenacher, R. andMartin-Recuerda, F.Tuplespace-based computing for the semantic web: A survey ofthe state-of-the-art.In: The Knowledge Engineering Review. Vol. 23, Num. 2, pp.181-212. Cambridge Univ Press (2008)
22 / 26
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 middlewarehttps://jxta.dev.java.net/
Worl Wide Consortium. W3c semantic web faq, August 201123 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Morelab at Twitter
Follow us in Twitter!
@morelab ud @DeustoTech
http://www.morelab.deusto.es
24 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Scenario A: Supermarket
Back
25 / 26
Introduction Triple Spaces Scenarios Conclusions Acknowledgments References
Scenario B: Hospital
Back
26 / 26