SeSF Use Cases

Printer-friendly version

Modularization Use Cases

  • The pattern for most modularization use cases is "Retrieve some subset of a knowledge based on given criteria".
  • There are a wide range of criteria. In some cases, the criteria is very specific, such as retrieving an ontological framework for a web application framework. Other times, the criteria are less strict; a subset that relates to a particular term or set of terms may be requested; maybe the user wants the entire knowledge base, separated into modules based on some additional criteria. The list can go on.

Application Integration

  • Framework F was designed to provide some service to a variety of web applications. Concurrently, web application A was developed that used framework F. Framework F is powered by a knowledge base Ka containing framework component terms and definitions, as well as application specific knowledge for A. The developers of F and A provide an ontology FOa, that serializes the knowledge in Ka.
  • A team would like to develop web application B that uses framework F. They must construct ontology FOb, which defines the appropriate terms for F as well as the knowledge required for the extensions for application B. The ontology developer for web application B would like to retrieve the component of Ka, call it FO, that contains only the minimum knowledge required for framework F to operate, the framework or application ontology.
  • S2S provides a specific example of this. The S2S framework powers the S2S application used for searching oceanographic data repositories. Rather than contributing to the S2S application, a developer may wish to reuse the S2S framework. In order to do that, an ontology developer will need to take the S2S "framework ontology" and extend it to fit the specifications of the new application. A modularization framework should provide the ability to construct a framework ontology from a knowledge base.

Vocabulary Reuse

  • Some knowledge base K hosts an ontology V, used to describes different components in a domain D. An ontology developer is interested in reusing a particular component C to create a new knowledge base.
  • There are various criteria for what constitutes the knowledge required to describe component C. In some cases, a hierarchal vocabulary may be requested (an RDFS case); in other cases, terms in related restriction axioms may be a part of component C (an OWL case).
  • The VSTO instrument vocabulary is one example. The VSTO ontology includes a variety of terms that describe the domain of solar-terrestrial physics. Someone developing a new application may decide that the VSTO instrument hierarchy, defining classes of instruments in the domain, is sufficient for categorizing the corpus of instrument metadata they provide. A modularization framework could construct the "primitive tree" ontologies for some class, C (in this case, instrument).

Expressivity Limits

  • Some knowledge base K contains an OWL Full ontology. The users would like to reason over a subset of all axioms in K that use descriptive logic, call this set K-DL. A modularization framework could construct ontologies that were strictly compatible with a subset of OWL (different expressivities, OWL "flavors").

Domain Specific Use Cases