Graph Search

Simple Semantic Web Architecture and Protocol

Graph Search

The following form can be used as a user interface to the programmatic support for semantically searching for SSWAP resources in the Knowledge Base.

Semantic graph searching allows you to search the Knowledge Base without a browser by sending the queryForResources service a SSWAP-compliant query graph. The service will return all resources that are the same class or a:

subclass of the query graph's sswap:Resource, and
superclass of the query graph's sswap:Subject, and
subclass of the query graphs's sswap:Object.

So in this manner you are finding all services that are tagged as at least as specific as you want (and maybe more specific); that operate on data that is guaranteed to subsume what you have (and may operate on more general data); and return data that is at least as specific as you requested (and maybe more specific). This is the power of semantic searching.

The text area is initially prepopulated with an example graph that will search for all resources that return data of type taxa:Taxa or a subclass.

The service returns a SSWAP response graph. Checking the "Format output for viewing in browser" box demonstrates SSWAP's support for redirection to independent presentation layers (using the sswap:outputURI predicate; See sswap:Resource).

Type or paste a graph, in RDF/XML format, into the area below and press the "Search" button:

Format output for viewing in browser

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rdf:RDF [
    <!ENTITY rdf   "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
    <!ENTITY xsd   "http://www.w3.org/2001/XMLSchema#">
    <!ENTITY owl   "http://www.w3.org/2002/07/owl#">
    <!ENTITY sswap "http://sswapmeet.sswap.info/sswap/">
    <!ENTITY taxa  "http://sswapmeet.sswap.info/taxa/">
]>

<rdf:RDF xmlns:rdf   = "&rdf;"
         xmlns:xsd   = "&xsd;"
         xmlns:owl   = "&owl;"
         xmlns:sswap = "&sswap;"
         xmlns:taxa  = "&taxa;"
     >

<!--
    Import the declarations of the SSWAP protocol since OWL-DL
    requires that all terms be declared.

See http://sswap.info/protocol.jsp for a clickable protocol.
    See http://sswapmeet.sswap.info/sswap/owlDoc for the OWL Docs.
    -->
    <owl:Ontology rdf:about="&sswap;owlOntology">
        <owl:imports rdf:resource="&sswap;owlOntology"/>
    </owl:Ontology>

<!--
    For this file to be stand-alone OWL-DL, all terms be declared.  So either
    declare each external term here indepedent of its own definition file, or
    assert each resource to be an owl:Ontology and import them.  The owlImports
    file (when/if it exists) should do a cascading import on all terms.

If you don't want to import an entire ontology of terms (for example,
    because of a very large ontology), you can declare terms only as you
    need them.  For example:
        <owl:Class rdf:about="&taxa;Taxa"/>
        ...
        <rdf:type rdf:resource="&taxa;Taxa"/>

or in-line when using the term as:
        ...
        <rdf:type>
            <owl:Class rdf:about="&taxa;Taxa"/>
        </rdf:type>

-->
    <owl:Ontology rdf:about="&taxa;owlImports">
        <owl:imports rdf:resource="&taxa;owlImports"/>
    </owl:Ontology>

<sswap:Resource>

<!--
      The query graph.  Here we ask for all resources that accept anything
      (the unqualified sswap:Subject node) and return data of type
      taxa:Taxa (the class on the sswap:Object node).

Another common example is to qualify the sswap:Subject node with the
      class of the data you have and leave the sswap:Object node unqualified;
      i.e., find me all resources that work on my data.

Semantic searching will return all resources that are a *superclass* of
      the sswap:Subject and a *subclass* of the sswap:Object.  A class is
      always considered a sub/super-class of itself.

Thus if finds all resources that operate on your data or a more
      generalization of it, and all resources that return the data type you
      want, or more specific (more property details).

Example: typing the sswap:Subject as type Mammal, would return all
      services that operate on Mammals and all superclasses of Mammal, such
      as Animals.  As a superclass, it is guaranteed to have all the properties
      of the subclass, so the service is guaranteed to be able to operate on
      your data.  Similarly, typing the sswap:Object as type Animal would
      return all services that return Animals, as well as all subclasses of
      Animal such as Mammal.  Returing more specific (detailed) data is
      acceptable, becase as subclasses of your query, the data is guaranteed
      to satisfy the properties you requested.
      -->
      <sswap:operatesOn>
        <sswap:Graph>
          <sswap:hasMapping>
            <sswap:Subject>
                <sswap:mapsTo>
                  <sswap:Object>
                     <rdf:type rdf:resource="&taxa;Taxa"/>
                  </sswap:Object>
                </sswap:mapsTo>
            </sswap:Subject>
          </sswap:hasMapping>
        </sswap:Graph>
      </sswap:operatesOn>

</sswap:Resource>

</rdf:RDF>

Home Protocol Ontologies About VPIN
Forum Publish Resources Developers' Page Contact Us

SSWAP 8.07 • 14 Jul 2008