index.html 59.6 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Web Ontology Language (OWL) Use Cases and Requirements</title>
<meta name="RCSId" content="$Id: Overview.html,v 1.8 2003/03/31 23:58:56 connolly Exp $"/>
<style type="text/css">
CODE {
  FONT-FAMILY: monospace
}
</style>

<link href="http://www.w3.org/StyleSheets/TR/W3C-WD.css"
type="text/css" rel="stylesheet" />
</head>
<body>
<div class="head"><a href="http://www.w3.org/"><img height="48"
alt="W3C" src="http://www.w3.org/Icons/w3c_home" width="72" border="0" /></a>

<h1>Web Ontology Language (OWL) Use Cases and Requirements</h1>

<h2>W3C Working Draft 31 March 2003</h2>

<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/2003/WD-webont-req-20030331/">http://www.w3.org/TR/2003/WD-webont-req-20030331/</a>
</dd>

<dt>Latest version:</dt>
<dd><a href="http://www.w3.org/TR/webont-req/">http://www.w3.org/TR/webont-req/</a>
</dd>

<dt>Previous version:</dt>
<dd><a href="http://www.w3.org/TR/2003/WD-webont-req-20030203/">http://www.w3.org/TR/2003/WD-webont-req-20030203/</a>
</dd>

<dt>Editor:</dt>

<dd>
Jeff Heflin (Lehigh University)
<a href="mailto:heflin@cse.lehigh.edu">heflin@cse.lehigh.edu</a>
</dd>
</dl>

<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2003 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup>
(<a href="http://www.lcs.mit.edu/"><acronym title="Massachusetts Institute of
Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym
title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>),
All Rights Reserved. W3C
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
<a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> and <a
href="http://www.w3.org/Consortium/Legal/copyright-software">software
            licensing</a> rules apply.</p>

<hr title="Separator for header" />
</div>

<h2><a id="abstract" name="abstract">Abstract</a></h2>

<p>This document specifies usage scenarios, goals and requirements
for a web ontology language. An ontology formally
defines a common set of terms that are used to describe and
represent a domain. Ontologies can be used by automated tools to
power advanced services such as more accurate Web search,
intelligent software agents and knowledge management.</p>


<div>
<h2><a id="status" name="status">Status of this document</a></h2>

<p>This is a <a
href="http://www.w3.org/Consortium/Process-20010719/tr.html#last-call">Last
Call Working Draft</a>. The <a
href="http://www.w3.org/TR/2002/WD-webont-req-20020307/">first release
of this document</a> was 7 March 2002 and the <a
href="http://www.w3.org/2001/sw/WebOnt">Web Ontology Working Group</a>
has made its best effort to address <a
href="http://lists.w3.org/Archives/Public/public-webont-comments/">comments
recieved</a> since then, releasing several drafts meanwhile.  The
working group seeks confirmation that comments have been addressed to
the satisfaction of the community.</p>

<p>This revision reflects refinements to requirements as the working
group resolved <a
href="http://www.w3.org/2001/sw/WebOnt/webont-issues.html">issues with
the requirements and design</a>.  Note the distinction between
requirements that the Working Group accepted as constraints on the
design versus <a href="#section-objectives">objectives</a> that were
noted as desireable but not accepted as constraints.</p>

<p>Requests for significant changes to the requirements are not
anticipated and will be evaluated in the context of the scope and
schedule of the <a href="http://www.w3.org/2001/sw/WebOnt/charter">Web
Ontology Working Group charter</a> and other plans for the <a
href="http://www.w3.org/2001/sw/">W3C Semantic Web Activity</a> (<a
href="http://www.w3.org/2001/sw/Activity">Activity Statement</a>).</p>

<p>Comments on this document are due <span class="commentsDue date">9
May 2003</span>. They should be sent to <a
href="mailto:public-webont-comments@w3.org">public-webont-comments@w3.org</a>,
a mailing list with a <a
href="http://lists.w3.org/Archives/Public/public-webont-comments/">public
archive</a>.  General discussion of related technology is welcome in
the mailing list <a
href="mailto:w3c-rdf-logic@w3.org">w3c-rdf-logic@w3.org</a>, which
also has a <a
href="http://lists.w3.org/Archives/Public/www-rdf-logic/">public
archive</a>.
</p>

<p>A list of <a rel="disclosure"
href="http://www.w3.org/2001/sw/WebOnt/discl">patent disclosures
related to this work</a> is maintained by W3C, regardless of whether
any such disclosures have been made or not.</p>

<p>This is a W3C Working Draft for review by W3C members and other
interested parties. It is a draft document and may be updated,
replaced, or obsoleted by other documents at any time. It is
inappropriate to use W3C Working Drafts as reference materials or to
cite them as other than "work in progress." A <a
href="http://www.w3.org/TR/">list of current W3C Recommendations and
other technical documents</a> can be found at
http://www.w3.org/TR/.</p>
</div>

<h2><a id="contents" name="contents">Table of contents</a></h2>
<ul>
<li><a href="#section-introduction">
1. Introduction</a>
<ul>
<li><a href="#onto-def">
1.1 What is an ontology?</a></li>
</ul>
</li>

<li><a href="#section-use-cases">
2. Use cases</a>
<ul>
<li><a href="#usecase-portal">
2.1 Web portal</a></li>
<li><a href="#usecase-multimedia">
2.2 Multimedia collections</a></li>
<li><a href="#usecase-website">
2.3 Corporate web site management</a></li>
<li><a href="#usecase-designdoc">
2.4 Design documentation</a></li>
<li><a href="#usecase-agent">
2.5 Agents and services</a></li>
<li><a href="#usecase-ubiquitous">
2.6 Ubiquitous computing</a></li>
</ul>
</li>

<li><a href="#section-goals">
3. Goals</a><br />
<ul>
<li><a href="#goal-shared-ontologies">
3.1 Shared ontologies</a></li>
<li><a href="#goal-evolution">
3.2 Ontology evolution</a></li>
<li><a href="#goal-interoperability">
3.3 Ontology interoperability</a></li>
<li><a href="#goal-inconsistency">
3.4 Inconsistency detection</a></li>
<li><a href="#goal-balance">
3.5 Balance of expressivity and scalability</a></li>
<li><a href="#goal-ease-of-use">
3.6 Ease of use</a></li>
<li><a href="#goal-standards">
3.7 Compatibility with other standards</a></li>
<li><a href="#goal-internationalization">
3.8 Internationalization</a></li>
</ul>
</li>

<li><a href="#section-requirements">
4. Requirements</a><br/>
</li>

<li><a href="#section-objectives">
5. Objectives</a><br/>
</li>

<li><a href="#acknowledgments">
Acknowledgments</a>
</li>

</ul>

<br/>

<hr />
<h2><a id="section-introduction"
name="section-introduction"></a>1 Introduction</h2>

<p>The Semantic Web is a vision for the future of the Web in
which information is given explicit meaning, making it easier for
machines to automatically process and integrate information
available on the Web. The Semantic Web will build on XML's
ability to define customized tagging schemes and RDF's flexible
approach to representing data. The next element required for the
Semantic Web is a Web ontology language which can formally
describe the semantics of classes and properties used in web
documents. In order for machines to perform useful reasoning
tasks on these documents, the language must go beyond the basic
semantics of RDF Schema. This document will enumerate the current
requirements of such a language. It is expected that future
languages will extend this one, adding, among other things,
greater logical capabilities and the ability to establish trust
on the Semantic Web.</p>

<p>This document motivates the need for a Web ontology language
by describing six <a
href="#section-use-cases">use
cases</a>. Some of these use cases are based on efforts currently
underway in industry and academia, others demonstrate more
long-term possibilities. The use cases are followed by <a
href="#section-goals">design
goals</a> that describe high-level objectives and guidelines for
the development of the language. These design goals will be
considered when evaluating proposed features. The section on <a
href="#section-requirements">Requirements</a>
presents a set of features that should be in the language and
gives motivations for those features. The <a
href="#section-objectives">Objectives</a>
section describes a list of features that might be useful for
many use cases but may not necessarily be addressed by the
working group.</p>

<p>The <a href="http://www.w3.org/2001/sw/WebOnt/charter">
Web Ontology Working Group charter</a> tasks the group to produce
this more expressive semantics and to specify mechanisms by which
the language can provide "more complex relationships between
entities including: means to limit the properties of classes with
respect to number and type, means to infer that items with various
properties are members of a particular class, a well-defined model
of property inheritance, and similar semantic extensions to the
base languages." The detailed specification of the Web Ontology
language will take into consideration:</p>

<ul>
<li>the design goals and requirements that are contained in this
document</li>
<li>review comments on this document from public feedback,
invited experts and working group members</li>
<li>specifications of or proposals for languages that meet many
of these requirements</li>
</ul>


<h3><a id="onto-def" name="onto-def">1.1 What is an ontology?</a></h3>

<p>An ontology defines the terms used to describe and represent
an area of knowledge. Ontologies are used by people, databases,
and applications that need to share domain information (a domain
is just a specific subject area or area of knowledge, like
medicine, tool manufacturing, real estate, automobile repair,
financial management, etc.). Ontologies include computer-usable
definitions of basic concepts in the domain and the relationships
among them (note that here and throughout this document, definition
is not used in the technical sense understood by logicians).
They encode knowledge in a domain and also knowledge
that spans domains. In this way, they make that knowledge
reusable.</p>

<p>The word ontology has been used to describe artifacts with
different degrees of structure. These range from simple
taxonomies (such as the Yahoo hierarchy), to metadata schemes
(such as the Dublin Core), to logical theories. The Semantic Web
needs ontologies with a significant degree of structure. These
need to specify descriptions for the following kinds of
concepts:</p>

<ul>
<li>Classes (general things) in the many domains of interest</li>
<li>The relationships that can exist among things</li>
<li>The properties (or attributes) those things may have</li>
</ul>

<p>Ontologies are usually expressed in a logic-based language, so
that detailed, accurate, consistent, sound, and meaningful
distinctions can be made among the classes, properties, and
relations. Some ontology tools can perform automated reasoning
using the ontologies, and thus provide advanced services to
intelligent applications such as: conceptual/semantic search and
retrieval, software agents, decision support, speech and natural
language understanding, knowledge management, intelligent
databases, and electronic commerce.</p>

<p>Ontologies figure prominently in the emerging Semantic Web as
a way of representing the semantics of documents and enabling the
semantics to be used by web applications and intelligent agents.
Ontologies can prove very useful for a community as a way of
structuring and defining the meaning of the metadata terms that
are currently being collected and standardized. Using ontologies,
tomorrow's applications can be "intelligent," in the sense that
they can more accurately work at the human conceptual level.</p>

<p>Ontologies are critical for applications that want to search
across or merge information from diverse communities. Although
XML DTDs and XML Schemas are sufficient for exchanging data
between parties who have agreed to definitions beforehand, their
lack of semantics prevent machines from reliably performing this
task given new XML vocabularies. The same term may be used with
(sometimes subtle) different meaning in different contexts, and
different terms may be used for items that have the same meaning.
RDF and RDF Schema begin to approach this problem by allowing
simple semantics to be associated with identifiers. With RDF Schema, one
can define classes that may have multiple subclasses and super
classes, and can define properties, which may have sub properties,
domains, and ranges. In this sense, RDF Schema is a
simple ontology language. However, in order to achieve
interoperation between numerous, autonomously developed and
managed schemas, richer semantics are needed. For example, RDF
Schema cannot specify that the Person and Car classes are
disjoint, or that a string quartet has exactly four musicians as
members.</p>

<p>One of the goals of this document is to specify what is needed
in a Web Ontology language. These requirements will be motivated
by potential use cases and general design objectives that take
into account the difficulties in applying the standard notion of
ontologies to the unique environment of the Web.</p>


<h2><a id="section-use-cases" name="section-use-cases">2 Use cases</a></h2>
<p>Ontologies can be used to improve existing Web-based
applications and may enable new uses of the Web. In this section
we describe six representative use cases of Web ontologies. Note
that this is not an exhaustive list, but instead a cross-section
of interesting use cases.</p>


<h3><a id="usecase-portal" name="usecase-portal">2.1 Web portals</a></h3>
<p>A Web portal is a web site that provides information content on a
common topic, for example a specific city or domain of interest. A web
portal allows individuals that are interested in
the topic to receive news, find and talk to one another, build a
community, and find links to other web resources of common
interest.</p>

<p>In order for a portal to be successful, it must be a starting
place for locating interesting content. Typically this content is
submitted by members of the community, who often index it under
some subtopic. Another means of collecting content relies on the
content providers tagging the content with information that can
be used in syndicating it. Typically, this takes the form of
simple metatags that identify the topic of the content, etc.</p>

<p>However, a simple index of subject areas may not provide the
community with sufficient ability to search for the content that
its members require. In order to allow more intelligent syndication,
web portals can define an ontology for the community.
This ontology can provide a terminology for describing
content and axioms that define terms using other terms from the
ontology. For example, an ontology might include terminology such as
"journal paper," "publication," "person," and "author." This
ontology could include definitions that state things such as
"all journal papers are publications" or "the authors of all
publications are people." When combined with facts, these definitions
allow other facts that are necessarily true to be inferred. These
inferences can, in turn, allow users to obtain search results from
the portal that are impossible to obtain from conventional retrieval
systems.
Of course, such a technique relies on content providers annotating
their pages with the web ontology language, but if we assume that
these owners will try to distribute their content as widely as
possible, then we can expect that they would be willing to do
this.</p>

<p>One example of an ontology based portal is <a
href="http://www.ontoweb.org/">OntoWeb</a>. This portal serves
the academic and industry community that is interested in
ontology research. Another example of a portal that uses Semantic
Web technologies and could benefit from an ontology language is
<a href="http://dmoz.org/">The Open Directory Project</a>; a large,
comprehensive human-edited directory of the Web. It is constructed
and maintained by a vast, global community of volunteer editors.
RDF dumps of the Open Directory database are available for download.</p>


<h3><a id="usecase-multimedia" name="usecase-multimedia">
2.2 Multimedia collections</a></h3>
<p>Ontologies can be used to provide semantic annotations for collections of
images, audio, or other non-textual objects.
It is even more difficult for machines to extract
meaningful semantics from multimedia than it is to extract
semantics from natural language text. Thus, these types of resources
are typically indexed by captions or metatags. However, since
different people can describe these non-textual objects in
different ways, it is important that the search facilities go
beyond simple keyword matching. Ideally, the ontologies would
capture additional knowledge about the domain that can be used to
improve retrieval of images.</p>

<p>Multimedia ontologies can be of two types: media-specific and
content-specific. Media specific ontologies could have taxonomies of
different media types and describe properties of different media.
For example, video may include properties to identify length of
the clip and scene breaks. Content-specific ontologies could
describe the subject of the resource, such as the setting or
participants. Since such ontologies are not specific to the media,
they could be reused by other documents that deal with the same
domain. Such reuse would enhance search that was simply looking
for information on a particular subject, regardless of the
format of the resource. Searches where media type was important
could combine the media-specific and content-specific ontologies.</p>

<p>As an example of a multimedia collection, consider an archive of
images of antique furniture. An ontology of antique furniture would be
of great use in searching such an archive. A taxonomy can be used
to classify the different types of furniture. It would also be
useful if the ontology could express definitional knowledge.
For example, if an indexer selects the value "Late Georgian" for the
style/period of (say) an antique chest of drawers, it should be
possible to infer that the data element "date.created" should have a
value between 1760 and 1811 A.D. and that the "culture" is
British. Availability of this type of background knowledge
significantly increases the support that can be given for
indexing as well as for search. Another feature that could be
useful is support for the representation of default
knowledge. An example of such knowledge would be that a
"Late Georgian chest of drawers" is typically made of mahogany.
This knowledge is crucial for real semantic queries, e.g. a
user query for "antique mahogany storage furniture" could match
with images of Late Georgian chests of drawers, even if nothing
is said about wood type in the image annotation.</p>


<h3><a id="usecase-website" name="usecase-website">
2.3 Corporate web site management</a></h3>
<p>Large corporations typically have numerous web pages
concerning things like press releases, product offerings and case
studies, corporate procedures, internal product briefings and
comparisons, white papers, and process descriptions. Ontologies
can be used to index these documents and provide better means of
retrieval. Although many large organizations have a taxonomy for
organizing their information, this is often insufficient. A
single taxonomy is often limiting because many things can fall
under multiple categories. Furthermore,
the ability to search on values for different
parameters
is often more useful than a keyword search with taxonomies.</p>


<p>An ontology-enabled web site may be used by:</p>
<ul>
<li>A salesperson looking for sales collateral relevant to a
sales pursuit.</li>
<li>A technical person looking for pockets of specific
technical expertise and detailed past experience.</li>
<li>A project leader looking for past experience and templates
to support a complex, multi-phase project, both during the
proposal phase and during execution.</li>
</ul>

<p>A typical problem for each of these types of users is that
they may not share terminology with the authors of the desired
content. The salesperson may not know the technical name for
a desired feature or technical people in different fields might
use different terms for the same concept. For such problems,
it would be useful for each class of user to have different
ontologies of terms, but have each ontology interrelated so
translations can be performed automatically.</p>

<p>Another problem is framing queries at the right level of
abstraction. A project leader looking for someone with expertise
in operating systems should be able to locate an employee who
is an expert with both Unix and Windows.</p>

<p>One aspect of a large service organization is that it may have
a very broad set of capabilities. But when pursuing large
contracts these capabilities sometimes need to be assembled in
new ways. There will often be no previous single matching
project. A challenge is to reason about how past templates and
documents can be reassembled in new configurations, while
satisfying a diverse set of preconditions.</p>


<h3><a id="usecase-designdoc" name="usecase-designdoc">
2.4 Design documentation</a></h3>
<p>This use case is for a large body of engineering documentation,
such as that used by the aerospace industry. This documentation can be of
several different types, including design documentation, manufacturing
documentation, and testing documentation. These document sets each have
a hierarchical structure, but the structures differ between the sets.
There is also a set of implied axes which cross-link the documentation
sets: for example, in aerospace design documents, an item such as a wing
spar might appear in each.</p>

<p>Ontologies can be used to build an information model which allows
the exploration of the information space in terms of the items which
are represented, the associations between the items, the properties
of the items, and the links to documentation which describes and
defines them (i.e., the external justification for the existence of
the item in the model). That is to say that the ontology and taxonomy
are not independent of the physical items they represent, but may be
developed/explored in tandem.</p>

<p>A concrete example of this use case is design
documentation for the aerospace domain, where typical users include:</p>

<ul>
<li>Maintenance engineer looking for all information relating
to a particular part (e.g., "wing-spar").</li>
<li>Design engineer looking at
constraints on re-use of a particular sub-assembly.</li>
</ul>

<p>To support this kind of usage, it is important
that constraints can be defined. These constraints may be used to
enhance search or check consistency. An example of a constraint might
be:</p>

<pre>
biplane(X) => CardinalityOf(wing(X)) = 2
wingspar(X) AND wing(Y) AND isComponentOf(X,Y) => length(X) &lt; length(Y)
</pre>


<p>Another common use of this kind of ontology is to support the
visualization and editing of charts which show snapshots of the information
space centered on a particular concept (e.g., a class or instance). These
are typically activity/rule diagrams or entity-relationship diagrams. </p>


<h3><a id="usecase-agent" name="usecase-agent">2.5 Agents and services</a></h3>
<p>The Semantic Web can provide agents with the capability to
understand and integrate diverse information resources. A
specific example is that of a social activities planner, which
can take the preferences of a user (such as what kinds of films
they like, what kind of food they like to eat, etc.) and use
this information to plan the user's activities for an evening.
The task of planning these activities will depend upon the
richness of the service environment being offered and the needs
of the user. During the service determination / matching process,
ratings and review services may also be consulted to find closer
matches to user preferences (for example, consulting reviews and
rating of films and restaurants to find the "best").</p>

<p>This type of agent requires domain ontologies that represent
the terms for restaurants, hotels, etc. and service ontologies to
represent the terms used in the actual services. When building
the actual services, the information may come from a number of
sources, such as portals, service-specific sites,
reservation sites and the general Web.</p>

<a href="http://www.agentcities.org/">Agentcities</a> is an
example of an initiative that is exploring the use of agents in a
distributed service environment across the Internet. This will
involve building a network of agent platforms that represent real
or virtual cities, such as <a
href="http://sf.us.agentcities.net/">San Francisco</a> or the Bay
Area, and populating them with the services of those cities.
Initially, these services will be oriented towards business to
consumer services, such as hotels, restaurants, entertainment,
etc., but eventually, they will be expanded to include business
to business services, such as payroll, and business to enterprise
services.

<p>This will require a number of different domain and service
ontologies: Key issues include:</p>
<ul>
<li>Use and integration of multiple separate ontologies across
different domains and services</li>
<li>Distributed location of ontologies across the Internet</li>
<li>Potentially different ontologies for each domain or service
(ontology translation/cross-referencing)</li>
<li>Simple ontology representation to make the task of defining
and using ontologies easier</li>
</ul>


<h3><a id="usecase-ubiquitous" name="usecase-ubiquitous">
2.6 Ubiquitous computing</a></h3>
<p>Ubiquitous computing is an emerging paradigm of personal
computing, characterized by the shift from dedicated computing
machinery to pervasive computing capabilities embedded in our
everyday environments. Characteristic to ubiquitous computing are
small, handheld, wireless computing devices. The pervasiveness
and the wireless nature of devices require network architectures
to support automatic, ad hoc configuration. An additional reason
for development of automatic configuration is that this
technology is aimed at ordinary consumers. </p>

<p>A key technology of true <em>ad hoc</em> networks is service discovery,
functionality by which "services" (i.e., functions offered by
various devices such as cell phones, printers, sensors, etc.) can
be described, advertised, and discovered by others. All of the
current service discovery and capability description mechanisms
(e.g., Sun's JINI, Microsoft's UPnP) are based on <em>ad hoc</em>
representation schemes and rely heavily on standardization (i.e.,
on a priori identification of all those things one would want to
communicate or discuss).</p>

<p>The key issue (and goal) of ubiquitous computing is
"serendipitous interoperability," interoperability under
"unchoreographed" conditions, i.e., devices which weren't
necessarily designed to work together (such as ones built for
different purposes, by different manufacturers, at a different
time, etc.) should be able to discover each others' functionality
and be able to take advantage of it. Being able to "understand"
other devices, and reason about their services/functionality is
necessary, since full-blown ubiquitous computing scenarios will
involve dozens if not hundreds of devices, and a priori
standardizing the usage scenarios is an unmanageable task.</p>

<p>The interoperation scenarios are dynamic in nature (i.e.,
devices appear and disappear at any moment as their owners carry
them from one room or building to another) and do not involve
humans in the loop as far as (re-)configuration is concerned.</p>

<p>Given that device functionality can be modeled as web
services, the needs for this use case are somewhat similar to the
needs for <a href="http://www.daml.org/services/">DAML-S</a>
(particularly the issues surrounding the <a
href="http://www.daml.org/services/daml-s/2001/10/rationale.html#expressiveness">
expressiveness</a> of the language).</p>

<p>The tasks involved in the utilization of services involve
discovery, contracting, and composition. The contracting of
services may involve representing information about security,
privacy and trust, as well as about compensation-related details
(the provider of a service may have to be compensated for
services rendered). In particular, it is a goal that corporate or organizational
security policies be expressed in application-neutral form, thus enabling
constraint representation across the diversity of enforcement mechanisms
(e.g., firewalls, filters/scanners, traffic monitors, application-level
routers and load-balancers).</p>

<p>Given that RDF-based schemes for representing information
about device characteristics have started to be adopted (namely,
<a href="http://www.w3.org/Mobile/CCPP/">W3C's Composite
Capability/Preference Profile (CC/PP)</a> and WAP Forum's
<a href="http://www1.wapforum.org/tech/documents/WAP-248-UAProf-20011020-a.pdf">User
Agent Profile</a> or UAProf), an additional need is
compatibility with RDF at some level.</p>


<h2><a id="section-goals" name="section-goals">3 Design goals</a></h2>
<p>Design goals describe general motivations for the language
that do not necessarily result from any single use case. In this
section, we describe eight design goals for the Web ontology
language. For each goal, we describe the tasks it supports and
explain the rationale for the goal. We also describe the degree
to which RDF and RDF Schema supports the goal.</p>


<h3><a id="goal-shared-ontologies" name="goal-shared-ontologies"></a>
3.1 Shared ontologies</h3>
<p>Ontologies should be publicly available and different data
sources should be able to commit to the same ontology for shared
meaning. Also, ontologies should be able to extend other
ontologies in order to provide additional definitions.</p>

<p><b>Supported Tasks:</b><br />
Any use case in which distributed data sources use shared
terminology.</p>

<p><b>Justification:</b><br />
Interoperability requires agreements on the definitions of
identifiers. Ontologies can provide standard sets of identifiers and formal
descriptions of those identifiers. Data sources that commit to the same
ontology explicitly agree to use the same identifiers with the same
meanings.</p>
<p>Often, shared ontologies are not sufficient. An organization
may find that an existing ontology provides 90% of what it needs,
but the remaining 10% is critical. In such cases, the
organization should not have to create a new ontology from
scratch, but instead be able to create an ontology which extends
an existing ontology and adds any desired identifiers and
definitions.</p>

<p><b>RDF(S) Support:</b><br />
In RDF, each schema has its own namespace identified by a URI.
Each resource in the schema has an ID, and a globally unique
identifier can be created by combining the ID with the
URI of the namespace. Any resource that uses this URI
references the term as defined in that schema. However, RDF is
unclear on the definition of a term that has partial definitions
in multiple schemas. The specification appears to assume that the
definition is the union of all descriptions that use the same
identifier, regardless of source. However, this may lead to
problems in a distributed environment, where some schemas may
contain incorrect or false definitions. There is no way in RDF
for a resource to indicate which set of definitions it agrees
to.</p>


<h3><a id="goal-evolution" name="goal-evolution"></a>
3.2 Ontology evolution</h3>
<p>An ontology may change during its lifetime. A data source should specify
the version of an ontology to which it commits.</p>

<p>An important issue
is whether or not documents that commit to one version
of an ontology are compatible with those that commit to another.
Both compatible and incompatible revisions should be allowed, but
it should be possible to distinguish between the two. Note that
since formal descriptions only provide approximations for the
meanings of most identifiers,
it is possible for a revision to change the intended meaning of an
identifier without changing its formal description. Thus determining
semantic backwards-compatibility requires more than a simple
comparison of term descriptions. As such, the ontology author
needs to be able to indicate such changes explicitly.</p>

<p><b>Supported Tasks:</b><br />
Any use case in which the ontology could potentially change,
and in particular those in which the owner of the ontology is
different from the data providers.</p>

<p><b>Justification:</b><br />
Since the web is constantly growing and changing, we must
expect ontologies to change as well. Ontologies may need to
change because there were errors in prior versions, because a new
way of modeling the domain is preferred, or because
new terminology has been created (e.g.,
as the result of the invention of new technology). A web ontology
language must be able to accommodate ontology revision. Note that
ontology evolution is different from ontology extension, which
does not change the original ontology.
</p>

<p><b>RDF(S) Support:</b><br />
The RDF Schema Specification recommends that each version of a
schema should be a separate resource with its own URI. The
rdfs:subClassOf and rdfs:subPropertyOf properties can be used to
relate new versions of classes and properties to older versions.
However, this has the drawback that incorrect definitions cannot
be retracted. For example, assume that in schema v1, v1:Dolphin
is a rdfs:subClassOf v1:Fish. When this mistake is noticed, the
new version of the schema, v2, says that v2:Dolphin is a
rdfs:subClassOf v2:Mammal. However, if we make v2:Dolphin a
rdfs:subClassOf v1:Dolphin, then we also say that v2:Dolphin is
an rdfs:subClassOf v1:Fish which perpetuates the error.</p>


<h3><a id="goal-interoperability" name="goal-interoperability"></a>
3.3 Ontology interoperability</h3>
<p>Different ontologies may model the same concepts in different
ways. The language should provide primitives for relating
different representations, thus allowing data to be converted to
different ontologies and enabling a "web of ontologies."</p>

<p><b>Supported Tasks:</b><br />
Any use case in which data from different providers with
different terminologies must be integrated.</p>

<p><b>Justification:</b><br />
Although shared ontologies and ontology extension allow a
certain degree of interoperability between different
organizations and domains, there are often cases where there are
multiple ways to model the same information. This may be due to
differences in the perspectives of different organizations,
different professions, different nationalities, etc. In order for
machines to be able to integrate information that commits to
heterogeneous ontologies, there need to be primitives that allow
ontologies to map concepts to their equivalents in other ontologies.</p>

<p><b>RDF(S) Support:</b><br />
RDF provides minimal support for interoperability by means of
the rdfs:subClassOf and rdfs:subPropertyOf properties.</p>


<h3><a id="goal-inconsistency" name="goal-inconsistency"></a>
3.4 Inconsistency detection</h3>
<p>Different ontologies or data sources may be contradictory. It
should be possible to detect these inconsistencies.</p>

<p><b>Supported Tasks:</b><br />
Any use cases in which decentralization of data and lack of
controlling authority can lead to conflicts in the data. Any
ontology extension task that may result in incoherent
descriptions (possibly by extending an ontology in a way that
generated an over constrained concept).</p>

<p><b>Justification:</b><br />
The Web is decentralized, allowing anyone to say anything. As
a result, different viewpoints may be contradictory, or even
false information may be provided. In order to prevent agents
from combining incompatible data or from taking consistent data
and evolving it into an inconsistent state, it is important that
inconsistencies can be detected automatically.</p>

<p><b>RDF(S) Support:</b><br />
RDF and RDFS do not allow inconsistencies to be expressed.</p>


<h3><a id="goal-balance" name="goal-balance"></a>
3.5 Balance of expressivity and scalability</h3>
<p>The language should be able to express a wide variety of
knowledge, but should also provide for efficient means to reason
with it. Since these two requirements are typically at odds, the
goal of the web ontology language is to find a balance that
supports the ability to express the most important kinds of
knowledge.</p>

<p><b>Supported Tasks:</b><br />
Any use case that uses large ontologies or large data sets and
requires the representation of diverse knowledge.</p>

<p><b>Justification:</b><br />
There are over one billion pages on the Web, and the potential
application of the Semantic Web to embedded devices and agents
poses even larger amounts of information that must be handled.
The web ontology language should support reasoning systems that scale
well. However, the language should also be as expressive
as possible, so that users can state the kinds of knowledge that
is important to their applications.</p>

<p>Expressivity determines what can be said in the language, and
thus determines its inferential power and what reasoning
capabilities should be expected in systems that fully implement
it. An expressive language contains a rich set of primitives that
allow a wide variety of knowledge to be formalized. A language
with too little expressivity will provide too few reasoning
opportunities to be of much use and may not provide any
contribution over existing languages.</p>

<p><b>RDF(S) Support:</b><br />
RDF is very scalable (with the exception of the XML syntax
being extremely verbose) but is not very expressive.</p>


<h3><a id="goal-ease-of-use" name="goal-ease-of-use"></a>
3.6 Ease of use</h3>
<p>The language should provide a low learning barrier and have
clear concepts and meaning. The concepts should be independent
from syntax.</p>

<p><b>Supported Tasks:</b><br />
Markup and querying of semantic web documents by users, either
directly or indirectly.</p>

<p><b>Justification:</b><br />
Although ideally most users will be isolated from the language
by front end tools, the basic philosophy of the language must be
natural and easy to learn. Furthermore, early adopters, tool
developers, and power users may work directly with the syntax,
meaning human readable (and writable) syntax is desirable.</p>

<p><b>RDF(S) Support:</b><br />
RDF is fairly easy to use, but RDF Schema is more complex. The
syntax appears to be a major barrier for many.</p>


<h3><a id="goal-standards" name="goal-standards"></a>
3.7 Compatibility with other standards</h3>
<p>The language should be compatible with other
commonly used Web and industry standards. In particular, this includes XML
and related standards (such as XML Schema and RDF), and possibly other
modeling standards such as UML.</p>

<p><b>Supported Tasks:</b><br />
Exchange of ontologies and data in a standard format.</p>

<p><b>Justification:</b><br />
Compatibility with other standards eases tool
development and deployment of the language.
</p>

<p><b>RDF(S) Support:</b><br />
RDF has an XML serialization syntax.</p>


<h3><a id="goal-internationalization" name="goal-internationalization">
</a>3.8 Internationalization</h3>
<p>The language should support the development of multilingual
ontologies, and potentially provide different views of ontologies
that are appropriate for different cultures.</p>

<p><b>Supported Tasks:</b><br />
Tasks where the same ontology is used by multiple countries or
cultures.</p>

<p><b>Justification:</b><br />
The Web is an international tool. The Semantic Web should aid
in the exchange of ideas and information between different
cultures, and should thus make it easy for members of different
nations to use the same ontologies.</p>

<p><b>RDF(S) Support:</b><br />
To the extent that XML supports internationalization, so does
RDF. </p>


<h2><a id="section-requirements" name="section-requirements"></a>
4 Requirements</h2>
<p>The use cases and design goals motivate a number of
requirements for a Web Ontology language. The Working Group
currently feels that the requirements described below are
essential to the language. Each requirement includes a short
description and is motivated by one or more
design goals from the previous section.</p>


<dl>
<dt><a id="req-distinct-res" name="req-distinct-res"></a>
<b>R1. Ontologies as distinct resources</b></dt>
<dd>
<p>Ontologies must be resources that have their own unique
identifiers, such as a URI reference.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">
Shared ontologies</a></p>
</dd>


<dt><a id="req-unambigous" name="req-unambigous"></a>
<b>R2. Unambiguous concept referencing with URIs</b></dt>
<dd>
<p>Two concepts in different ontologies must have distinct absolute
identifiers (although they may have identical relative
identifiers). It must be possible to uniquely identify a concept in
an ontology using a URI reference.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">Shared ontologies</a>,
<a href="#goal-interoperability">Ontology interoperability</a>
</p>
</dd>


<dt><a id="req-explicit" name="req-explicit"></a>
<b>R3. Explicit ontology extension</b></dt>
<dd>
<p>Ontologies must be able to explicitly extend other ontologies
in order to reuse concepts while adding new classes and properties.
Ontology extension must be a transitive relation; if ontology A
extends ontology B, and ontology B extends ontology C, then
ontology A implicitly extends ontology C as well.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">Shared ontologies</a></p>
</dd>


<dt><a id="req-commit" name="req-commit"></a>
<b>R4. Commitment to ontologies</b></dt>
<dd>
<p>Resources must be able to explicitly commit to specific
ontologies, indicating precisely which set of definitions and
assumptions are made.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">Shared ontologies</a></p>
</dd>


<dt><a id="req-metadata" name="req-metadata"></a>
<b>R5. Ontology metadata</b></dt>
<dd>
<p>It must be possible to provide meta-data for each ontology,
such as author, publish-date, etc. These properties may
or may not be borrowed from the Dublin Core element set.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">Shared ontologies</a></p>
</dd>


<dt><a id="req-versioning" name="req-versioning"></a>
<b>R6. Versioning information</b></dt>
<dd>
<p>The language must provide features for comparing and relating
different versions of the same ontology. This should include
features for relating revisions to prior versions, explicit
statements of backwards-compatibility, and the ability to
deprecate identifiers (i.e., to state they are available for
backwards-compatibility only, and should not be used in new
applications/documents.)</p>

<p><b>Motivation:</b>
<a href="#goal-evolution">Ontology evolution</a></p>
</dd>


<dt><a id="req-class-definition" name="req-class-definition"></a>
<b>R7. Class definition primitives</b></dt>
<dd>
<p>The language must be able to express complex definitions of
classes. This includes, but is not limited to, sub classing and
Boolean combinations of class expressions
(i.e., intersection, union, and complement).</p>

<p><b>Motivation:</b>
<a href="#goal-balance">Balance of expressivity and scalability</a>,
<a href="#goal-interoperability">Ontology interoperability</a>,
<a href="#goal-inconsistency">Inconsistency detection</a>
</p>
</dd>


<dt><a id="req-property-definition" name="req-property-definition"></a>
<b>R8. Property definition primitives</b></dt>
<dd>
<p>The language must be able to express the definitions of
properties. This includes, but is not limited to, sub properties,
domain and range constraints, transitivity, and inverse
properties.</p>

<p><b>Motivation:</b>
<a href="#goal-balance">Balance of expressivity and scalability</a>,
<a href="#goal-interoperability">Ontology interoperability</a>,
<a href="#goal-inconsistency">Inconsistency detection</a>
</p>
</dd>


<dt><a id="req-datatypes" name="req-datatypes"></a>
<b>R9. Data types</b></dt>
<dd>
<p>The language must provide a set of standard data types. These
data types may be based on XML Schema data types.</p>

<p><b>Motivation:</b>
<a href="#goal-standards">Compatibility with other standards</a>,
<a href="#goal-ease-of-use">Ease of use</a></p>
</dd>


<dt><a id="req-equivalence" name="req-equivalence"></a>
<b>R10. Class and property equivalence</b></dt>
<dd>
<p>The language must include features for stating that
two classes or properties are equivalent.</p>

<p><b>Motivation:</b>
<a href="#goal-interoperability">Ontology interoperability</a></p>
</dd>


<dt><a id="req-id-equivalence" name="req-id-equivalence"></a>
<b>R11. Individual equivalence</b></dt>
<dd>
<p>The language must include features for stating that pairs of
identifiers represent the same individual (note that consistent
with the terminology used in other OWL documents, an individual
here is any instance of an OWL class, and does not necessarily
mean a person). Due to the distributed
nature of the Web, it is likely that different identifiers will
be assigned to the same individual. The use of a standard URL
does not solve this problem, because some individuals may have
multiple URLs, such as a person who has home and work web pages
or e-mail addresses.</p>

<p><b>Motivation:</b>
<a href="#goal-interoperability">Ontology interoperability</a>
</p>
</dd>


<dt><a id="req-statement-properties" name="req-statement-properties"></a>
<b>R12. Attaching information to statements</b></dt>
<dd>
<p>The language must provide a way to allow statements to be "tagged" with
additional information such as source, timestamp, confidence level,
etc. The language need not provide a standard set of properties
that can be used in this way, but should instead provide a
general mechanism for users to attach such information.
RDF reification may be one possible way to
accommodate the requirement, although reification is a somewhat
controversial feature.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">Shared ontologies</a>,
<a href="#goal-interoperability">Ontology interoperability</a>
</p>
</dd>


<dt><a id="req-class-as-instance" name="req-class-as-instance"></a>
<b>R13. Classes as instances</b></dt>
<dd>
<p>The language must support the ability to treat classes as
instances. This is because the same concept can often be seen as
a class or an individual, depending on the perspective of the
user. For example, in a biological ontology, the class Orangutan
may have individual animals as its instances. However, the class
Orangutan may itself be an instance of the class Species. Note, that Orangutan
is not a subclass of Species, because then that would say that each
instance of Orangutan (an animal) is an instance of Species.</p>

<p><b>Motivation:</b>
<a href="#goal-interoperability">Ontology interoperability</a>
</p>
</dd>

<dt><a id="req-cardinality-constraints" name="req-cardinality-constraints"></a>
<b>R14. Cardinality constraints</b></dt>
<dd>
<p>The language must support the specification of cardinality
restrictions on properties. These restrictions set minimum and
maximum numbers of individuals that any single individual can be related
to via the specified property.</p>

<p><b>Motivation:</b>
<a href="#goal-balance">Balance of expressivity and scalability goal,</a>,
<a href="#goal-inconsistency">Inconsistency detection</a>
</p>
</dd>


<dt><a id="req-xml-syntax" name="req-xml-syntax"></a>
<b>R15. XML syntax</b></dt>
<dd>
<p>The language should have an XML serialization syntax. XML has become
 widely accepted by industry and numerous tools
for processing XML have been developed. If the web ontology
language has an XML syntax, then these tools can be extended and
reused.</p>

<p><b>Motivation:</b>
<a href="#goal-standards">Compatibility with other standards</a>
</p>
</dd>

<dt><a id="req-user-labels" name="req-user-labels"></a>
<b>R16. User-displayable labels</b></dt>
<dd>
<p>The language should support the specification of multiple alternative
user-displayable labels for the resources specified by an ontology. This can be
used, for example, to view the ontology in different natural languages.</p>

<p><b>Motivation:</b>
<a href="#goal-internationalization">Internationalization</a>,
<a href="#goal-ease-of-use">Ease of use</a>
</p>
</dd>


<dt><a id="req-character-model" name="req-character-model"></a>
<b>R17. Supporting a character model</b></dt>
<dd>
<p>The language should support the use of multilingual character
sets.</p>

<p><b>Motivation:</b>
<a href="#goal-internationalization">Internationalization</a>,
<a href="#goal-standards">Compatibility with other standards</a>
</p>
</dd>


<dt><a id="req-uniqe-unicode" name="req-uniqe-unicode"></a>
<b>R18. Supporting a uniqueness of Unicode strings</b></dt>
<dd>
<p>In some character encodings, e.g. Unicode based encodings,
there are some cases where two different character sequences look
the same and are expected, by most users, to compare equal. An
example is one using a pre-composed form (just one c-cedilla
character) and another using a decomposed form (a 'c' character
followed by a cedilla accent character). Given that the W3C I18N
WG has decided that early uniform normalization (to Unicode
Normal Form C) as the usual approach to solving this problem, any
other solution needs to be justified.</p>

<p><b>Motivation:</b>
<a href="#goal-internationalization">Internationalization</a>,
<a href="#goal-standards">Compatibility with other standards</a>
</p>
</dd>
</dl>


<h2><a id="section-objectives" name="section-objectives"></a>
5 Objectives</h2>
<p>In addition to the set of features that should be in the
language (as defined in the previous section), there are other
features that would be useful for many use cases. These features
will be addressed by the working group if possible, but the group
may decide that there are good reasons for excluding them from
the language or for leaving them to be implemented by a later
working group. Some of these objectives are not fully defined,
and as such need further clarification if they are to be
addressed by the language. Note that the order of the objectives
below does not imply relative priority or degree of consensus.</p>


<dl>
<dt><a id="obj-layering" name="obj-layering"></a>
<b>O1. Layering of language features</b></dt>
<dd>
<p>The language may support different levels of complexity for
defining ontologies. Applications can conform to a particular
layer without supporting the entire language. A guideline for
identifying layers may be based on functionality found in
different types of database and knowledge base systems.</p>

<p><b>Motivation:</b>
<a href="#goal-balance">Balance of expressivity and scalability</a></p>
</dd>


<dt><a id="obj-default-property" name="obj-default-property"></a>
<b>O2. Default property values</b></dt>
<dd>
<p>The language should support the specification of default
values for properties. Such values are useful in making
inferences about typical members of classes. However, true
default values are nonmonotonic, which can be problematic on the
Web where new information is constantly being discovered or
added. Furthermore, there is no commonly accepted method for
dealing with defaults. An alternative is for the language
specification to recommend to users how they can create their own
default mechanisms.</p>

<p><b>Motivation:</b>
<a href="#goal-balance">Balance of expressivity and scalability</a>
</p>
</dd>


<dt><a id="obj-closed-world" name="req-closed-world"></a>
<b>O3. Ability to state closed worlds</b></dt>
<dd>
<p>Due to the size and rate of change on the Web, the
<i>closed-world assumption</i> (which states that anything that
cannot not be inferred is assumed to be false) is inappropriate.
However, there are many situations where closed-world information
would be useful. Therefore, the language must be able to state that a given
ontology can be regarded as complete. This would then sanction additional
inferences to be drawn from that ontology. The precise semantics of such a
statement (and the corresponding set of inferences) remains to be defined,
but examples might include assuming complete property information about
individuals, assuming completeness of class-membership, and assuming
exhaustiveness of subclasses.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">Shared ontologies</a>,
<a href="#goal-inconsistency">Inconsistency detection</a>
</p>
</dd>


<dt><a id="obj-range-constraints" name="obj-range-constraints"></a>
<b>O4. Range constraints on data types</b></dt>
<dd>
<p>The language should support the ability to specify ranges of
values for properties. This mechanism may borrow from XML Schema
data types.</p>

<p><b>Motivation:</b>
<a href="#goal-inconsistency">Inconsistency detection</a>
</p>
</dd>


<dt><a id="obj-chained-properties" name="obj-chained-properties"></a>
<b>O5. Chained properties</b></dt>
<dd>
<p>The language may support the composition of properties in statements
about classes and properties. An example of the use of property
composition would be the assertion that a property called <i>uncleOf</i>
is the same as the composition of the <i>fatherOf</i> and <i>brotherOf</i>
properties.</p>

<p><b>Motivation:</b>
<a href="#goal-balance">Balance of expressivity and scalability</a>
</p>
</dd>


<dt><a id="obj-effective-decision-procedure" name="obj-effective-decision-procedure"></a>
<b>O6. Effective decision procedure</b></dt>
<dd>
<p>The language should be decidable.</p>

<p><b>Motivation:</b>
<a href="#goal-balance">Balance of expressivity and scalability</a>
</p>
</dd>


<dt><a id="obj-commitment" name="obj-commitment"></a>
<b>O7. Commitment to portions of ontologies</b></dt>
<dd>
<p>The language should support the ability to commit to portions
of an ontology, as well as committing to an entire ontology.
However, it is unclear what granularity should be used here.
Possible choices are to choose a subset of concepts with their entire
definitions, or to choose individual pieces of definitions. Note
that borrowing partial definitions of concepts must address the potential
interoperability problems that can arise since different applications will be
using the same identifier to mean different things.</p>

<p><b>Motivation:</b>
<a href="#goal-shared-ontologies">Shared ontologies</a></p>
</dd>


<dt><a id="obj-view" name="obj-view"></a>
<b>O8. View mechanism</b></dt>
<dd>
<p>The language should support the ability to create ontology
views, in which subsets of an ontology can be specified or concepts can
be assigned alternate names. This is particularly useful in
developing multicultural versions of an ontology. Note that this
requirement may be satisfied by having multiple ontologies and
using an ontology mapping mechanism.</p>

<p><b>Motivation:</b>
<a href="#goal-internationalization">Internationalization</a>,
<a href="#goal-interoperability">Ontology interoperability</a>
</p>
</dd>


<dt><a id="obj-digital-signature" name="obj-digital-signature"></a>
<b>O9. Integration of digital signatures</b></dt>
<dd>
<p>The W3C XML Digital Signature specification is an important building block
for communication among untrusted properties, which is important for many
ontology applications. The web ontology language should be designed in
a way that makes it straightforward to use XML Signatures.</p>

<p><b>Motivation:</b>
<a href="#goal-standards">Compatibility with other standards</a>
</p>
</dd>


<dt><a id="obj-arithmetic" name="obj-arithmetic"></a>
<b>O10. Arithmetic primitives</b></dt>
<dd>
<p>The language should support the use of arithmetic functions.
These can be used in translating between different units of
measure.</p>

<p><b>Motivation:</b>
<a href="#goal-interoperability">Ontology interoperability</a></p>
</dd>


<dt><a id="obj-string-manipulation" name="obj-string-manipulation"></a>
<b>O11. String manipulation</b></dt>
<dd>
<p>The language should support string concatenation and simple
pattern matching. These features can be used to establish
interoperability between ontologies that treat complex
information as a formatted string and those that have separate
properties for each component. For example, one ontology may
represent a person's name as a single string "lastname,
firstname," while another may have a property for each.</p>

<p><b>Motivation:</b>
<a href="#goal-interoperability">Ontology interoperability</a></p>
</dd>


<dt><a id="obj-aggregation" name="obj-aggregation"></a>
<b>O12. Aggregation and grouping</b></dt>
<dd>
<p>The language should support the ability to aggregate
information in a way similar to SQL's GROUP BY clause. It should
allow counts, sums, and other operations to be computed for each
group. This would allow interoperability between ontologies that
represented information at different levels of granularity, and
could relate things such as budget category totals to budget
line item amounts, or the number of personnel to individual data on
employees.</p>

<p><b>Motivation:</b>
<a href="#goal-interoperability">Ontology interoperability</a></p>
</dd>


<dt><a id="obj-procedural-attachment" name="obj-procedural-attachment"></a>
<b>O13. Procedural attachment</b></dt>
<dd>
<p>The language should support the use of executable code to
evaluate complex criteria. Procedural attachments greatly extend
the expressivity of the language, but are not well-suited to
formal semantics. A procedural attachment mechanism for web
ontologies should specify how to locate and execute the
procedure. One potential candidate language would be Java, which
is already well-suited to intra-platform sharing on the Web.</p>

<p><b>Motivation:</b>
<a href="#goal-interoperability">Ontology interoperability</a></p>
</dd>


<dt><a id="obj-unique-name-assumption" name="obj-unique-name-assumption"></a>
<b>O14. Local unique names assumptions</b></dt>
<dd>
<p>In general, the language will not make a <i>unique names
assumption</i>. That is, distinct identifiers are not assumed to
refer to different individuals (see <a href="#req-id-equivalence">Requirement
R11</a>).
However, there are many applications where the unique names
assumption would be useful. Users should have the option of
specifying that all of the names in a particular namespace or
document refer to distinct individuals.</p>

<p><b>Motivation:</b>
<a href="#goal-inconsistency">Inconsistency detection</a>
</p>
</dd>


<dt><a id="obj-complex-data-types" name="obj-complex-data-types"></a>
<b>015. Complex data types</b></dt>
<dd>
<p>The language must support the definition and use of complex/
structured data types. These may be used to specify dates,
coordinate pairs, addresses, etc.</p>

<p><b>Motivation:</b>
<a href="#goal-standards">Compatibility with other standards</a>,
<a href="#goal-ease-of-use">Ease of use</a>
</p>
</dd>


</dl>

<hr />

<h2><a id="acknowledgments" name="acknowledgments"></a>
Acknowledgments</h2>

<p>
This document is the result of extensive discussions within the
<a href="http://www.w3.org/2001/sw/Webont">Web Ontology Working Group
</a>as a whole.  The members of this group working group included:
Yasser al Safadi, Jean-Francois Baget,  James Barnette, Sean
Bechhofer, Jonathan Borden,  Frederik Brysse, Stephen Buswell, Peter
Crowther, Jos De Roo, David De Roure,  Mike Dean, Larry Eshelman,
Jerome Euzenat, Dieter Fensel, Tim Finin, Nicholas Gibbins, Pat
Hayes,  Jeff Heflin, Ziv Hellman, James Hendler,  Bernard Horan,
Masahiro Hori, Ian Horrocks, Francesco Iannuzzelli, Mario Jeckle,
Ruediger Klein,  Ora Lassila, Alexander Maedche, Massimo Marchiori,
Deborah McGuinness, Libby Miller, Enrico Motta,  Leo Obrst, Laurent
Olivry , Peter Patel-Schneider, Martin Pike, Marwan Sabbouh, Guus
Schreiber, Shimizu Noboru,  Michael Sintek,  Michael Smith, Ned
Smith, John Stanton,  Lynn Andrea Stein, Herman ter Horst,  Lynne R.
Thompson,  David Trastour, Frank van Harmelen,  Raphael Volz, Evan
Wallace, Christopher Welty, and John Yanosy.
</p>

<p>Particularly significant contributions were made by the following people:
Raphael Volz and Jonathan Dale were co-editors for earlier versions
of this document.
Many of the original goals are based on a list of requirements
contributed by Deborah McGuinness. A draft version of the Corporate
Web Site Management section was written by Michael Smith.</p>


  <p>
    <a href="http://validator.w3.org/check/referer"><img
        src="http://www.w3.org/Icons/valid-xhtml10"
        alt="Valid XHTML 1.0!" height="31" width="88" /></a>
  </p>


</body>
</html>