1 / 1

Overview

Evaluating Semantic Web Instance Data. Li Ding, Jiao Tao and Deborah L. McGuinness Rensselaer Polytechnic Institute, Troy, NY 12180, USA. Evaluation Architecture. Overview. Motivation We want to make sure the instance data really follows the ontology and the application requirements

trina
Download Presentation

Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Evaluating Semantic Web Instance Data Li Ding, Jiao Tao and Deborah L. McGuinness Rensselaer Polytechnic Institute, Troy, NY 12180, USA Evaluation Architecture Overview • Motivation • We want to make sure the instance data reallyfollows the ontology and the application requirements • Challenges • The gap between the assumptions using by semantic web community and real-world applications • Solution • Provide a service-oriented instance evaluation environment • Check the potential issues and report them as warnings to bridge above gap • Online demo: http://onto.rpi.edu/demo/oie/ Evaluation reports URI or text of RDF document Semantic web data Evaluation services Optional ontologies RDF parsing and validation Instance data Referenced ontology resolution OWL semantics validation Referenced ontologies Application-specific issues evaluation Issues in Instance Data Example Walkthrough • Syntax errors (SE) • OWL semantic inconsistency (OSI) • Issues related to individual’s type • Unexpected individual type (UIT) • Redundant individual type (RIT) • Non-specific individual type (NSIT) • Issues related to individual’s property • Missing property value (MPV) • Excessive property value (EPV) • Other Issues • Naming conventions • Missing annotations • Load and parse wine instance data (D) SE (missing “/” in the last markup on line 2) • <wine:Zinfandel rdf:about="#W3"> • <wine:hasMaker> <wine:Winery rdf:about="#Elyse" /> <wine:hasMaker> • </wine:Zinfandel> Is D syntactically correct? Instance Data W1 wine:hasColor rdf:type wine:Red wine:Zinfandel OSI owl:disjointWith EarlyHarvest LateHarvest rdf:type rdf:type W 2. Load wine ontology (O) Is O reachable and correct? Wine Ontology wine:Zinfandel wine:Red owl:equivalentClass rdfs:subClassOf owl:intersectionOf owl:cardinality "1" UIT rdf:rest rdfs:range hasColor WineColor WineSugar rdfs:subClassOf rdf:first owl:onProperty wine:Wine wine:hasColor rdf:rest rdf:type hasColor W Sweet owl:cardinality rdfs:subClassOf "1" owl:onProperty wine:hasMaker RIT rdfs:subClassOf Zinfandel Wine rdf:type rdf:type W 3. Derive the inferred model of D and O ( Inf[D+O] ) NSIT rdf:type W Wine Is D+O logical consistent (using Pellet OWL-DL reasoner)? rdfs:subClassOf rdfs:subClassOf Merlot Zinfandel 4. Check application-specific issues owl:cardinality EPV MPV "1" owl:cardinality "1" owl:onProperty hasColor owl:onProperty hasMaker rdf:type rdf:type owl:Restriction owl:Restriction rdfs:subClassOf rdfs:subClassOf Wine Wine Red hasColor W W White rdf:type rdf:type hasColor TW funding from: DARPA, NSF, IARPA, ARL, Lockheed Martin, SRI, Fujitsu, IBM

More Related