FI-WARE: Semantic Application Support Generic Enabler

1. FI-PPP Webinars FI-WARE: Semantic Application Support Generic Enabler Ivan Martinez Mauricio Ciprián

2. Follow Semantic Application Support GE @fiware_semapp News about the Semantic Application Support GE Please send us your question and doubts about the GE during the presentation

3. Outline • Overview • Semantic Application Support GE • SAS Infrastructure • Architecture • Main Interactions • Open RESTfulAPI • SAS Engineering Environment • Architecture • Main Interactions • Open Specification • Next Steps • Summary • Hands on: Using SAS in your application • Q&A Session

4. Overview • The Semantic Application Support enabler aims at providing an effective environment for developers to implement and deploy high quality Semantic Web-based applications • Reasons preventing semantic web adoption: • Technical: lack of infrastructure to meet industry requirements in terms of scalability, distribution, security, etc. • Engineering: not general uptake of methodologies, lack of best practices and supporting tools • Commercial aspects: difficulties to penetrate in the market, lack of understanding of the main strengths and weaknesses of the semantic technologies by company managers, no good sales strategies, etc.

5. Overview • The Semantic Application Support enabler addresses some of engineering and technical problems by providing: • SAS Infrastructure: An infrastructure for metadata publishing, retrieving and subscription that meets industry requirements like scalability, distribution and security. • SAS Engineering Environment: A set of tools for infrastructure and data management, supporting most adopted methodologies and best practices. • SAS is built on top of well-known semantic technologies (Sesame, NeOn Toolkit) and enhanced with lessons learnt from applying semantic technologies in several projects belonging to different domains. • Further info: http://forge.fiware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Data.SemanticSupport#Semantic_Application_Support_GE_ArchitectureAS Architecture Overview

6. SAS GE – SAS Infrastructure • SAS Infrastructure • Architecture • Main interactions • Open REST Full API

7. SAS GE – Architecture

8. SAS GE – Architecture • Data layer: • A relational database to store ontology documents loaded into the GE. • A Knowledge Base providing OWL-2RL support used by ontology and workspace registries to store ontology and workspace related metadata and by managing, querying and publishing modules to provide their functionality. • Presentation layer: • Functionality provided from SAS Infrastructure are supposed to be accessed for human users by means of the SAS Engineering Environment (aka NeOn Toolkit). • In addition web clients MAY be develop to access specific functionality, mainly related with infrastructure management.

9. SAS GE – Architecture • Business layer: • Ontology registry that manages ontologies loaded into the system and its related metadata. Operations: retrieving / uploading ontology, retrieving / uploading metadata, etc. • Workspace registry that manages workspaces and their related metadata created by users to be used by their semantic enable applications. Operations: creating / deleting a workspace, listing ontologies loaded into the workspace, etc. • Publishing module that allow user to publish data into the GE. • Managing module that allow users to monitor the status and content of the GE. Operations: retrieving a list of available ontologies, retrieving a list of subscriptions, etc • Subscription module that allows users to subscribe to events produced in the GE. Operations: subscribing to ontology updates or workspace modifications. • Querying module that allows users to query their workspace following SPARQL Query Protocol

10. SAS GE – Main Interactions • The description of this functionality is based on the functionality provided by the baseline asset in FI-WARE first release • It describes functionality provided by the GE enabler as service invocation methods for both human or computer agents. • A subset of methods belonging to publishing and managing rest APIs will be provided: • Publishing API: • Getting, uploading and deleting ontologies • Getting, uploading and deleting ontology metadata • Management API: • Listing ontologies and their versions

11. SAS GE – Open RESTfulAPI

12. SAS GE – Open RESTfulAPI • /ontologies/{ontologyIRI} • /ontologies/{ontologyIRI}/{versionIRI} • Open STFull API Spec - Ontologies

13. SAS GE – Open RESTfulAPI • /metadata/{ontologyIRI} • /metadata/{ontologyIRI}/{versionIRI} • Open RESTful API Spec - Metadata

14. SWAS GE – Open RESTfulAPI • /mgm/list • /mgm/list/{ontologyIRI} • API Spec - Management

15. SAS GE – SAS Infrastructure • SAS Engineering Environment • Architecture • Main Interactions • Open Specification

16. SAS GE – Architecture

17. SAS GE – Architecture • SAS Engineering Environment • Provides the core ontology editing and engineering functionality. • Relies in eclipse platform for handling project, folders, etc. • Contributed plug-ins • Extensions that provide extra functionality supporting different phases of the NeOn Methodology • SWAS GE Architecture

18. SAS GE – Main Interactions • SAS Engineering Environment functionality is based on the functionality provided by the baseline asset NeOn Toolkit. The NeOn Toolkit is a state-of-the-art, eclipse based, open source multi-platform ontology engineering environment, which provides comprehensive support for the ontology engineering life-cycle • It takes advantage of some paradigms introduced by Eclipse including: • Using workspaces, projects, folders and files as containers to organize and store development artifacts. • Using workbench, editors, views and perspectives to provide functionality to the user by means of GUI. • Therefore, most of the functionality provided by SAS Engineering Environment is provided as editors, views and perspectives

19. SAS GE – Main Interactions • Ontology navigation perspective allows users to manage their projects and ontologies, creating or removing projects, loading or creating new ontologies, etc • In the scope of a given ontology, users are able to manage (adding, removing, etc) main ontology contents such as classes, object properties and data properties. Once selected, ontology contents can be edited by means of a proper editor

20. SAS GE – Main Interactions • Class editor is composed of four tabs: • Class restrictions tab that allow the user to modify restrictions applicable to the class. • Taxonomy tabs that allow the user to modify the class ancestors, successors or siblings. • Annotation tab that allows the user to annotate the class con textual descriptions. • Source tab that presents the user the OWL code generated for the described class.

21. SAS GE – Main Interactions • Views present additional information about the items selected in the ontology navigation perspective. • Range view presents for each class, the set of object properties that has the selected class as range

22. SAS GE – Open Specification • SAS Engineering Environment functionality is based on the functionality provided by the baseline asset NeOn Toolkit. • NeOn Toolkit is an outcome of the NeOn Project (2006 – 2010) and nowadays is maintained by the NeOn Foundation… • So the best way to figure out what it can provide is… to download it and start working: http://neon-toolkit.org/

23. SAS GE – SAS Next Steps • SAS Next Steps: • Semantic Repository Component providing: • Application workspace management • RDF Schema + RDF Data storing • Synchronization with Ontology Registry • Frontend Functionality based on NeOn Toolkit framework. Mostof the functionality provided by SAS Engineering Environment will be provided as editors, views and perspectives. • Under Ontology Navigation perspective users are able to manage their projects and ontologies, creating or removing projects, loading or creating new ontologies, etc. • In the scope of a given ontology, users are able to manage (adding, removing, etc) main ontology contents such as classes, object properties and data properties. Once selected, ontology contents can be edited by means of a proper editor.

24. Summary • Semantic Web Application Support GE has been presented, including objectives, basic principles and architecture. • A concrete description of the functionalities that will be available for the first FI-WARE release has been made. • We are wiling to collaborate with UC Projects so let me remind that there is a tracker system so you can suggest functionality, ask for implementation order and interact with the team developing SAS GE.Data Tracker

25. Hands On: Using SAS GE in your applications. • SAS Service Endpoint (URL): • http://semanticas.lab.fi-ware.eu:8180/ontology-registry-service/webresources/ontology-registry • Demos: • Demo1: Register an ontology in the Registry • Demo 2: List the ontologies contained in the repository and their versions. • Demo 3: List the versions of a given ontology contained in the repository. • Demo 4: Get the metadata related to the latest version of an ontology. • Demo 5:Get the latest version of the ontology from the repository. • Demo 6:Get a specific version of an ontology from the repository.

26. Q&A Session Send us your questions through Twitter @fiware_semapp

27. Thank You !!

28. SAS GE – Main Interactions GONTT Label Translator