DIG 2.0 High-Level Overview

This version:
http://ect.bell-labs.com/who/pfps/dig/overview.html
Authors:
Peter F. Patel-Schneider, Bell labs Research

Abstract

DIG 2.0 provides a unified way of interacting with Description Logic reasoners. At a high level the interface consists simply of sending XML messages to the reasoner, which responds as appropriate.


General Interface

The Description Logic Interface 2.0 (DIG 2.0) provides a uniform way of interacting with Description Logic reasoners. The reasoner accepts HTTP POST requests and responds as appropriate. The content of these requests are XML elements defined by an XML Schema.

Core Functionality

The core functionality of DIG 2.0 permits a client to tell the reasoner axioms that make up a knowledge base in a variant of the SROIQDn- Description Logic and pose semantic queries against that knowledge base. [PFPS: Need to check to make sure that Dn- is the correct qualifier.] This Description Logic was chosen for the core of DIG 2.0 because it is the Description Logic underlying the OWL 1.1 language.

As far as DIG 2.0 is concerned, then, a knowledge base is nothing more than a bag of axioms. A DIG 2.0 server is responsible for parsing the axioms it receives and answering queries against the resultant knowledge base. The server is also responsible for responding appropriately when it encounters syntactic or semantic problems in its input.

The core functionality of DIG 2.0 is completely described in the DIG 2.0 Core document. The XML Schema for the core is provided in the DIG 2.0 Core XML Schema.

Unusual Features of the DIG 2.0 Description Language

Because the DIG 2.0 Description Logic mirrors the OWL 1.1 language it has a couple unusual features.

Punning and Names in DIG 2.0

One unusual feature of the DIG 2.0 Description Logic is its use of what is generally called "punning". The basic idea is that each name in a DIG 2.0 knowledge base can be used as the name of any or all of a datatype property, an object property, a class, a datatype, and an individual at the same time. However, the all five of these uses are completely independent. (This is very different from the situation in RDF, for example.)

Punning in DIG 2.0 knowledge bases eliminates the need for introducing names in "def" statements. In fact, the DIG 2.0 syntax has been chosen so that constructs that use names provide as well information about how the name is used. (In this way DIG 2.0 is slightly different from the OWL 1.1 abstract syntax.) Therefore the "def" statements from DIG 1.1 are deprecated in DIG 2.0 and DIG 2.0 reasoners are free to ignore such statements.

XML Schema Datatypes in DIG 2.0

The DIG 2.0 Description Logic incorporates a datatype feature. As in OWL 1.1, the datatypes here are taken from XML Schema Datatypes. [More is needed here.]

Extensibility

Different Description Logic reasoners support different Description Logics and different reasoning factilities. To partly support these differences, DIG 2.0 provides an extensibility mechanism. There is a document describing the rationale behind the extension mechanism.

A DIG 2.0 extension consists of two documents, 1/ an XML Schema document defining the syntax of the messages in the extension, and 2/ an HTML document providing the remainder of the syntax and sufficient information about the meaning of these messages for correct implementations to be built. Both documents must be available on the web, and their URIs must differ only in their extension. [Note: Can the two documents share a URI and be distinguished by content negotiation?] Although it is not a formal requirement of the DIG 2.0 extensibility mechanism, it is expected that the XML schemas will define the syntax of extensions as extensions of XML schemas for other DIG 2.0 extensions as much as possible.

A standard DIG 2.0 extension is simply an extension whose URI starts with the standard DIG 2.0 URI prefix, namely "http://dl.kr.org/dig/dig2.0/". As can be seen from the above, the core of DIG 2.0 is in the form of a standard DIG 2.0 extension.

It is possible for DIG 2.0 "extensions" to define subsets of the core DIG 2.0 functionality.

Accessing Told Information

Sometimes it is very useful to be able to access the unprocessed information sent to a Description Logic reasoner. (For example, when debugging a knowledge base that was accessed over the Web or if several clients are feeding information to the reasoner.)

To this end, one of the standard DIG 2.0 extensions provides the ability to retrieve the information that has been explicitly given to the reasoner ("told") as axioms. The simplest form of this extension returns axioms that explicitly mention at top level a named class, property, or individual.

There is a draft document describing the told access extension.

Retracting Information

The core DIG 2.0 functionality builds up a knowledge base monotonically. The only facility for removing information involves starting over from an empty knowledge base. A DIG 2.0 extension provides a simple method for retracting information from a knowledge base.

In this retraction extension, only top-level axioms that had been previously added to the knowledge base can be retracted. The axioms are identified either via identification tags associated with axioms when they were added to the knowledge base or by tags associated with retrieved told information.

There is a draft document describing the retraction extension.