OntologySummit2011: Application Framework Synthesis    (2LKF)

Ontology Usage Framework    (2LKE)

Co-Champions: MichaelGruninger, MichaelUschold, NicolaGuarino    (2SUO)

The objective of the framework is to provide a common terminology for describing applications of ontologies and the benefits that ontologies deliver within these applications. In addition to classifying ontology applications, this provides the basis for benchmarks and the ability to compare different applications of ontologies.    (2S4B)

Dimensions    (2S4C)

Functionality    (2S4D)

How are the ontologies used?    (2S4E)

(omv:IntegrationTask, omv:MatchingTask)    (2SJE)

(omv:QueryFormulationTask, omv:QueryRewritingTask)    (2SJF)

(omv:SearchTask, omv:FilteringTask, omv:IndexingTask, omv:AnnotationTask)    (2SJG)

(omv:ConfigurationTask)    (2SJH)

(omv:MediationTask, omv:PersonalizationTask)    (2SJI)

Architecture    (2S4K)

Are the ontologies being applied to a single system or are they being used among multiple systems?    (2S4L)

When are the ontologies used?    (2S4M)

Are the ontologies used at design time for the system or are they used by the system at runtime?    (2S4N)

Who is using the ontologies?    (2S4O)

What ontologies are used?    (2S4U)

Problem addressed    (2S4V)

Why are the ontologies being used?    (2S4W)

Benefit    (2S4X)

What is the impact of the ontologies on the functional/nonfunctional requirements of existing system?    (2S4Y)

The value metrics for evaluating the benefits associated with nonfunctional requirements are the same metrics used for nonfunctional requirements themselves.    (2S51)

Enterprise Context    (2S52)

 .    (2S57)

An Initial Classification of Ontology Applications    (2S58)

We can use the above "dimensions" to identify the following classes of applications.    (2S59)

Integration    (2S5A)

In this class of applications, the primary functionality is the matching and mapping of concepts, while the primary architecture is within a set of multiple systems. Ontologies are typically used at runtime by application developers (who are in the best position to write translators among the systems).    (2S5B)

Examples: web service composition, mashups, information aggregation, data fusion, linked data    (2S5D)

Examples: applications of biomedical ontologies    (2S5F)

Decision Support    (2S5I)

In this class of applications, automated inference is the primary functionality. Ontologies are used at runtime, typically by knowledge workers and application users. With respect to the architecture, ontologies are used within a single system.    (2S5J)

Examples of automated theorem provers: Racer, Prover9    (2S5L)

Examples: temporal reasoners, scheduling algorithms    (2S5N)

Semantic Augmentation    (2S5P)

Applications in this class focus on using the ontologies as the basis for specification within a single system. As a result, the ontologies are used primarily at runtime by knowledge workers and application developers.    (2S5Q)

Examples: information retrieval, NLP    (2S5S)

Examples: Units of Measure, CL axiomatization of UML    (2S5Y)

Knowledge Management    (2S60)

In this class of applications, knowledge workers use ontologies for classification within a single system.    (2S61)

Examples: Indexing, data warehouses, semantic annotation    (2S64)

 --    (2SUP)
 A discussion of the range of uses of the term "ontology" can be found in the Communique for Ontology Summit 2007.
 (http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2007_Communique)    (2SUQ)
 maintained by the Track-1 champions ... please do not edit    (2LKG)