swbpd-charter.html 26.1 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" lang="en">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  <title>Semantic Web Best Practices and Deployment Working Group
  Charter</title>
  <link href="/StyleSheets/base.css" rel="stylesheet" type="text/css" />
  <link href="charter.css" rel="stylesheet" type="text/css" />
</head>

<body xml:lang="en" lang="en">
<p><a href="http://www.w3.org/"><img height="48" alt="W3C"
src="http://www.w3.org/Icons/w3c_home.gif" width="72" /></a> <a
href="http://www.w3.org/TandS/" accesskey="D"><img
src="http://www.w3.org/Icons/tands" width="212" height="48"
alt="Technology and Society Domain" /></a> <a href="/2001/sw/"><img
src="/2001/sw/sw" alt="The Semantic Web Home Page" /></a></p>

<h1>Semantic Web Best Practices and Deployment (SWBPD) Working Group
Charter</h1>

<h2>Status of this Document</h2>

<p>Per section <a
href="http://www.w3.org/2004/02/Process-20040205/groups.html#GAGeneral">6
Working Groups, Interest Groups, and Coordination Groups</a> of the W3C
Process, this charter, and any changes to it, take effect by way of an
announcement to the W3C Membership via <a
href="http://lists.w3.org/Archives/Member/w3c-ac-members/">w3c-ac-members</a>.</p>

<p>This charter was approved by the W3C Director in an announcement to the
W3C Membership on 25 February, 2004. The <a href="#changelog">change log</a>
summarizes changes from the <a href="/2004/01/12-swbpd-charter">proposed
charter</a>.</p>

<h2>About</h2>

<p>The Semantic Web Best Practices and Deployment (SWBPD) Working Group is
focused on providing consensus-based guidance - including practical
deployment recommendations, engineering guidelines, ontology / vocabulary
development practices, educational material and effective demonstrations,
designed to facilitate <a href="/2001/sw/">Semantic Web</a> deployment.</p>

<h2>Contents</h2>
<ul class="toc">
  <li><a href="#sec1">1. Scope</a>
    <ul class="toc">
      <li><a href="#sec11">1.1 General aim</a></li>
      <li><a href="#sec12">1.2 Focus areas</a></li>
      <li><a href="#sec13">1.3 Out of scope</a></li>
    </ul>
  </li>
  <li><a href="#sec2">2. Deliverables and Schedule</a></li>
  <li><a href="#sec3">3. Relationship with Other Activities</a>
    <ul class="toc">
      <li><a href="#sec31">3.1 W3C activities</a></li>
      <li><a href="#sec32">3.2 External groups</a></li>
    </ul>
  </li>
  <li><a href="#sec4">4. Membership, Meetings, and Logistics</a>
    <ul class="toc">
      <li><a href="#sec41">4.1 Email communication</a></li>
      <li><a href="#sec42">4.2 Group home page</a></li>
      <li><a href="#sec43">4.3 Telephone meetings</a></li>
      <li><a href="#sec44">4.4 Face-to-face meetings</a></li>
    </ul>
  </li>
  <li><a href="#sec5">5. Resources</a>
    <ul class="toc">
      <li><a href="#sec51">5.1 WG participation</a></li>
      <li><a href="#sec52">5.2 W3C team involvement</a></li>
    </ul>
  </li>
  <li><a href="#sec6">6. Intellectual Property Rights</a></li>
</ul>
<hr />

<h2><a name="sec1" id="sec1">1. Scope</a></h2>

<h3><a name="sec11" id="sec11">1.1 General aim</a></h3>
The aim of this Semantic Web Best Practices and Deployment (SWBPD) Working
Group is to provide hands-on support for developers of Semantic Web
applications. With the publication of the revised RDF and the new OWL
specification we expect a large number of new application developers. Some
evidence of this could be seen at the last International Semantic Web
Conference in Florida, which featured a wide range of applications, including
10 submissions to the Semantic Web Challenge (see <a
href="http://challenge.semanticweb.org/">http://challenge.semanticweb.org/</a>).This
working group will help application developers by providing them with "best
practices" in various forms, ranging from engineering guidelines, ontology /
vocabulary repositories to educational material and demo applications.

<p>This Working Group is intended to capitalize on work already been done.
This work is typically spread over a range of disciplines and communities,
combining experience from industry and computer science with research
insights from fields as diverse as philosophy, linguistics, library science,
psychology, conceptual modeling, and domain modeling, amongst others. This
work is typically spread over a range of disciplines: philosophy,
linguistics, library science, psychology, conceptual modeling, domain
modeling, etc.</p>

<p>The working group will focus on four areas for providing support.</p>

<h3><a name="sec12" id="sec12">1.2 Focus areas</a></h3>

<h4><a name="focus1" id="focus1">1.2.1 Focus: Supporting initiatives for
publishing ontologies / vocabularies</a></h4>

<p>In various domains large ontologies, including vocabularies and thesauri,
have been constructed. Typically, these corpora are the result of many years
of collaborative effort in a community. Such corpora form indispensable
resources for Semantic Web applications. One prime objective of the SWBPD
Working Group is to help make these resources publicly available for
application developers.</p>

<p>To this end the working group will undertake the following activities:</p>
<ul>
  <li>Produce a Working Group Note on guidelines for transforming an existing
    representation into an RDF/OWL representation. This note should be based
    on experiences in this area (e.g. the <a
    href="http://lists.w3.org/Archives/Public/www-rdf-interest/2003Nov/0095.html">Calendar</a>
    work).</li>
  <li>Work with ontology / vocabulary owners to convert their corpora to
    RDF/OWL.</li>
  <li>Support the publication of the resulting RDF/OWL ontology on a publicly
    accessible spot.</li>
</ul>

<p>The result should be a set of publicly available high-profile ontologies.
The following is an indicative (nonlimitative) list of existing ontologies at
which this focus area is targeted:</p>
<ul>
  <li>Lexical corpora: e.g., <a
    href="http://www.semanticweb.org/library/#wordnet">WordNet,</a>, <a
    href="http://www.icsi.berkeley.edu/~framenet/">FrameNet</a>, non-English
    versions of WordNet (EuroWordNet)</li>
  <li><a href="http://dublincore.org/">Dublin Core</a> and its
    specializations (e.g. <a href="http://www.vraweb.org/vracore3.htm">VRA
    Core Categories</a>)</li>
  <li>Cultural-heritage standards/thesauri: e.g., <a
    href="http://www.getty.edu/research/conducting_research/vocabularies/">the
    Getty thesauri</a> (Art and Architecture Thesaurus, Union List of Artist
    Names, Thesaurus of Geographic Names), <a
    href="http://www.iconclass.nl">ICONCLASS</a>, <a
    href="http://cidoc.ics.forth.gr/index.html">CIDOC CRM</a></li>
  <li>Medical vocabularies: e.g., <a
    href="http://www.nlm.nih.gov/research/umls/">UMLS</a>, <a
    href="http://www.opengalen.org/">OpenGALEN</a>, <a
    href="http://www.mindswap.org/2003/CancerOntology/">NCI cancer
    ontology</a></li>
  <li>Product vocabularies: e.g., <a
    href="http://www.rosettanet.org/">RosettaNet</a>, <a
    href="http://www.unspsc.org/">UNSPSC</a>, <a
    href="http://www.census.gov/epcd/www/naics.html">NAICS</a></li>
  <li>Molecular biology: e.g., <a href="http://www.geneontology.org/">Gene
    Ontology</a></li>
  <li>Foundational ontologies: e.g., units and measures, engineering
    mathematics, <a href="http://www.loa-cnr.it/DOLCE.html">DOLCE</a>, Cohn's
    spatial ontology, Allen's time ontology, URIs for Geography and Languages
    (c.f. <a
    href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=geolang">related
    Topic Maps work</a>).</li>
  <li>Large common-sense ontologies: e.g., <a
    href="http://suo.ieee.org/">SUO</a>, <a
    href="http://www.opencyc.org/">OpenCyc</a> <a
    href="http://dmoz.org/">Open Directory Project</a></li>
</ul>
Criteria for an ontology to be within the scope of this Working Group are:
<ul>
  <li>The ontology is the result of the collaborative work in some community
    and represents some form of consensus.</li>
  <li>The ontology has a user community.</li>
  <li>The ontology owner is maintaining the ontology.</li>
  <li>The ontology owner is willing to make the ontology publicly available
    on a <a
    href="/Consortium/Patent-Policy-20040205/#sec-Requirements">Royalty Free
    basis</a>.</li>
</ul>

<p>Related works to be considered include <a
href="http://www.w3c.rl.ac.uk/SWAD/thesaurus.html">SWAD Europe work on
thesauri</a>, <a href="http://www.schemaweb.info/">SchemaWeb</a> as well as
similar initiatives.</p>

<h4><a name="focus2" id="focus2">1.2.2 Focus: FAQs and how-to-do-it
guidelines</a></h4>

<p>The goal of this focus area is to provide support for practical issues
related to ontology / vocabulary engineering and use for the Semantic Web.</p>

<p>The Working Group will be the sponsoring group for the RDF in XHTML Task
Force [<a href="http://www.w3.org/2003/08/rdf-in-xhtml-charter">charter</a>,
<a href="http://www.w3.org/2003/03/rdf-in-xml.html">work plan</a>], currently
chartered under the Semantic Web Coordination Group. The Working Group will,
in conjunction with the HTML Working Group, provide a solution for
representing RDF metadata within an XHMTL document.</p>

<p>Additional task forces may be created to investigate specific deployment
issues, especially those which have a connection to other W3C work. The
development of an RDF Schema or OWL Ontology for the XML Schema datatypes is
an example of such a task force.</p>

<p>Other Working Group Notes may be developed from topics brought by Working
Group participants. Research topics are out of scope. Examples of possible
guideline development include:</p>
<ul>
  <li>Design patterns for constructing ontologies, covering typical modeling
    problems such as defaults, part-of, .... As an example of a Wiki-based
    pattern, see Chris Welty's <a
    href="http://esw.w3.org/topic/PartWhole">part-whole pattern</a>.</li>
  <li>Naming conventions for classes/properties/individuals;</li>
  <li>Ontology mapping: how to use multiple heterogeneous ontologies in an
    interoperable way.</li>
  <li>Ontology integration/unification vs. mapping (the latter is usually
    preferred)</li>
</ul>

<p>to the extent that these topics (above) consider practical deployment
questions and avoid areas of research. The WG should give priority to topics
concerning interoperability as well as to topics that relate to other W3C
work.</p>

<p>The Working Group may choose to create or contribute to an index of:</p>
<ul>
  <li>links to course materials</li>
  <li>links to introductory texts: e.g. "Ontologies for Dummies"</li>
  <li>collections of worked-out examples, covering a broad range of
  fields</li>
  <li>pointers to knowledge-elicitation techniques</li>
</ul>

<p>Working Group Notes that could be produced:</p>
<ul>
  <li>How to use Semantic markup on your web page</li>
  <li>Differences in world view between description logic, frames and
    first-order logic</li>
  <li>Identifying the backbone of an ontology [Rector, OntoClean]</li>
</ul>

<h4><a name="focus3" id="focus3">1.2.3 Focus: Repository of tools and demo
applications</a></h4>

<p>The Working Group will cooperate with and contribute to efforts to
maintain a Tool and application index. This index should provide data in RDF
and OWL format in addition to a human-friendly presentation format. The index
should provide only references to materials when they have a home elsewhere
in the Web but may host materials developed by or contributed to the Working
Group. The Working Group may choose to offer some 'value add' by highlighting
materials that in its view support the Working Group's other Focus Areas in
some noteworthy manner.</p>
<ul>
  <li>Example tool types
    <ul>
      <li>RDF/RDFS/OWL parsers</li>
      <li>benchmarking tools</li>
      <li>visualization tools. e.g. <a
        href="http://www.w3.org/2001/11/IsaViz/">IsaViz</a>, <a
        href="http://rdfweb.org/people/damian/RDFAuthor/">RDFAuthor</a>, <a
        href="http://www.research.att.com/sw/tools/graphviz/">GraphViz</a></li>
      <li>validators/checkers</li>
      <li>reasoners</li>
      <li>query languages, rule languages, APIs</li>
      <li>ontology editors</li>
      <li>tools for marking up web pages</li>
    </ul>
  </li>
  <li>Typical demo applications
    <ul>
      <li><a href="http://challenge.semanticweb.org/">Semantic Web
        Challenge</a></li>
      <li><a href="http://www.w3.org/2002/12/cal/">RDF Calendar</a></li>
      <li><a href="http://www.foaf-project.org/">FOAF</a> (Friend of a
      Friend)</li>
      <li>W3C glossary</li>
      <li>Example web pages using RDF/OWL mark-up</li>
      <li>Using the Working Group itself as demo application (use of ICal,
        annotation of pages, etc.)</li>
    </ul>
  </li>
</ul>

<p>Preference is given to open-source software.</p>

<p class="note">NOTE: This focus area is likely to be carried out in
coordination with activities in the DAML program, e.g. on open-source tools
for OWL.</p>

<h4><a name="focus4" id="focus4">1.2.4 Focus: Links to related
techniques</a></h4>

<p>The Working Group will consider publishing Working Group Notes on links to
related (standardization) efforts. The goal of such notes will be to provide
guidelines for users who want to combine usage of the two fields. Typical
topics for such notes would be:</p>
<ul>
  <li>interoperable use of MPEG and RDF/OWL annotations and/or ontologies</li>
  <li>using UML for ontology development/visualization</li>
  <li>the relationship between Semantic Web and Topic Maps</li>
  <li>the relationship between Semantic Web and databases</li>
</ul>

<p>This should typically be done in cooperation with the other organizations
involved (MPEG, OASIS, OMG)</p>

<h3><a name="sec13" id="sec13">1.3 Out of scope</a></h3>
<ul>
  <li>Ontologies / vocabularies that do not meet the criteria set out for
    focus area 1 are out of scope.</li>
  <li>Guidelines that are not based on some form of established practice are
    out of scope.</li>
  <li>Proprietary information (software which is not open source, ontologies
    which are not publicly available on a royalty-free basis) will not be
    addressed by this group.</li>
  <li>The relation to web services is not the primary focus of the working
    group.</li>
  <li>Work that requires basic research is out of scope.</li>
  <li>Duplication of effort; areas that are being adequately addressed in
    other parts of the RDF and OWL community should be treated as out of
    scope.</li>
  <li>Endorsement of specific tools is out of scope.</li>
</ul>

<h2><a name="sec2" id="sec2">2. Deliverables and Schedule</a></h2>

<p>This Working Group is chartered for a duration of 23 months, through 1
May 2006. The kick-off meeting is planned to be held on <b>March 4-5 2004
at the <a href="http://www.w3.org/2003/08/allgroupoverview.html">W3C Tech
Plenary in Cannes</a></b>.</p>

<p>The Working Group will initiate task forces for producing Working Group
notes. These task forces will typically operate in the following way:</p>
<ul>
  <li>The time frame of a task force is short-term, e.g. 4 (2-6) months</li>
  <li>The editors/coordinators of a task force are selected from the Working
    Group participants.</li>
  <li>A task force may recommend non-Member individuals with relevant skills
    to participate in the task force as invited experts. The normal <a
    href="http://www.w3.org/2003/06/Process-20030618/groups.html#invited-expert-wg">invited
    expert</a> process will be followed. Final decision on any task force
    issue rests with the whole Working Group.</li>
  <li>The task force size should be 4-8 people</li>
  <li>Task forces use the regular Working Group communication channels.</li>
  <li>The result of this work is proposed to the full Working Group for
    consideration and discussion on next steps.</li>
</ul>

<p>The Working Group may consider using Wiki techniques to facilitate its
work, particularly for data collection or FAQs, however formally edited and
published Working Group Notes are to be preferred over Wikis for
dissemination of guidelines. When the material is appropriate, the Working
Group will use the <a
href="http://www.w3.org/2004/02/Process-20040205/tr.html#Reports">W3C
Recommendation Track Process</a> to propose the advancement of technical
reports to Recommendation.</p>

<p>The Working Group will consider producing a short note about how the
Working Group determines what is a best practice, e.g. that it should be
based on real implementations. The <a
href="http://www.oasis-open.org/committees/uddi-spec/doc/bps.htm">best-practices
process</a> of the OASIS UDDI Spec TC could serve as useful input.</p>

<h2><a name="sec3" id="sec3">3. Relationship with Other Activities</a></h2>

<h3><a name="sec31" id="sec31">3.1 W3C-related activities</a></h3>
<ul>
  <li>The W3C <a href="http://www.w3.org/2001/sw/interest/">Semantic Web
    Interest Group</a></li>
  <li><a href="http://www.w3.org/2000/01/sw/">SWAD-MIT</a></li>
  <li><a href="http://www.w3.org/2001/sw/Europe/">SWAD-Europe</a></li>
  <li>The W3C <a href="http://www.w3.org/2002/ws/swsig/">Semantic Web
    Services Interest Group</a></li>
  <li>The W3C <a href="http://www.w3.org/XML/Group/Schemas">XML Schema WG</a>
    especially for datatype discussions</li>
  <li>The W3C <a href="http://www.w3.org/International/">Internationalization
    Activity</a> especially if language ontologies are discussed</li>
</ul>

<h3><a name="sec32" id="sec32">3.2 External groups</a></h3>
<ul>
  <li><a href="http://www.daml.org/">DAML program</a></li>
  <li>European IST projects: <a
    href="http://www.w3.org/2001/sw/Europe/">SWAD-Europe</a>, <a
    href="http://knowledgeweb.semanticweb.org">Knowledge Web</a></li>
  <li>OMG: UML profile for OWL</li>
  <li>MPEG: relationship MPEG 7/21 &lt;-&gt; RDF/OWL</li>
  <li>Vocabulary programs: e.g. Getty, UMLS,</li>
  <li>Topic Map groups at ISO/OASIS</li>
</ul>

<h2><a name="sec4" id="sec4">4. Membership, Meetings, and Logistics</a></h2>

<p>To become a participant of the Working Group, a representative of a W3C
Member organization must be nominated by their Advisory Committee
Representative (details on how to join are on the group home page). The
nomination must include explicit agreement to this charter, including its
goals, the level of effort required and an IPR disclosure.</p>

<p>Experts from appropriate communities may also be invited to join the
working group, following the <a
href="http://www.w3.org/2003/06/Process-20030618/groups.html#invited-expert-wg">normal
process.</a></p>

<p>Each Working Group participant is expected to contribute 20%, or at least
a day per week to this group.</p>

<p>All proceedings of the Working Group (mail archives, telecon minutes, ftf
minutes) will be available to the public.</p>

<p>Working Group participants are not obligated to participate in every task
force, however the Working Group as a whole is responsible for reviewing and
accepting the output of each task force. Task force participants are expected
to participate in WG face-to-face meetings and telecons where the work of the
task force is on the agenda.</p>

<h3><a name="sec41" id="sec41">4.1 Email communication</a></h3>

<p>The mailing list for group communication is <a
href="mailto:public-swbp-wg@w3.org">public-swbp-wg@w3.org</a> with a publicly
readable <a
href="http://lists.w3.org/Archives/Public/public-swbp-wg/">archive</a>.</p>

<h3><a name="sec42" id="sec42">4.2 Group home page</a></h3>

<p>The Working Group will have a home page that records the history of the
group, provides access to the archives, meeting minutes, updated schedule of
deliverables, membership list, and relevant documents and resources. The page
will be available to the public and will be maintained by one of the
co-chairs in collaboration with the W3C team contact.</p>

<h3><a name="sec43" id="sec43">4.3 Telephone meetings</a></h3>

<p>The Working Group will hold teleconferences approximately every two weeks.
Participation in phone conferences is limited to members of the working
group. The Chair may, at his discretion, invite guest experts to attend
particular phone conferences. An IRC channel may be used to supplement
teleconferences.</p>

<p>Meeting records should be made available within two days of each telephone
meeting.</p>

<h3><a name="sec44" id="sec44">4.4 Face-to-face meetings</a></h3>

<p>Participation in face-to-face meetings is limited to working group members
and observers invited by the Chair. Observers may take part in
decision-making at the discretion of the Chair.</p>

<p>In addition to the required two annual face-to-face meetings, the Working
Group may schedule other face-to-face meetings in a manner that maximizes
co-location with events that Working Group members might be attending
anyway.</p>

<p>The Chair makes Working Group meeting dates and locations available to the
group at least eight weeks before the meeting, per W3C Process.</p>

<h2><a name="sec5" id="sec5">5. Resources</a></h2>

<h3><a name="sec51" id="sec51">5.1 Working Group participation</a></h3>

<p>To be successful, we expect to have between 10 and 20 active participants
for the duration of this Working Group. We also expect a large public review
group that will participate in the mailing list discussions.</p>

<h3><a name="sec52" id="sec52">5.2 W3C team involvement</a></h3>

<p>The W3C Team expects to allocate the equivalent of 40% of a full-time
person to this work for the duration of this working group; through 1
May 2006. This time includes the Team Contact effort as well as
additional participation.</p>

<h2><a name="sec6" id="sec6">6. Intellectual Property Rights</a></h2>

<p>This Working Group operates under the <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy
(5 Feb 2004 Version)</a>. To promote the widest adoption of Web standards,
W3C seeks to issue Recommendations that can be implemented, according to this
policy, on a Royalty-Free basis.</p>

<p>$Id: swbpd-charter.html,v 1.42 2006/04/20 14:21:17 swick Exp $</p>
<a id="changelog" name="changelog"></a>
<pre>$Log: swbpd-charter.html,v $
<pre>Revision 1.42  2006/04/20 14:21:17  swick
<pre>Charter extended to 1 May 2006, per announcement to AC on 19 Jan.
<pre>http://lists.w3.org/Archives/Member/w3c-ac-members/2006JanMar/0009.html
<pre>
<pre>Revision 1.41  2004/02/26 20:58:16  janet
<pre>(janet) Changed through Jigsaw.
<pre>
Revision 1.40  2004/02/26 15:20:06  swick
Add a link to the WG mailing list archive.

Revision 1.39  2004/02/26 15:06:31  swick
Add back a link to the snapshot of the as-reviewed charter in the Status.

Revision 1.38  2004/02/26 15:02:18  swick
Charter approved and announced to AC in message from Janet Daly to
the W3C Advisory Committee Representatives on 25 Feb 2004 15:09:27 -0800

Revision 1.37  2004/02/25 21:19:11  swick
Patent Policy disclosure obligations exist on Working Drafts only,
not on Working Group Notes.  So no additional language in the IPR section.

Revision 1.36  2004/02/25 20:45:53  swick
fix URI citing Royalty Free licensing section of Patent Policy.

Revision 1.34  2004/02/25 20:26:35  swick
Update Process Document and Patent Policy citations to the current versions.

Revision 1.33  2004/02/24 21:13:05  swick
Note to-do for Patent Policy language in Seciton 6.

Revision 1.32  2004/02/24 20:13:20  swick
Treat duplicative efforts as out of scope, largely to avoid this WG
preempting other efforts.

Revision 1.31  2004/02/24 20:02:32  swick
Work requiring basic research is out of scope.

Revision 1.30  2004/02/24 19:52:13  swick
W3C does not endorse others' software -- remind the WG that endorsement
of specific tools is out of scope.

Revision 1.29  2004/02/24 04:31:00  swick
Place some expectations on task force participation.

Revision 1.28  2004/02/24 04:27:04  swick
Clarify intent of reference to 'review' of proprietary ontologies being
out of scope.  Clarify 'outside people' as invited experts.  Add XML Schema
and I18N to list of relevant W3C activities.

Revision 1.27  2004/02/24 03:08:54  swick
Revise the intent of 1.2.3 Focus: Repository.  In particular, the
repository/archive/index work should be complementary and contributory
to other existing indices and should not host materials that already
have a suitable Web home.

Revision 1.26  2004/02/24 02:47:12  swick
Use of XML Schema datatypes with RDF and OWL is a specific example
of another possible task force.

Revision 1.25  2004/02/23 19:04:59  swick
Further advice to the WG on FAQ and guideline priorities;
interoperability and items that connect to other W3C work.

Revision 1.24  2004/02/23 18:52:12  swick
Revise 1.2.2 Focus: FAQs and guidelines.  Technical Reports are preferred
over Wiki for formal publishing (revision to 2.Deliverables).  Caution
the WG to avoid research topics and to contribute to other indices
of how-to-do-it components where those indices exist.

Revision 1.22  2004/02/23 18:13:34  swick
Work on 1.2.1 Focus area; delete paragraph suggesting a separate repository
for other ontologies, add citation of geolang work as foundational ontologies.

Revision 1.20  2004/02/23 17:55:46  swick
Merge Process Document header paragraph into SOTD, add changelog.

Revision 1.19  2004/02/23 17:50:48  swick
Add Status section and cite the as-proposed snapshot.</pre>

<p><small><a
href="/Consortium/Legal/ipr-notice-20000612#Copyright">Copyright</a>&nbsp;©&nbsp;1998-2000&nbsp;
<a href="http://www.w3.org/"><acronym
title="World Wide Web Consortium">W3C</acronym></a> <sup>®</sup> (<a
href="http://www.lcs.mit.edu/"><acronym
title="Massachusetts Institute of Technology">MIT</acronym></a>, <a
href="http://www.inria.fr/"><acronym xml:lang="fr" lang="fr"
title="Institut National de Recherche en Informatique et en Automatique">INRIA</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym
title="World Wide Web Consortium">W3C</acronym> <a
href="/Consortium/Legal/ipr-notice-20000612#Legal_Disclaimer">liability</a>,
<a href="/Consortium/Legal/ipr-notice-20000612#W3C_Trademarks">trademark</a>,
<a href="/Consortium/Legal/copyright-documents-19990405">document use</a> and
<a href="/Consortium/Legal/copyright-software-19980720">software
licensing</a> rules apply. Your interactions with this site are in accordance
with our <a
href="/Consortium/Legal/privacy-statement-20000612#Public">public</a> and <a
href="/Consortium/Legal/privacy-statement-20000612#Members">Member</a>
privacy statements.</small></p>
</body>
</html>