230 likes | 332 Views
www.ontogrid.net. Ontology Access in Grids with WS-DAIOnt and the RDF(S) Realization. Miguel Esteban Gutiérrez mesteban@fi.upm.es Asunción Gómez-Pérez asun@fi.upm.es Óscar Muñoz García omunoz@delicias.dia.fi.upm.es Boris Villazón Terrazas bvillazon@fi.upm.es. Ontology Engineering Group, UPM.
E N D
www.ontogrid.net Ontology Access in Grids with WS-DAIOnt and the RDF(S) Realization Miguel Esteban Gutiérrezmesteban@fi.upm.esAsunción Gómez-Pérezasun@fi.upm.esÓscar Muñoz Garcíaomunoz@delicias.dia.fi.upm.esBoris Villazón Terrazas bvillazon@fi.upm.es Ontology Engineering Group, UPM Semantic Grid Workshop GGF16, Athens, 15th Feb 2006
Table of Contents • OGSA-DAI limitations • WS-DAIOnt • Goals • Approaches • WS-DAI-RDF(S) • Component Description • Implementation details • Short demo • Workplan GGF16, Athens, 15th Feb 2006
Diversity of Ontology tools and languages • No uniform access to ontologies implemented in W3C languages • RDF(S) • OWL • Each language has several query languages • and inference engines • RDF(S): SparQL, SeRQL, RQL, RDQL and SILRI, RIL, Triple • OLW: OWL-QL and FACT, Racer • Each ontology tool and storage system has its own API for accessing ontologies • Accessing RDF(S) ontologies • Sesame • Statements(classUri, rdfs:type, rdfs:class) next() getObject() • Jena • getResource(classURI) GGF16, Athens, 15th Feb 2006
OGSA-DAI limitation • No Grid compliant ontology access mechanisms in RDF(S) and OWL • No specialized registry for localizing ontologies • No Grid compliant instance access mechanisms in RDF • SemGrid Applications access ontologies as on the Semantic Web GGF16, Athens, 15th Feb 2006
OGSA-Ont OGSA-Ont • Grid compliant ontology access mechanisms • RDF(S) • OWL • Specialized registry for localizing ontologies GGF16, Athens, 15th Feb 2006
Ontologies and S-OGSA Is-a Middleware layer Insurance settlement Satellite quality analysis Application layer Architect, adapt and extend existing ontology services to be Grid compliant • Access heterogeneus and distributed ontology sources as a homogeneous logical resources • Provide homogeneous service interfaces • Modular design to ease extensibility GGF16, Athens, 15th Feb 2006
What is WS-DAIOnt? • Web Services Data Access and Integration – The Ontology Realization • Specification of Grid Compliant Ontology Services, which • Defines a framework for creating ontology access services in aGrid environment • Is fully compliant with S-OGSA (consequently with OGSA) • Is based on up-to-date Grid standards (GGF) • WS-DAI • Is based on Web Service standards (OASIS, W3C) • WS-RF, WS-Addressing... • First implementation of WS-DAIOnt-RDF(S) • Backend: Sesame and SeRQL as query language • Download it from the OntoGrid web site (www.ontogrid.net) GGF16, Athens, 15th Feb 2006
Four approaches for WS-DAIOnt Monolithic approach Jena Jena Sesame Sesame Dual tier approach Declarative approach Dual tier approach Low extensibility and adaptability Metamodel approach Monolithic approach High extensibility and adaptability GGF16, Athens, 15th Feb 2006
Two sample implementations: Architectural implications • Dual tier approach: • Client side: single access logic • Server side: One protocol + two implementations • Monolithic approach: • Client side: splitted ontology access logic • Server side: Two protocols + two implementations GGF16, Athens, 15th Feb 2006
RDFS model GGF16, Athens, 15th Feb 2006
Component Description Jena .... GGF16, Athens, 15th Feb 2006
RDFSRepositorySelectorService GGF16, Athens, 15th Feb 2006
RDFSRepositorySelectorService getRepositoryFactory message Returns a EPR for a given repository <xsd:element name="getRepositoryFactory"> <xsd:complexType> <xsd:sequence> <xsd:element name = "id" minOccurs="1" maxOccurs="1" ref="tns:repositoryId"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="getRepositoryFactoryResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name = "epr" minOccurs="1" maxOccurs="1" ref="wsa:EndpointReference"/> </xsd:sequence> </xsd:complexType> </xsd:element> GGF16, Athens, 15th Feb 2006
RDFSRepositoryService GGF16, Athens, 15th Feb 2006
RDFSRepositoryService getClassFactory message Returns the EPR for a given class <xsd:element name="getClassFactory"> <xsd:complexType> <xsd:sequence> <xsd:element name="classUri" maxOccurs="1" minOccurs="1" ref="tns:Uri"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="getClassFactoryResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name="epr" ref="wsa:EndpointReference"/> </xsd:sequence> </xsd:complexType> </xsd:element> GGF16, Athens, 15th Feb 2006
RDFSClassService GGF16, Athens, 15th Feb 2006
RDFSClassService getSubclasses message Returns all the subclasses of a given class <xsd:element name="getSubClasses"> <xsd:complexType/> </xsd:element> <xsd:element name="getSubClassesResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name="classes" minOccurs="0" maxOccurs="unbounded" ref="tns:Uri"/> </xsd:sequence> </xsd:complexType> </xsd:element> GGF16, Athens, 15th Feb 2006
RDFSClassService getSuperClasses message Returns all the superclasses of a given class <xsd:element name="getSuperClasses"> <xsd:complexType/> </xsd:element> <xsd:element name="getSuperClassesResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name="classes" minOccurs="0" maxOccurs="unbounded" ref="tns:Uri"/> </xsd:sequence> </xsd:complexType> </xsd:element> GGF16, Athens, 15th Feb 2006
The rest of the model 1 3 2 GGF16, Athens, 15th Feb 2006
Configuration RDFSRepository.rdfs Structure RDFSNamespace uri has RDFSRepository SC RDFSSesameRepository More RDF(S) Repositories here to be added For example:RDFSJenaRepository SC SC SC RDFSSesameFileRepository file RDFSSesameMemoryRepository RDFSSesameRemoteRepository user password SC SC RDFSSesameHTTPRepository url RDFSSesameRMIRepository rmiuri GGF16, Athens, 15th Feb 2006
RDFSRepository.rdf example Configuration <?xml version="1.0" encoding="WINDOWS-1252"?> <rdf:RDF xmlns:rdfs_repos="http://wsdaiordfs.eu.ist.ontogrid/RDFSRepository#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"> <rdf:Description rdf:about="http://wsdaiordfs.eu.ist.ontogrid/RDFSRepository#civil_file"> <rdfs:comment>A testing file</rdfs:comment> <rdfs:label>civil_file</rdfs:label> <rdfs_repos:has rdf:resource="http://wsdaiordfs.eu.ist.ontogrid/RDFSRepository#civil"/> <rdfs_repos:file>/etc/ws-daio-rdfs/Civil_Personality.rdfs</rdfs_repos:file> <rdf:type rdf:resource="http://wsdaiordfs.eu.ist.ontogrid/RDFSRepository#RDFSSesameFileRepository"/> </rdf:Description> <rdf:Description rdf:about="http://wsdaiordfs.eu.ist.ontogrid/RDFSRepository#civil"> <rdfs:comment>An example namespace.</rdfs:comment> <rdfs:label>civil</rdfs:label> <rdfs_repos:uri>http://webode.dia.fi.upm.es/RDFS/Civil_Personality#</rdfs_repos:uri> <rdf:type rdf:resource="http://wsdaiordfs.eu.ist.ontogrid/RDFSRepository#RDFSNamespace"/> </rdf:Description> </rdf:RDF> GGF16, Athens, 15th Feb 2006
Ongoing development workplan • First spec for WS-DAIOnt • Ontogrid deliverable d3.1 • WS-DAIOnt-RDF(S) implementation • access to RDF(S) ontologies… • … stored in Sesame (download it !!) • … stored in Jena (July 2006) • Spec at the end of (April 2006) • WS-DAIOnt-OWL • spec & first implementation (December 2006) • Provide seamless access to both RDF(S) and OWL (Aug. 07) GGF16, Athens, 15th Feb 2006
Use WS-DAIOnt-RDF(S)! available at:www.ontogrid.net Feedback to: mesteban@fi.upm.es omunoz@delicias.dia.fi.upm.es Acknowledgements to the consortium GGF16, Athens, 15th Feb 2006