& current status (v0.0.6) Mara Poveda Villaln Fernando Serena - PowerPoint PPT Presentation

WoT ontology development & current status (v0.0.6) María Poveda Villalón Fernando Serena Raúl García Castro Ontology Engineering Group Universidad Politécnica de Madrid 17 st May, 2017 mpoveda@fi.upm.es Osaka F2F (remote) @MariaPovedaV

Ontology Engineering Group Created in1995 Directors: A. Gómez-Pérez, O. Corcho Position: 8th in the UPM ranking (200 groups) Research Group (30 people) o 2 Full Professors o 5 Associate Professors o 3 Assistant Professors o 7 Senior Postdocs o 6 PhD Students o 2 MSc and BSc Students o 2 software engineers o 1 system administrator o 2 project managers 170+ Past Collaborators http://www.oeg-upm.net/ 50+ Past Visitors https://github.com/oeg-upm @oeg-upm WoT ontology – Osaka F2F 2

Ontology Engineering Group   Created in1995 Awards and Prizes   Ada Byron, Fujitsu, Open data, ISWC World-wide known in the research areas  SUR Awards Watson for Tech. Watch  Ontologies  Supervision of students  Semantic Web and Linked Data   Multilingual linked Data 28 Ph.D thesis (9 awarded best thesis prize)   Open Data >150 MS.C thesis and BS.C  eScience  Events organization  Projects (> 12M € )  11 editions of the International Summer School on Ontological Engineering and the Semantic  27 EU projects (7 as coordinator) Web  54 National Projects  > 50 WS and tutorials  27 contracts with companies  Standardization activities  Awards: SUR IBM Watson   >25 @ W3C , ISO, OASIS, AENOR, etc. Publications   Mobility 106 journals  362 International conferences and book chapters  PhD students: 3-6 months abroad  7 Books  Postdocs: 1 month every 2 years  Impact of publications H-index  Visibility  Asunción Gómez-Pérez (h:50, citations 15025)  Program chairs of ESWC, ISWC, KCAP,  Oscar Corcho García (h: 36, citations 8258) EKAW, TKE, TIA   Editorial board of Journals Services to the Spanish community  Invited talks at conferences and events  Host esDbpedia  Programme Committee presence  Host linkeddata.es  Collaboration with COM (Center Open Middleware) WoT ontology – Osaka F2F 3

VICINITY - vision and Objectives http://vicinity2020.eu/ VICINTY’s vision is to  provide “Interoperability” as a service  create a platform for domain-crossing, value-added services by building and demonstrating a  bottom-up ecosystem of decentralised interoperability of IoT infrastructures called virtual neighbourhood,  like social network for things, enabling value added services o where users can share the access to their smart objects without losing the control over them o where x-domain services and buisiness models can be established WoT ontology – Osaka F2F 4

VICINITY ontology network Legend + - External drives Use case concept Ontologies is extended by Use case N Use case M Use case O is reused by VICINITY Requirements VICINITY Use case Ontologies Document Use case 2 Use case 1 VICINITY Domain building Ontologies WoT Health Transport Building health ontology transport VICINITY Crossdomain Reusability Ontologies space Usability Vicinity core ontology Service time Upper Web of Level Things Time Space Document - + WoT ontology – Osaka F2F 5

Ontology development process overview Openly reported in Openly managed GitHub issue tracker : in GitHub new needs, bugs, etc.  Ont. Devel.  Ont. Devel.  Ont. Devel.  Ont. Devel.  Users  Users  Experts  Experts Ontological Ontology Ontology Ontology requirements implementation Publication maintenance specification Competency Online Ontology Issue tracker questions ontology Shared in snapshot in documentation online spreadsheets  Actor Activity Output Legend activity flow Ontology code and documentation available online Slide 6 WoT ontology – Osaka F2F 6

Requirements from WoT WG http://w3c.github.io/wot/current-practices/wot- practices § Ont. Devel. § Ont. Devel. § Ont. Devel. § Ont. Devel. § Users § Users § Experts § Experts Ontological Ontology Ontology Ontology requirements implementation Publication maintenance specification Competency Online Ontology Issue tracker questions ontology https://lists.w3.org/Archives/Public/public-wot- ig/2016Dec/0016.html WoT ontology – Osaka F2F 7

WoT ontology 0.0.6 WoT ontology – Osaka F2F 8

Example wot:Thing wot:InteractionPattern sensor:Temperature wot:DataSchema wot:DataType wot:Link 7 wot:Property 4 ex:MyTemperatureThing TemperatureOutputData 7 wot:hasOutput 7 Data wot:hasValueType ex:number 4 9 1 7 3 9 wot:providesInteraction ex:MyTemperatureTh ex:MyTemperatureThing ex:temperature wot:isAccesibleThrough Pattern ingTemperatureLink1 2 5 8 6 10 11 om:Unit_of_measure sensor:unit wot:thingName wot:href wot:hasMediaType wot:interactionName wot:isWritable 6 “MyT emperature “co ap://mytemp.example.com: “t emperature “^ ^xsd:string “f alse ”^ ^xsd:boolean sensor:Celsius “a pplication/json “^ ^xsd:string Thing “^ ^xsd:string 5683/temp “^ ^xsd:string 1 2 3 4 5 6 7 8 9 10 11 WoT ontology – Osaka F2F 9

WoT Ontology implementation § Ont. Devel. § Ont. Devel. Output: § Users § Ont. Devel. § Ont. Devel. § Users § Experts § Experts Ontology Ontological Ontology Ontology Ontology code requirements implementation Publication maintenance specification Competency Online Ontology Issue tracker questions ontology Tool: Ontology editor Tool: GitHub repository Slide 10 https://github.com/mariapoveda/vicinity-ontology-wot WoT ontology – Osaka F2F 10

WoT ontology publication (so far) http://iot.linkeddata.es/def/wot/ § Ont. Devel. § Ont. Devel. § Users § Ont. Devel. § Ont. Devel. § Users § Experts § Experts No project dependencies. Ontological Ontology Ontology Ontology Proposal: http://www.w3.org/ns/td# requirements implementation Publication maintenance specification Output: Competency Online Ontology Issue tracker questions ontology Human oriented documentation Ontology code Output: Machine oriented code WoT ontology – Osaka F2F 11

Issue tracker § Ont. Devel. § Ont. Devel. Tool: GitHub issue tracker § Ont. Devel. § Ont. Devel. § Users § Users § Experts § Experts https://github.com/mariapoveda/vicinity-ontology-wot Ontological Ontology Ontology Ontology requirements maintenance implementation Publication specification Competency Online Ontology Issue tracker questions ontology WoT ontology – Osaka F2F 12

WoT evolution  Done o Remove • Physical thing, Virtual thing, Relative endpoint, Thing description ecosystem (VICINITY concept), o Rename • Data schema (data format), Link (endpoint), o Add • Security (not described yet) o Changed model • Default value (Property  DataSchema), Media type (concept  datatype), added cardinalities  Next steps: Currently discussing o Need of communication protocol? o Model types? o Coupling IG JSON model with ontology conceptual model? • Rename properties? • Not following OE good practices vs space reducing in TD? o Security WoT ontology – Osaka F2F 13

Questions? Thanks for you attention WoT ontology – Osaka F2F 14

WoT ontology development & current status (v0.0.6) María Poveda Villalón Fernando Serena Raúl García Castro Ontology Engineering Group Universidad Politécnica de Madrid 17 st May, 2017 mpoveda@fi.upm.es Osaka F2F (remote) @MariaPovedaV