You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1847 lines
85 KiB
1847 lines
85 KiB
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<!--
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:dcterms="http://purl.org/dc/terms/" xml:lang="en-US" lang="en-US">
|
|
-->
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
|
|
<head>
|
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
|
|
<!--
|
|
<meta property="dcterms:hasVersion" content="$Id: Overview.html,v 1.11 2009/08/18 13:31:14 swick Exp $"/>
|
|
<meta property="dcterms:modified" content="$Date: 2009/08/18 13:31:14 $"/>
|
|
-->
|
|
<title>SKOS Use Cases and Requirements</title>
|
|
<style type="text/css" xml:space="preserve">
|
|
form { background: #eee5de; color: black; border: thin black solid; padding: .5em; margin-top: 1em }
|
|
.sample { border: thin black solid }
|
|
.testname { display: none }
|
|
.boilerplate, .boilerplate-nocode { font-size: small; background: #ddd }
|
|
div.boilerplate, p.boilerplate, blockquote.boilerplate, div.boilerplate-nocode, p.boilerplate-nocode, blockquote.boilerplate-nocode { margin: 1em; border: thin black solid; padding: .25em }
|
|
div.source { margin: 1em }
|
|
.notetoeditor { color: red; background: white}
|
|
input[type="submit"] { border: 2px green solid }
|
|
dd h5 { font-weight:bold; padding:.25em 0; margin:0 }
|
|
dl { margin:0; padding:0 }
|
|
ul.descriptions li {padding:.25em}
|
|
</style>
|
|
<link rel="stylesheet" type="text/css"
|
|
href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE" />
|
|
</head>
|
|
|
|
<body>
|
|
|
|
<div class="head">
|
|
<p><a href="http://www.w3.org/"><img alt="W3C" height="48"
|
|
src="http://www.w3.org/Icons/w3c_home" width="72" /></a></p>
|
|
|
|
<h1 style="clear:both" id="title">SKOS Use Cases and Requirements</h1>
|
|
|
|
<h2 id="W3C-doctype">W3C Working Group Note 18 August 2009</h2>
|
|
<dl>
|
|
<dt>This version:</dt>
|
|
<dd><a href="http://www.w3.org/TR/2009/NOTE-skos-ucr-20090818/"
|
|
>http://www.w3.org/TR/2009/NOTE-skos-ucr-20090818/</a></dd>
|
|
<dt>Latest version:</dt>
|
|
<dd><a
|
|
href="http://www.w3.org/TR/skos-ucr">http://www.w3.org/TR/skos-ucr</a></dd>
|
|
<dt>Previous version:</dt>
|
|
<dd><a
|
|
href="http://www.w3.org/TR/2007/WD-skos-ucr-20070516/">http://www.w3.org/TR/2007/WD-skos-ucr-20070516/</a></dd>
|
|
<dt>Editors:</dt>
|
|
<dd>Antoine Isaac, Vrije Universiteit Amsterdam, <a
|
|
href="mailto:aisaac@few.vu.nl">aisaac@few.vu.nl</a></dd>
|
|
<dd>Jon Phipps, Cornell University, <a
|
|
href="mailto:jphipps@madcreek.com">jphipps@madcreek.com</a></dd>
|
|
<dd>Daniel Rubin, Stanford Medical Informatics, <a
|
|
href="mailto:dlrubin@stanford.edu">dlrubin@stanford.edu</a></dd>
|
|
</dl>
|
|
|
|
<p class="copyright"><a
|
|
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
|
|
© 2009 <a href="http://www.w3.org/"><acronym
|
|
title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a
|
|
href="http://www.csail.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>
|
|
and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
|
|
use</a> rules apply.</p>
|
|
</div>
|
|
<hr />
|
|
|
|
<h2 id="abstract">Abstract</h2>
|
|
|
|
<p>Knowledge organization systems, such as taxonomies, thesauri or subject
|
|
heading lists, play a fundamental role in information structuring and access.
|
|
The Semantic Web Deployment Working Group aims at providing a model for
|
|
representing such vocabularies on the Semantic Web: SKOS (Simple Knowledge
|
|
Organization System).</p>
|
|
|
|
<p>This document presents the preparatory work for the 2009 version of SKOS
|
|
[<cite><a href="#SKOS-REFERENCE">SKOS-REFERENCE</a></cite>]. It lists
|
|
representative use cases, which were obtained after a dedicated questionnaire
|
|
was sent to a wide audience. It also features a set of fundamental or
|
|
secondary requirements derived from these use cases, that have been used to
|
|
guide the design of SKOS.</p>
|
|
|
|
<p>This document is a companion to the <a
|
|
href="http://www.w3.org/TR/skos-reference">SKOS Reference</a> and the <a
|
|
href="http://www.w3.org/TR/skos-primer/">SKOS Primer</a>, which respectively
|
|
provide the normative reference on SKOS and a user guide for those who would
|
|
like to represent their concept scheme using SKOS.</p>
|
|
<hr />
|
|
|
|
<h2 id="status">Status of this document</h2>
|
|
|
|
<p><em>This section describes the status of this document at the time of its
|
|
publication. Other documents may supersede this document. A list of current
|
|
W3C publications and the latest revision of this technical report can be
|
|
found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>
|
|
at <a href="http://www.w3.org/TR/">http://www.w3.org/TR/</a>.</em></p>
|
|
|
|
<p>This document is an editorial update to the first public
|
|
Working Draft of the "SKOS (Simple
|
|
Knowledge Organization System) Use Cases and Requirements", developed by the
|
|
W3C <a href="http://www.w3.org/2006/07/SWD/">Semantic Web Deployment Working
|
|
Group</a> [<a href="#SWD">SWD</a>]. Publication of this version is
|
|
concurrent with the advancement of the
|
|
<a href="http://www.w3.org/TR/skos-reference">SKOS Reference</a>
|
|
to W3C Recommendation.</p>
|
|
|
|
<p>The <a href="#L7057">Use Cases</a> detailed in this document have been
|
|
selected as representative of the use cases submitted in response to a "<a
|
|
href="http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0036.html">Call
|
|
for Use Cases</a>" published in December 2006. These use cases as well as <a
|
|
href="http://www.w3.org/2006/07/SWD/track/products/3">Issues</a> identified
|
|
by the working group have resulted in draft <a
|
|
href="#Requirements">Requirements</a> that will guide the design of the
|
|
future SKOS Recommendaton. Early feedback is therefore most useful. Feedback
|
|
on use cases that can help to resolve <a
|
|
href="http://www.w3.org/2006/07/SWD/track/products/3">open issues</a> is
|
|
especially important. Note also that any feature listed under <a
|
|
href="#Candidate">Candidate Requirements</a> should be considered as "at
|
|
risk" without further feedback.</p>
|
|
|
|
<p>Comments on this document may be sent to <a
|
|
href="mailto:public-swd-wg@w3.org">public-swd-wg@w3.org</a>; please include
|
|
the text "[SKOS] UCR comment" in the subject line. All messages received at
|
|
this address are viewable in a <a
|
|
href="http://lists.w3.org/Archives/Public/public-swd-wg/">public archive</a>.</p>
|
|
|
|
<p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
|
|
|
|
<p>This document was produced by a group operating under the <a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
|
|
W3C Patent Policy</a>. W3C maintains a <a rel="disclosure"
|
|
href="http://www.w3.org/2004/01/pp-impl/39408/status">public list of any
|
|
patent disclosures</a> made in connection with the deliverables of the group;
|
|
that page also includes instructions for disclosing a patent. An individual
|
|
who has actual knowledge of a patent which the individual believes contains
|
|
<a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
|
|
Claim(s)</a> must disclose the information in accordance with <a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
|
|
6 of the W3C Patent Policy</a>.</p>
|
|
|
|
<hr />
|
|
|
|
<h2 id="Table"><a id="toc" name="toc"></a>Table of Contents</h2>
|
|
|
|
<div class="toc">
|
|
<ul>
|
|
<li><a href="#Table">Table of contents</a></li>
|
|
<li><a href="#L7031">1 Introduction</a></li>
|
|
<li><a href="#L7057">2 Use Cases</a>
|
|
<ul>
|
|
<li><a href="#UC-Manuscripts">2.1 Use Case #1 — An integrated view to
|
|
medieval illuminated manuscripts</a></li>
|
|
<li><a href="#UC-Biozen">2.2 Use Case #2 — Bio-zen ontology framework
|
|
for representing scientific discourse in life science</a></li>
|
|
<li><a href="#UC-Aims">2.3 Use Case #3 — Semantic search service
|
|
across mapped multilingual thesauri in the agriculture domain</a></li>
|
|
<li><a href="#UC-ProductLifeCycleSupport">2.4 Use Case #4 —
|
|
Supporting product life cycle</a></li>
|
|
<li><a href="#UC-RankingForDescription">2.5 Use Case #5 —
|
|
CHOICE@CATCH ranking of candidate terms for description of radio and
|
|
TV programs</a></li>
|
|
<li><a href="#UC-BirnLex">2.6 Use Case #6 — BIRNLex: a lexicon for
|
|
neurosciences</a></li>
|
|
<li><a href="#UC-RadLex">2.7 Use Case #7 — Radlex: a lexicon for
|
|
radiology</a></li>
|
|
<li><a href="#UC-MetadataRegistry">2.8 Use Case #8 — NSDL Metadata
|
|
Registry</a></li>
|
|
<li><a href="#Other">2.9 Other use cases</a></li>
|
|
</ul>
|
|
</li>
|
|
<li><a href="#Requirements">3 Requirements</a>
|
|
<ul>
|
|
<li><a href="#Accepted">3.1 Accepted requirements</a></li>
|
|
<li><a href="#Candidate">3.2 Candidate requirements</a></li>
|
|
</ul>
|
|
</li>
|
|
<li><a href="#Conclusion">4 Conclusion</a></li>
|
|
<li><a href="#References">References</a></li>
|
|
<li><a href="#Acknowledgments">Acknowledgments</a></li>
|
|
</ul>
|
|
</div>
|
|
<hr />
|
|
|
|
<h2 id="L7031"><a id="section-introduction" name="section-introduction"></a>1
|
|
Introduction</h2>
|
|
|
|
<p>Knowledge organization systems play a fundamental role in information
|
|
structuring and access, e.g. for asset description or web site organization.
|
|
Such vocabularies, coming in the form of thesauri, classification schemes,
|
|
subject heading lists, taxonomies or even folksonomies, are developed and
|
|
used worldwide, by institutions as well as individuals. However these very
|
|
important knowledge resources are still mostly isolated from the outside
|
|
world, and not widely used in implementing systems.</p>
|
|
|
|
<p>The development of new information technologies and infrastructures, such
|
|
as the World Wide Web, calls for new ways to create, manage, publish and use
|
|
these knowledge organization systems. It is especially expected that
|
|
conceptual schemes will benefit from greater shareability, e.g. by being
|
|
published via web services. In the meantime, the documentary systems which
|
|
use them will turn to advanced information retrieval techniques to construct
|
|
most of their semantic structure and lexical content.</p>
|
|
|
|
<p>SKOS (Simple Knowledge Organization System) provides a model to represent
|
|
and use vocabularies and ontologies in the framework of the Semantic Web. A
|
|
first version [<cite><a
|
|
href="#SWBP-SKOS-CORE-GUIDE">SWBP-SKOS-CORE-GUIDE</a></cite>] has been
|
|
produced by the Semantic Web Best Practices and Deployment working group
|
|
[<cite><a href="#SWBPD">SWBPD</a></cite>], and is already used in some
|
|
research projects. The Semantic Web Deployment Working Group [<cite><a
|
|
href="#SWD">SWD</a></cite>] has been chartered to continue this work, and to
|
|
"produce guidelines and an RDF vocabulary (SKOS) for transforming an existing
|
|
vocabulary representation into an RDF/OWL representation" [<cite><a
|
|
href="#SWD-Charter">SWD-Charter</a></cite>].</p>
|
|
|
|
<p>In order to delimit the scope and elicit the required features for SKOS,
|
|
the SWD working group has issued in December 2006 a call for use cases,
|
|
asking for descriptions of existing or planned SKOS applications, according
|
|
to a specific <a
|
|
href="http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0036.html">questionnaire</a>.
|
|
Following the gathering of these use cases, the Working Group has elicited a
|
|
number of requirements for SKOS which are motivated by the previous work on
|
|
SKOS, or by contributions received following the call for use cases.</p>
|
|
|
|
<p>This document gives an account of this process. First, section 2 presents
|
|
summaries of selected contributions, and pointers to the complete set of
|
|
cases which were sent to the Working Group. Second, section 3 lists the
|
|
requirements the Working Group has elicited following the call for use
|
|
cases.</p>
|
|
<hr />
|
|
|
|
<h2 id="L7057">2 Use Cases</h2>
|
|
|
|
<h3 id="UC-Manuscripts">2.1 Use Case #1 — An integrated view to medieval
|
|
illuminated manuscripts</h3>
|
|
|
|
<p><span style="font-size: 10pt">(Contributed by Antoine Isaac. <br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucManuscriptsDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucManuscriptsDetailed</a>
|
|
<span style="font-size: 10pt">and at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucIconclassDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucIconclassDetailed</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>The purpose of this application is to provide the user with access to two
|
|
collections of illuminated manuscripts from the Dutch and French national
|
|
libraries, <em>Medieval Illuminated Manuscripts</em> and <em>Mandragore</em>
|
|
(accessible online at <a
|
|
href="http://www.kb.nl/manuscripts">http://www.kb.nl/manuscripts</a> and <a
|
|
href="http://mandragore.bnf.fr">http://mandragore.bnf.fr</a>). The
|
|
descriptions of images from these two collections follow different metadata
|
|
schemes, and contain values from different controlled vocabularies for
|
|
subject indexing. The user should however be able to search for items from
|
|
the two collections using his preferred point of view, either using
|
|
vocabulary from collection 1 or vocabulary from collection 2.</p>
|
|
|
|
<p>The main feature of the current application—available on the STITCH
|
|
project site, <a
|
|
href="http://stitch.cs.vu.nl/">http://stitch.cs.vu.nl/</a>—is
|
|
collection browsing (previously in BNF_KB_demo.html), which uses hierarchical links in vocabularies: if a
|
|
concept matching a query has subconcepts, the documents indexed against these
|
|
subconcepts should be returned. The application also uses mapping links
|
|
between concepts from the two vocabularies. For example, if an equivalence
|
|
link is found between a query concept from one vocabulary and another concept
|
|
from the second one, documents indexed by this other concept shall also be
|
|
included in the query results.</p>
|
|
|
|
<p>Requires: <a href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-IndexingRelationship">R-IndexingRelationship</a></p>
|
|
|
|
<p>Additionally, the application enables search based on free text queries
|
|
over the collection metadata: documents can be retrieved based on free-text
|
|
querying of the different fields used to describe the documents (creator,
|
|
place, subject, etc.). For subject indexing, if a text query matches the
|
|
label of a controlled vocabulary concept, the documents indexed against this
|
|
concept will be returned.</p>
|
|
|
|
<p>The two collections use respectively the Iconclass and Mandragore analysis
|
|
vocabularies.</p>
|
|
|
|
<p>Iconclass (<a href="http://www.iconclass.nl">http://www.iconclass.nl</a>)
|
|
contains 28,000 classes used to describe the subjects of an image (persons,
|
|
event, abstract ideas). Complete versions are available for English, German,
|
|
French, Italian, and partial translations for Finnish and Norwegian.</p>
|
|
|
|
<p>Requires: <a
|
|
href="#R-MultilingualLexicalInformation">R-MultilingualLexicalInformation</a></p>
|
|
|
|
<p>The main building blocks of Iconclass are <em>subjects</em>, used to
|
|
describe the subjects of images. An Iconclass subject consists of a
|
|
<em>notation</em> (an alphanumeric identifier used for annotation) and a
|
|
<em>textual correlate</em> (e.g. “25F9 mis-shapen animals; monsters”).
|
|
Subjects are organized in hierarchical trees, as in the following extract:</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td>2 Nature<br />
|
|
|
|
|
|
<div style="text-indent: 15pt">
|
|
25 earth, world as celestial body</div>
|
|
|
|
<div style="text-indent: 30pt">
|
|
25F animals</div>
|
|
|
|
<div style="text-indent: 45pt">
|
|
25F(+) KEY</div>
|
|
|
|
<div style="text-indent: 45pt">
|
|
25F1 groups of animals</div>
|
|
|
|
<div style="text-indent: 45pt">
|
|
…</div>
|
|
|
|
<div style="text-indent: 45pt">
|
|
25F9 mis-shapen animals; monsters</div>
|
|
|
|
<div style="text-indent: 45pt">
|
|
25FF fabulous animals (sometimes wrongly called 'grotesques');
|
|
'Mostri' (Ripa)</div>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Subjects can have associative cross-reference links between them
|
|
(<em>systematic references</em>) and are linked to <em>keywords</em> that are
|
|
used to search for them in Iconclass tools. Keywords form a network of their
|
|
own, featuring <em>see</em> links (from one non-preferred keyword, not
|
|
attached to any subject, to a preferred one), <em>see also</em> links
|
|
(between keywords that are semantically or iconographically related) and
|
|
<em>translation</em> links (between keywords in different languages).</p>
|
|
|
|
<p>Requires: <a href="#R-LabelRepresentation">R-LabelRepresentation</a>, <a
|
|
href="#R-RelationshipsBetweenLabels">R-RelationshipsBetweenLabels</a></p>
|
|
|
|
<p>Iconclass additionally provides <em>auxiliary</em> mechanisms for subject
|
|
specialization at indexing time. These actually allow for collection-specific
|
|
vocabulary extension:</p>
|
|
<ul>
|
|
<li>by specializing a conceptual "placeholder" into a named individual
|
|
(<em>bracketed text</em>) : <code>11H(…) saints</code> can be
|
|
specialized into <code>11H(VALENTINE)</code>, which does not exist in the
|
|
standard Iconclass,</li>
|
|
<li>or by combining an existing subject with special auxiliaries (e.g.
|
|
<em>keys</em> and <em>structural digits</em>): <code>25F2 mammals</code>
|
|
can be combined with <code>(+33) head of an animal</code>, resulting in
|
|
<code>25F(+33)</code> which will index an image of a mammal's head. Or
|
|
<code>11H(VALENTINE)2</code> can be synthesized from
|
|
<code>11H(VALENTINE)</code> and <code>11H(...)2 early life of male
|
|
saint</code> to index an image which specifically denotes the early days
|
|
of St. Valentine.</li>
|
|
</ul>
|
|
|
|
<p>Requires: <a
|
|
href="#R-ConceptSchemeExtension">R-ConceptSchemeExtension</a>, <a
|
|
href="#R-SkosSpecialization">R-SkosSpecialization</a>, <a
|
|
href="#R-IndexingAndNonIndexingConcepts">R-IndexingAndNonIndexingConcepts</a>,
|
|
<a href="#R-ConceptCoordination">R-ConceptCoordination</a></p>
|
|
|
|
<p>Maintenance of the vocabulary is done via manual editing of
|
|
semi-structured source files. As a general rule, the standard version will
|
|
only be changed in a conservative way, not modifying the existing
|
|
subjects.</p>
|
|
|
|
<p>Mandragore contains 16,000 subjects. 15,800 are <em>descriptors</em>,
|
|
which are used to describe the illuminations and form a flat list. Additional
|
|
structure is given by 200 <em>abstract topic classes</em> which form a
|
|
hierarchy organizing the descriptors according to general domains, but cannot
|
|
themselves be used to describe documents:</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<tbody>
|
|
<tr>
|
|
<td>
|
|
<div>
|
|
ZOOLOGIE</div>
|
|
|
|
<div style="text-indent: 15pt">
|
|
.zoologie (généralités)</div>
|
|
|
|
<div style="text-indent: 15pt">
|
|
.mollusques</div>
|
|
|
|
<div style="text-indent: 15pt">
|
|
.mammifères</div>
|
|
|
|
<div style="text-indent: 30pt">
|
|
cochon [mammifère ongulé]</div>
|
|
|
|
<div style="text-indent: 30pt">
|
|
girafe [mammifère ongulé]</div>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>A descriptor is specified by a French label (“cochon”, for pig),
|
|
optional rejected forms (“porc”), an optional definition (“mamifère
|
|
ongulé”, hoofed mammal) and a reference to one or more topic classes
|
|
(“.mammifères”, mammals). A note can sometimes be found as a
|
|
complementary definition.</p>
|
|
|
|
<p>To enable integrated browsing, elements from Mandragore and Iconclass
|
|
vocabularies must be linked together using equivalence or specialization
|
|
links as in the following:</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<tbody>
|
|
<tr>
|
|
<td><code>25F72 molluscs</code> (Iconclass) is equivalent to
|
|
<code>mollusques</code> (Mandragore) </td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>25F711 insects</code> (Iconclass) is more specific than
|
|
<code>autres invertébrés (vers,arachnides,insectes...)</code>
|
|
("other invertebrates (worms, arachnida, insects)", Mandragore) </td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>11U4 Mary and John the Baptist together with (e.g. kneeling
|
|
before) the judging Christ, 'Deesis' ~ Last Judgement</code>
|
|
(Iconclass) is equivalent to the <em>combination</em> of subjects
|
|
<code>s.marie</code>, <code>s.jean.baptiste</code>,
|
|
<code>christ</code> and <code>jugement.dernier</code> (Mandragore)
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>25F(+441) herd, group of animals</code> (Iconclass) is
|
|
equivalent to <code>troupeau</code> (Mandragore) </td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Requires: <a
|
|
href="#R-ConceptualMappingLinks">R-ConceptualMappingLinks</a></p>
|
|
<hr />
|
|
|
|
<h3 id="UC-Biozen">2.2 Use Case #2 — Bio-zen ontology framework for
|
|
representing scientific discourse in life science</h3>
|
|
|
|
<p><span style="font-size: 10pt">(Contributed by Matthias Samwald,
|
|
Medizinische Universität Wien. <br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucBiozenDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucBiozenDetailed</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>Bio-zen (<a
|
|
href="http://neuroscientific.net/index.php?id=43">http://neuroscientific.net/index.php?id=43</a>)
|
|
allows the description of biological systems and the representation of
|
|
scientific discourse on the web in a highly distributed manner. It is
|
|
intended to be used by researchers and developers in the life sciences.</p>
|
|
|
|
<p>SKOS is used in bio-zen for the representation of many existing life
|
|
sciences vocabularies, taxonomies and ontologies coming from the "Open
|
|
Biomedical Ontologies" (OBO) collection (<a
|
|
href="http://www.fruitfly.org/~cjm/obo-download/">http://www.fruitfly.org/~cjm/obo-download/</a>).
|
|
The size of all converted taxonomies taken together is on the order of
|
|
millions of concepts. Typical examples are the Gene Ontology or Medical
|
|
Subject Headings (MeSH), an entry of which is displayed here:</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<tbody>
|
|
<tr>
|
|
<td>id</td>
|
|
<td>MESH:A.01.047.025</td>
|
|
</tr>
|
|
<tr>
|
|
<td>name</td>
|
|
<td>abdominal_cavity</td>
|
|
</tr>
|
|
<tr>
|
|
<td>def</td>
|
|
<td>"The region in the abdomen extending from the thoracic DIAPHRAGM to
|
|
the plane of the superior pelvic aperture (pelvic inlet). The
|
|
abdominal cavity contains the PERITONEUM and abdominal VISCERA\, as
|
|
well as the extraperitoneal space which includes the RETROPERITONEAL
|
|
SPACE." [MESH:A.01.047.025]</td>
|
|
</tr>
|
|
<tr>
|
|
<td>synonym</td>
|
|
<td>abdominal_cavity</td>
|
|
</tr>
|
|
<tr>
|
|
<td>synonym</td>
|
|
<td>cavitas_abdominis</td>
|
|
</tr>
|
|
<tr>
|
|
<td>is_a</td>
|
|
<td>MESH:A.01.047 ! abdomen</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Requires: <a href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-LabelRepresentation">R-LabelRepresentation</a>, <a
|
|
href="#R-TextualDescriptionsForConcepts">R-TextualDescriptionsForConcepts</a></p>
|
|
|
|
<p>To represent such vocabulary elements as well as other types of
|
|
information, the existing SKOS model has been integrated into a single OWL
|
|
ontology, together with the DOLCE foundational ontology and the Dublin Core
|
|
metadata model. In the process, the SKOS model has been extended with special
|
|
types of concepts, e.g. biozen:sequence-concept. To enable efficient
|
|
reasoning with the available dataset, it is important to note that existing
|
|
constructs have been made compatible with the OWL-DL language.</p>
|
|
|
|
<p>Requires: <a
|
|
href="#R-CompatibilityWithOWL-DL">R-CompatibilityWithOWL-DL</a></p>
|
|
|
|
<p>The bio-zen framework will consist of several applications, especially
|
|
Semantic Wikis. A Bio-zen ontology incorporates constructs to make statements
|
|
about digital information resources, that is creating "concept tags". This
|
|
concept-tagging is an important feature of bio-zen, because it eases the
|
|
integration of information from different sources.</p>
|
|
|
|
<p>Requires: <a href="#R-IndexingRelationship">R-IndexingRelationship</a></p>
|
|
<hr />
|
|
|
|
<h3 id="UC-Aims">2.3 Use Case #3 — Semantic search service across mapped
|
|
multilingual thesauri in the agriculture domain</h3>
|
|
|
|
<p><span style="font-size: 10pt">(Contributed by Margherita Sini and Johannes
|
|
Keizer, Food and Agriculture Organization. <br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucAimsDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucAimsDetailed</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>This application coming from the AIMS project (<a
|
|
href="http://www.fao.org/aims">http://www.fao.org/aims</a>) is a semantic
|
|
search service that makes use of mapped agriculture thesauri. It allows users
|
|
to search any available terminology in any of the languages in which the
|
|
thesauri are provided and retrieve information from resources which may have
|
|
been indexed by one of the mapped vocabularies. Typical functions are
|
|
navigating resources, helping to build boolean searches via concept
|
|
identification, or expanding given searches by extra languages or
|
|
synonyms.</p>
|
|
|
|
<p>Requires: <a href="#R-IndexingRelationship">R-IndexingRelationship</a></p>
|
|
|
|
<p>The service builds on several agriculture vocabularies: the Agrovoc
|
|
Thesaurus (<a
|
|
href="http://www.fao.org/aims/ag_intro.htm">http://www.fao.org/aims/ag_intro.htm</a>),
|
|
the Agris/Caris Classification Scheme (ASC), the FAO Technical Knowledge
|
|
Classification Scheme (TKCS), the subjects from the FAOTERM vocabulary,
|
|
etc.</p>
|
|
|
|
<p>Agrovoc contains 35,000 <em>terms</em> in 12 languages (not all of the
|
|
languages feature the same translated terms, however), while ASC, TCKS and
|
|
FAOTERM range between 100 and 200 categories available in the 5 official FAO
|
|
languages. Agrovoc terms consist of one or more words and always represent a
|
|
single concept. Terms are divided into <em>descriptors</em> and
|
|
<em>non-descriptors</em>, the first currently only used for indexing. For
|
|
each descriptor, a word block is displayed showing the relation to other
|
|
terms: BT (broader term), NT (narrower term), RT (related term), UF
|
|
(non-descriptor). There are also scope notes, used to clarify the meaning of
|
|
both descriptors and non-descriptors.</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td><code>Term code</code></td>
|
|
<td><code>1939</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>Term label</code></td>
|
|
<td><code>EN : Cows, FR : Vache, ES : Vaca, AR : بقرات , ZH : ?牛
|
|
, PT : Vaca, CS : krávy, JA : 雌牛 , TH : ?ม่โค , SK :
|
|
kravy, DE : KUH</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>BT</code></td>
|
|
<td><code>Cattle (code 1391)</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>NT</code></td>
|
|
<td><code>Suckler cows, Dairy cows (26767, 36875)</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>RT</code></td>
|
|
<td><code>Heifers, Cow milk, Milk yielding animals, Females (3535,
|
|
4833, 15969, 16080)</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>SNR</code></td>
|
|
<td><code>Females (15969)</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>Scope Note</code></td>
|
|
<td><code>Use only for cattle and zebu cattle; for other species use
|
|
"Females" (15969) plus the descriptor for the species</code></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Requires: <a href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-LabelRepresentation">R-LabelRepresentation</a>, <a
|
|
href="#R-TextualDescriptionsForConcepts">R-TextualDescriptionsForConcepts</a>,
|
|
<a
|
|
href="#R-MultilingualLexicalInformation">R-MultilingualLexicalInformation</a></p>
|
|
|
|
<p>Actually, the AIMS project includes some more specific links, presented in
|
|
<a
|
|
href="http://www.fao.org/aims/">http://www.fao.org/aims/</a> (formerly in cs_relationships.htm:
|
|
Concept-to-Concept relationships (subclass of; caused by; member of; part
|
|
of), Term-to-Term relationships (related term; synonym; translation) and
|
|
String-to-String relationships (spelling variant; acronym).</p>
|
|
|
|
<p>Examples of such links are:</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<tbody>
|
|
<tr>
|
|
<td><code>synonym</code></td>
|
|
<td><code>bucket</code></td>
|
|
<td><code>pail</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>abbreviation_of</code></td>
|
|
<td><code>Corp.</code></td>
|
|
<td><code>Corporation</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>acronym</code></td>
|
|
<td><code>Food and Agriculture Organization</code></td>
|
|
<td><code>FAO</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>spelling_variant</code></td>
|
|
<td><code>organisation</code></td>
|
|
<td><code>organization</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>translation</code></td>
|
|
<td><code>vache</code></td>
|
|
<td><code>cow</code></td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>scientific_taxonomic_name</code></td>
|
|
<td><code>African violet</code></td>
|
|
<td><code>Saintpaulia</code></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Requires: <a href="#R-SkosSpecialization">R-SkosSpecialization</a>, <a
|
|
href="#R-RelationshipsBetweenLabels">R-RelationshipsBetweenLabels</a></p>
|
|
|
|
<p>Currently the Agrovoc management system lacks distributed maintenance, but
|
|
it is expected that a new system will soon solve this problem, which is
|
|
crucial since changes are made by experts from all over the world.</p>
|
|
|
|
<p>For AIMS, Agrovoc has been converted into SKOS and is being mapped to two
|
|
other vocabularies: the Chinese Agricultural Thesaurus (CAT) and the National
|
|
Agricultural Library thesaurus (NAL). This mapping uses links inspired by the
|
|
SKOS mapping vocabulary [<cite><a
|
|
href="#SWBP-SKOS-MAPPING">SWBP-SKOS-MAPPING</a></cite>], as below:</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<tbody>
|
|
<tr>
|
|
<td>CAT-ID</td>
|
|
<td>CAT-EN</td>
|
|
<td>Map</td>
|
|
<td>AG-ID</td>
|
|
<td>AG-EN</td>
|
|
<td>AG-ID</td>
|
|
<td>AG-EN</td>
|
|
</tr>
|
|
<tr>
|
|
<td>30854</td>
|
|
<td>Senta flammea</td>
|
|
<td>Exact</td>
|
|
<td>9748</td>
|
|
<td>Cheena</td>
|
|
<td></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>50008</td>
|
|
<td>Mayetola destructor</td>
|
|
<td>Exact-OR</td>
|
|
<td>24260</td>
|
|
<td>Triticale (gramineae)</td>
|
|
<td>7949</td>
|
|
<td>Triticales (product)</td>
|
|
</tr>
|
|
<tr>
|
|
<td>1160</td>
|
|
<td>Two-shear sheep</td>
|
|
<td>NT1</td>
|
|
<td>3662</td>
|
|
<td>Hordeum vulgare</td>
|
|
<td></td>
|
|
<td></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Requires: <a
|
|
href="#R-ConceptualMappingLinks">R-ConceptualMappingLinks</a></p>
|
|
<hr />
|
|
|
|
<h3 id="UC-ProductLifeCycleSupport">2.4 Use Case #4 — Supporting product
|
|
life cycle</h3>
|
|
|
|
<p><span style="font-size: 10pt">(Contributed by Sean Barker, BAE Systems.
|
|
<br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucProductLifeCycleSupportDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucProductLifeCycleSupportDetailed</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>The problem of the Product Life Cycle Support (PLCS) application is to
|
|
integrate a network of interconnected supply chains, with multiple, large
|
|
customers buying a wide range of products (from shoes to aircraft) each
|
|
dictating their own standards, and with every supplier being part of multiple
|
|
supply chains. Each customer wants to maintain a common approach over all its
|
|
supply chains. And each supplier wants to maintain the same system for each
|
|
of the supply chains it works in.</p>
|
|
|
|
<p>The aim of this application is to propose a data exchange mechanism for
|
|
managing the life support of complex products (<a
|
|
href="http://www.oasis-open.org">http://www.oasis-open.org</a>), including
|
|
configuration definition, maintenance definition, maintenance planning and
|
|
scheduling, and maintenance and usage recording (including configuration
|
|
change).</p>
|
|
|
|
<p>For that, an upper ontology of several hundred items for the description
|
|
of the product life cycle will be defined. There is no chance of the entire
|
|
supply system (10,000's of businesses) developing a single detailed model.
|
|
However, given the upper ontology, they will be free to specialize individual
|
|
ontology terms (playing the role of place holders for local extension) to
|
|
meet their precise needs.</p>
|
|
|
|
<p>PLCS is conceptually a co-operatively developed web in XML, with the live
|
|
version being a set of runtime views assembled from files submitted by a
|
|
dozen or so contributors. It may be useful, where ontologies diverge, to map
|
|
terms between the diverging branches, either to indicate where terms can be
|
|
harmonized to their equivalent, or to identify that there is a similarity
|
|
link that is not exact equivalence.</p>
|
|
|
|
<p>Requires: <a href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-ConceptSchemeExtension">R-ConceptSchemeExtension</a>, <a
|
|
href="#R-ConceptualMappingLinks">R-ConceptualMappingLinks</a></p>
|
|
|
|
<p>The PLCS vocabulary addresses hundreds of separate functions, including
|
|
classification of items, classification of information usages (e.g. types of
|
|
part identifier), classification of entity roles (e.g. date as start date) or
|
|
classification of relationships (e.g. supersedes).</p>
|
|
|
|
<p>Typical examples of terms are:</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td>Identification_code</td>
|
|
<td>An Identification_code is an identifier_type which is encoded
|
|
according to some convention. Typically but not necessarily
|
|
concatenated from parts each with a meaning. E.g. tag number, serial
|
|
number, package number and document number.</td>
|
|
</tr>
|
|
<tr>
|
|
<td>Part_identification_code</td>
|
|
<td>A Part_indentfication_code is an Identification_code that
|
|
identifies the types of parts. For example, a part number. <br />
|
|
CONSTRAINT: An Identification_assignment classified as a
|
|
Part_identification_code can only be assigned to Part
|
|
Organization_name. </td>
|
|
</tr>
|
|
<tr>
|
|
<td>Owner_of</td>
|
|
<td>An Owner_of is an Organization_or_person_in_organization_assignment
|
|
that is assigning a person or organization to something in the role
|
|
of owner. <br />
|
|
For example, the owner of the car. </td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>The vocabulary has been encoded using OWL, and is managed via the Protege
|
|
OWL editor.</p>
|
|
|
|
<p>Requires: <a
|
|
href="#R-TextualDescriptionsForConcepts">R-TextualDescriptionsForConcepts</a></p>
|
|
<hr />
|
|
|
|
<h3 id="UC-RankingForDescription">2.5 Use Case #5 — CHOICE@CATCH ranking of
|
|
candidate terms for description of radio and TV programs</h3>
|
|
|
|
<p><span style="font-size: 10pt">(Contributed by Véronique Malaisé and
|
|
Hennie Brugman, Vrije Universiteit Amsterdam and Max Planck Institute for
|
|
Psycholinguistics. <br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucRankingForDescriptionDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucRankingForDescriptionDetailed</a>
|
|
<span style="font-size: 10pt">and at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucGtaaBrowser"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucGtaaBrowser</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>Radio and television programs at the Dutch national broadcasting archive
|
|
(Sound and Vision, <a
|
|
href="http://www.beeldengeluid.nl">http://www.beeldengeluid.nl</a>) are
|
|
typically associated with contextual text descriptions: web site texts,
|
|
subtitles, program guide texts, texts from the production process, etc. These
|
|
context documents are used by documentalists at Sound and Vision who manually
|
|
describe programs using concepts from the GTAA thesaurus (Gemeenschappelijke
|
|
Thesaurus Audiovisuele Archieven—Common Thesaurus for Audiovisual
|
|
Archives).</p>
|
|
|
|
<p>The CHOICE project (part of the Dutch CATCH research program) uses natural
|
|
language processing techniques to automatically extract candidate GTAA terms
|
|
from the context documents. The application focused on in this section takes
|
|
these candidate terms as input, and ranks them on the basis of the structure
|
|
of the GTAA thesaurus. For example, the fact that "Voting" and
|
|
"Democratization" are related in GTAA by a two-step path (via the "Election"
|
|
term and two "related-to" links) will positively influence the ranking of
|
|
these terms. Ranked terms will be presented to documentalists to speed up
|
|
their description work.</p>
|
|
|
|
<p>The GTAA vocabulary covers a wide range of topics, as it is meant to
|
|
describe anything that can be broadcast on TV or radio. It contains
|
|
approximately 160,000 terms, divided into 6 disjoint facets: Keywords,
|
|
Locations, Person Names, Organization-Group-Other Names, Maker Names, and
|
|
Genres.</p>
|
|
|
|
<p>The thesaurus mainly uses constructs from the ISO 2788 standard, like
|
|
Broader Term, Narrower Term, Related Term and Scope Notes. Terms from all
|
|
facets of the GTAA may have Related Terms, Use/Use For and Scope Notes, but
|
|
only Keywords and Genres can also have Broader Term/Narrower Term relations,
|
|
organizing them into a set of hierarchies. In addition to these standard
|
|
features, Keywords terms are thematically classified in 88 subcategories of
|
|
16 top Categories.</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td>Preferred Term</td>
|
|
<td>ambachten <em>(crafts)</em></td>
|
|
</tr>
|
|
<tr>
|
|
<td>Related Terms</td>
|
|
<td>ondernemingen <em>(ventures)</em> , beroepen
|
|
<em>(professions)</em>, artistieke beroepen <em>(artistic
|
|
professions)</em></td>
|
|
</tr>
|
|
<tr>
|
|
<td>Broader Term</td>
|
|
<td>beroepen <em>(professions)</em></td>
|
|
</tr>
|
|
<tr>
|
|
<td>Narrower Terms</td>
|
|
<td>boekbinders <em>(bookbinders)</em>, bouwvakkers <em>(building
|
|
workers)</em>, glasblazers <em>(glassblowers)</em></td>
|
|
</tr>
|
|
<tr>
|
|
<td>Scope Note</td>
|
|
<td>niet voor afzonderlijke ambachten maar alleen als verzamelbegrip,
|
|
bijv. voor (markten van) oude ambachten <em>(not for specific crafts,
|
|
only in general meaning, e.g. (markets of) old crafts)</em></td>
|
|
</tr>
|
|
<tr>
|
|
<td>Categories</td>
|
|
<td>05 economie (economy), 09 techniek (technique)</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Requires: <a href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-LabelRepresentation">R-LabelRepresentation</a>, <a
|
|
href="#R-SkosSpecialization">R-SkosSpecialization</a></p>
|
|
|
|
<p>The application, envisioned as a SOAP web service, uses a Sesame RDF web
|
|
repository (<a href="http://openrdf.org">http://openrdf.org</a>) containing
|
|
the SKOS version of the GTAA thesaurus to retrieve the 'term contexts' of the
|
|
terms in the input list, which is stored in a local RDF repository.</p>
|
|
|
|
<p>This term context includes, for one given term, all terms that are
|
|
directly connected to it by Broader Term, Narrower Term or Related Term
|
|
relations. This includes pre-computed inter-facet links that are not part of
|
|
the ISO standard, though allowed by the GTAA data model. For example, one can
|
|
link a "King" in the Person facet to the general subject "Kings" and the
|
|
country which this King rules.</p>
|
|
|
|
<p>For the ranking, it is now assumed that candidate terms that are mutually
|
|
connected by thesaurus relations (directly or indirectly) are more likely to
|
|
be good descriptions than isolated candidate terms. Later on, it might be
|
|
interesting to differentiate between types of thesaurus relations, or to use
|
|
more complex patterns of these relations.</p>
|
|
|
|
<p>The thesaurus-based recommendation system can also be integrated with a
|
|
recommendation system that is based on co-occurences between terms that are
|
|
used in previously existing descriptions of programs.</p>
|
|
<hr />
|
|
|
|
<h3 id="UC-BirnLex">2.6 Use Case #6 — BIRNLex: a lexicon for
|
|
neurosciences</h3>
|
|
|
|
<p><span style="font-size: 10pt">(Contributed by William Bug, Drexel
|
|
University College of Medicine. <br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucBirnLexDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucBirnLexDetailed</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>BIRNLex is an integrated ontology+lexicon used for various purposes —
|
|
some end-user/interactive, others back-end/infrastructure — within the BIRN
|
|
Project to support semantically-formal data annotation, semantic data
|
|
integration, and semantically-driven, federated query resolution.</p>
|
|
|
|
<p>Requires: <a
|
|
href="#R-ConceptualMappingLinks">R-ConceptualMappingLinks</a>, <a
|
|
href="#R-IndexingRelationship">R-IndexingRelationship</a>, <a
|
|
href="#R-LexicalMappingLinks">R-LexicalMappingLinks</a></p>
|
|
|
|
<p>Below are examples of BIRNLex class definitions that illustrate the need
|
|
for lexical support and links to external knowledge sources. The general
|
|
design goals have been to use both the Dublin Core metadata elements and SKOS
|
|
where ever possible. The goal is to use SKOS for all lexical qualities. There
|
|
are certain annotation properties that should be shared across all biomedical
|
|
knowledge resources. There are other required elements specific to the
|
|
specific needs in BIRN (the group producing BIRNLex).</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td>Class</td>
|
|
<td>Anterior_ascending_limb_of_lateral_sulcus</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:birnlexCurator</td>
|
|
<td>Bill Bug</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:birnlexExternalSource</td>
|
|
<td>NeuroNames</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:bonfireID</td>
|
|
<td>C0262186</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:curationStatus</td>
|
|
<td>raw import</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:neuronames</td>
|
|
<td>ID 49</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:UmlsCui</td>
|
|
<td>C0262186</td>
|
|
</tr>
|
|
<tr>
|
|
<td>obo_annot:createdDate</td>
|
|
<td>"2006-10-08"^^http://www.w3.org/2001/XMLSchema#date</td>
|
|
</tr>
|
|
<tr>
|
|
<td>obo_annot:modifiedDate</td>
|
|
<td>"2006-10-08"^^http://www.w3.org/2001/XMLSchema#date</td>
|
|
</tr>
|
|
<tr>
|
|
<td>skos:prefLabel</td>
|
|
<td>Anterior_ascending_limb_of_lateral_sulcus</td>
|
|
</tr>
|
|
<tr>
|
|
<td>skos:scopeNote</td>
|
|
<td>human-only</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p></p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td>Class</td>
|
|
<td>Medium_spiny_neuron</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:birnlexCurator</td>
|
|
<td>Maryann Martone</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:birnlexDefinition</td>
|
|
<td>The main projection neuron found in caudate nucleus, putamen and
|
|
nucleus accumbens...</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:bonfireID</td>
|
|
<td>BF_C000100</td>
|
|
</tr>
|
|
<tr>
|
|
<td>birn_annot:curationStatus</td>
|
|
<td>pending final vetting</td>
|
|
</tr>
|
|
<tr>
|
|
<td>dc:source</td>
|
|
<td>Maryann Martone</td>
|
|
</tr>
|
|
<tr>
|
|
<td>obo_annot:createdDate</td>
|
|
<td>"2006-07-15"^^http://www.w3.org/2001/XMLSchema#date</td>
|
|
</tr>
|
|
<tr>
|
|
<td>obo_annot:modifiedDate</td>
|
|
<td>"2006-09-28"^^http://www.w3.org/2001/XMLSchema#date</td>
|
|
</tr>
|
|
<tr>
|
|
<td>skos:prefLabel</td>
|
|
<td>Medium_spiny_neuron</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p>Requires: <a href="#R-CompatibilityWithDC">R-CompatibilityWithDC</a>, <a
|
|
href="#R-CompatibilityWithOWL-DL">R-CompatibilityWithOWL-DL</a>, <a
|
|
href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-LabelRepresentation">R-LabelRepresentation</a>, <a
|
|
href="#R-ConceptSchemeExtension">R-ConceptSchemeExtension</a></p>
|
|
|
|
<p>The following is a subset of BIRNLex applications, either extant or in the
|
|
offing:</p>
|
|
<ul>
|
|
<li>online curation: tools to enable curating the BIRNLex ontology+lexicon
|
|
via the web;</li>
|
|
<li>annotation: applications designed to support domain experts annotating
|
|
neuroimaging data;</li>
|
|
<li>query/mediation: a mediator program federates more than 60 data
|
|
repositories. Site databases register with the mediator by mapping the
|
|
relevant elements from their resident data model into the mediator's
|
|
global model.</li>
|
|
</ul>
|
|
|
|
<p>In all of these applications, it is critical to have a clear, distinct,
|
|
and shared representation for the associated lexicon. For instance, when
|
|
integrating BIRN segmented brain images with those from other projects across
|
|
the net, use of lexical variants from a variety of public terminologies and
|
|
thesauri such as SNOMED and MeSH can provide a powerful means to largely
|
|
automate semantic integration of like entities - e.g., corresponding brain
|
|
region, equivalent behavioral assays described using different preferred
|
|
labels/names. In providing a community shared formalism for representing the
|
|
associated lexicon, SKOS can greatly simplify this task. If, for instance,
|
|
the lexical repository (collection of Lexical Unique Identifier, each lexical
|
|
variant of a term getting one LUI) contained in UMLS were represented
|
|
according to SKOS, this would provide an extremely valuable resource to the
|
|
community of semantically-oriented bioinformatics researchers, as well as a
|
|
powerful tool to support latent semantic analysis or natural language
|
|
processing when linking to unstructured text.</p>
|
|
|
|
<p>The following are the collection of terminologies and ontologies being
|
|
linked into BIRNLex: Neuronames, Brainmap.org classification schemes, <a
|
|
href="#UC-RadLex">RadLex</a>, Gene Ontology, Reactome, OBI, PATO, Subcellular
|
|
Anatomy Ontology (CCDB - <a
|
|
href="http://ccdb.ucsd.edu/">http://ccdb.ucsd.edu/</a>), MeSH.</p>
|
|
|
|
<p>Neuronames concerns brain anatomy and is about 750 classes and thousands
|
|
of associated lexical variants. Brainmap.org classification includes
|
|
hierarchies to describe neuroanatomy, subject variables, stimulus conditions,
|
|
and experimental paradigms associated with functional MRI of the nervous
|
|
system The Subcellular Anatomy Ontology is designed to describe the
|
|
subcellular entities associated with ultrastructural and histological imaging
|
|
of neural tissue. Currently the application is only dealing with English
|
|
lexical entries.</p>
|
|
|
|
<p>BIRNLex curators are working with the National Center for Biomedical
|
|
Ontology (NCBO) to adopt the OBO Foundry recommendations in the construction
|
|
of BIRNLex. Use of SKOS elements can be useful, so that, for instance,
|
|
software applications can draw on "skos:prefLabel", "obo_annot:synonym",
|
|
"obo_annot:definition", etc.</p>
|
|
|
|
<p>The management of BIRNLex is currently done manually in Protege-OWL.</p>
|
|
|
|
<p>Requires: <a
|
|
href="#R-CompatibilityWithOWL-DL">R-CompatibilityWithOWL-DL</a></p>
|
|
|
|
<p>However, the ultimate goal is to adopt a client-server infrastructure that
|
|
will create an RDF-based backend store and support both curation of the
|
|
ontology and annotation using the ontology via Java Portlet-based
|
|
applications. BIRN has a core infrastructure staff dedicated to use of the
|
|
GridSphere Java Portlet implementation framework (<a
|
|
href="http://www.gridsphere.org">www.gridsphere.org</a>).</p>
|
|
<hr />
|
|
|
|
<h3 id="UC-RadLex">2.7 Use Case #7 — Radlex: a lexicon for radiology</h3>
|
|
|
|
<p><span style="font-size: 10pt">(contributed by Curt Langlotz. <br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucRadlexDetailed"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/EucRadlexDetailed</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>RadLex provides a structured vocabulary of terms used in the field of
|
|
radiology. Currently completed are listings of anatomic terms and "findings",
|
|
which includes things that can be seen on or inferred from images produced by
|
|
radiologists. These two sets include a total of about 7,500 terms. A list of
|
|
the terms used to describe the creation of such images, including information
|
|
about the equipment used and the various imaging sequences performed, will be
|
|
complete by the end of 2007.</p>
|
|
|
|
<p>An example application demonstrating functionality is an image annotation
|
|
program that reads in RadLex and provides users the ability to search for and
|
|
use particular RadLex terms to associate with images, post-coordinating them
|
|
if necessary. Users would want to be able to retrieve RadLex terms by name or
|
|
synonym.</p>
|
|
|
|
<p>Requires: <a href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-LabelRepresentation">R-LabelRepresentation</a>, <a
|
|
href="#R-TextualDescriptionsForConcepts">R-TextualDescriptionsForConcepts</a>,
|
|
<a href="#R-ConceptCoordination">R-ConceptCoordination</a></p>
|
|
|
|
<p>RadLex, which can be searched and browsed online at <a
|
|
href="http://www.radlex.org">www.radlex.org</a>, is a taxonomy currently
|
|
built predominantly using is-a relations. But there are also part-of and
|
|
other relations (especially for anatomy), and new relations will be added as
|
|
RadLex expands. Each term has a rich set of metadata fields to include
|
|
provenance information and terminological data such as synonyms, definition,
|
|
and related terms from other vocabularies.</p>
|
|
|
|
<p>The practical fields include:</p>
|
|
<ul>
|
|
<li>Term name</li>
|
|
<li>ID number (with no inherent semantics)</li>
|
|
<li>parents, and their relation to the term</li>
|
|
<li>children, and their relation to the term</li>
|
|
</ul>
|
|
|
|
<p>and optionally, any</p>
|
|
<ul>
|
|
<li>mappings to other vocabularies</li>
|
|
<li>definition</li>
|
|
<li>synonyms</li>
|
|
<li>source (a reference publication which includes this term)</li>
|
|
<li>other comments (such as derivation of the term, special or preferred
|
|
uses of it, etc.)</li>
|
|
</ul>
|
|
|
|
<p>Requires: <a href="#R-ConceptualRelations">R-ConceptualRelations</a>, <a
|
|
href="#R-AnnotationOnLabel">R-AnnotationOnLabel</a>, <a
|
|
href="#R-RelationshipsBetweenLabels">R-RelationshipsBetweenLabels</a>, <a
|
|
href="#R-LexicalMappingLinks">R-LexicalMappingLinks</a></p>
|
|
|
|
<p>The relationships used among terms include:</p>
|
|
<ul class="descriptions">
|
|
<li>Continuous with [DEF: Two structures are “continuous with” one
|
|
another if they are immediately adjacent and physically connected to one
|
|
another. This relationship is often used for cavitary and tubular
|
|
structures, such as the continuity between the left ventricle and the
|
|
aorta. This is a reflexive relation.]</li>
|
|
<li>Branch of [DEF: a smaller conduit is a “branch of” a larger conduit
|
|
if it is one of a group of two or more conduits that continue in the
|
|
direction of flow where only one conduits had existed before. It is
|
|
permissible for one of the continuing conduits to maintain the same name
|
|
of original conduits. This relation is often used with arteries.]</li>
|
|
<li>Branch [DEF: the converse relation to “branch of”]</li>
|
|
<li>Tributary of [DEF: a smaller conduit is a “tributary of” a larger
|
|
conduit if it is one of a group of two or more vessels that join to form
|
|
a single conduit in the direction of flow. This relation is often used
|
|
with veins. ]</li>
|
|
<li>Tributary [DEF: the converse relation to “tributary of”]</li>
|
|
<li>Part of [DEF: one object is “part of” another object if it
|
|
comprises less than all of the other object. This relation is often used
|
|
with solid body parts and organs.]</li>
|
|
<li>Segment of [DEF: one tubular structure is a “segment of” another if
|
|
it defines a part of that structure divided perpendicular to the axis of
|
|
the tube. This relation is often used to define the subparts of tubular
|
|
structures, such as arteries, veins, and intestines.</li>
|
|
<li>Part [DEF: the converse relation to “part of”]</li>
|
|
<li>Segment [DEF: the converse relation to “segment of”]</li>
|
|
<li>Contained_in [DEF: One structure is “contained in” another if the
|
|
first structure is inside the other. For example the liver is contained
|
|
in the abdominal cavity.]</li>
|
|
<li>Contains [DEF: the converse relation to “contained in”]</li>
|
|
<li>Is_a; Type of</li>
|
|
<li>Member of [DEF: One structure is a “member of” a set of structures.
|
|
For example, the “liver” is a member of the “set of viscera of
|
|
abdomen”]</li>
|
|
<li>Member [DEF: the converse relation to “member of”]</li>
|
|
<li>Synonym [DEF: the term is a less-preferred synonym of a preferred
|
|
term]</li>
|
|
</ul>
|
|
|
|
<p>For instance, “nervous system” has a part called “brain”, and
|
|
“nervous system” contains “nervous system spaces”. The view of the
|
|
hierarchy itself does not reveal the relationships among the terms; this
|
|
information is found within the term features, shown in this format on the
|
|
right-hand side. In this framework, the hierarchy is generated from the
|
|
different relationships among terms, using either SPARQL or a custom
|
|
interface to an application that consumes the terminology.</p>
|
|
|
|
<p>There are 9 separate hierarchies in the vocabulary: Treatment; Image
|
|
acquisition, Processing and Display; Modifier; Finding; Anatomic Location;
|
|
Uncertainty (to be renamed Certainty); Teaching Attribute; Relationship; and
|
|
Image Quality. There are currently no relations holding between terms in
|
|
different hierarchies, though this could be developed in future (e.g. linking
|
|
of particular Findings to potential Anatomic Locations).</p>
|
|
|
|
<p>The Radlex vocabulary is provided in English, with plans to include other
|
|
languages (e.g., German).</p>
|
|
|
|
<p>Requires: <a
|
|
href="#R-MultilingualLexicalInformation">R-MultilingualLexicalInformation</a></p>
|
|
|
|
<p>Protégé has been used to create a machine-readable version of the
|
|
vocabulary, which is available at <a
|
|
href="http://www.rsna.org/radlex/downloads.cfm">http://www.rsna.org/radlex/downloads.cfm</a>.
|
|
RadLex will be available in OWL-DL in the future.</p>
|
|
|
|
<p>Requires: <a
|
|
href="#R-CompatibilityWithOWL-DL">R-CompatibilityWithOWL-DL</a></p>
|
|
|
|
<p>During the design of the vocabulary, basic guidelines from Cimino and
|
|
Chute were used, such as ensuring that a term only corresponds to one
|
|
concept. As the terminology is being developed into a more structured form,
|
|
with more types of relationships, different parents are being allowed as long
|
|
as the relationship type is different. E.g. one IS-A parent, one PART-OF
|
|
parent, etc.</p>
|
|
|
|
<p>Potential changes in the vocabulary are submitted to the chair of the
|
|
RadLex Steering Committee of the Radiological Society of North America, who
|
|
consults with the relevant lexicon development committee. Accepted changes
|
|
are periodically incorporated into the vocabulary. The first release was made
|
|
public in November 2006.</p>
|
|
|
|
<p>Currently, a mapping is being developed between RadLex and the
|
|
corresponding terms/codes in SNOMED (Systematized Nomenclature of Medicine)
|
|
and the ACR (American College of Radiology) Index, the vocabularies that were
|
|
used as a starting point for terminology development.</p>
|
|
|
|
<p>From a representational point of view, this mapping shall consist of
|
|
equivalence and specialization links. Later, we expect people to compose
|
|
atomic terms (post-coordination) to describe composite entities.</p>
|
|
|
|
<p>Requires: <a href="#R-ConceptCoordination">R-ConceptCoordination</a></p>
|
|
<hr />
|
|
|
|
<h3 id="UC-MetadataRegistry">2.8 Use Case #8 — NSDL Metadata Registry</h3>
|
|
|
|
<p><span style="font-size: 10pt">(Contributed by Jon Phipps, Cornell
|
|
University. <br />
|
|
Complete description available at</span> <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/RucMetadataRegistryExtended"
|
|
style="font-size: 10pt">http://www.w3.org/2006/07/SWD/wiki/RucMetadataRegistryExtended</a><span
|
|
style="font-size: 10pt">)</span></p>
|
|
|
|
<p>The NSDL Registry is intended to provide a complete vocabulary development
|
|
and management environment for development of controlled vocabularies.
|
|
Services are primarily directed at vocabulary owners and include provisions
|
|
for:</p>
|
|
<ul class="descriptions">
|
|
<li>managing access and editing rights for groups of vocabulary maintainers
|
|
maintaining individual vocabularies</li>
|
|
<li>import and management of existing vocabularies, with and without
|
|
existing URIs</li>
|
|
<li>namespace management and maintenance services providing permanent
|
|
URIs</li>
|
|
<li>registered users to receive notifications of changes to vocabularies to
|
|
which they have subscribed</li>
|
|
<li>content negotiation for retrieval of registered vocabularies in various
|
|
formats, currently RDF/XML (rdf), XHTML (html), and XML Schema (xsd)</li>
|
|
<li>content negotiation and resolution services for registered vocabularies
|
|
in non-registry namespaces (in alpha)</li>
|
|
<li>controlled concept editing and maintenance using SKOS properties</li>
|
|
<li>controlled editing of reciprocal relationships between concepts
|
|
(Requires: SKOS status property in order to manage reciprocal
|
|
endorsement)</li>
|
|
<li>controlled mapping of relationships between concepts in different
|
|
vocabularies. See <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/RucMetadataRegistryExtended">http://www.w3.org/2006/07/SWD/wiki/RucMetadataRegistryExtended</a>.
|
|
(Requires: <a
|
|
href="#R-ConceptualMappingLinks">R-ConceptualMappingLinks</a>)</li>
|
|
<li>concept-level change history management (Requires: URI content
|
|
negotiation and http 301/302 redirection)</li>
|
|
<li>vocabulary- and concept-level version management (in alpha)</li>
|
|
<li>multilingual vocabulary maintenance (Requires: the ability to manage
|
|
concept equivalence between vocabularies in different languages and
|
|
intra-concept language-related equivalence between concept properties in
|
|
multiple languages)</li>
|
|
<li>skos validation by user input constraint and validation of imported
|
|
vocabularies (Requires: <a
|
|
href="#R-ConsistencyChecking">R-ConsistencyChecking</a>)</li>
|
|
<li>search and browse for concepts by label</li>
|
|
</ul>
|
|
|
|
<p>The registry currently has a number of vocabularies registered. A sample
|
|
entry of a vocabulary/scheme and a single concept are shown below (taken from
|
|
<a
|
|
href="http://metadataregistry.org/uri/NSDLEdLvl.html">http://metadataregistry.org/uri/NSDLEdLvl.html</a>):</p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td>Scheme</td>
|
|
<td>NSDLEdLvl</td>
|
|
</tr>
|
|
<tr>
|
|
<td>Name</td>
|
|
<td>NSDL Education Level Vocabulary</td>
|
|
</tr>
|
|
<tr>
|
|
<td>Owner</td>
|
|
<td>National Science Digital Library</td>
|
|
</tr>
|
|
<tr>
|
|
<td>Community</td>
|
|
<td>Science, Mathematics, Engineering, Technology</td>
|
|
</tr>
|
|
<tr>
|
|
<td>URL</td>
|
|
<td>http://metamanagement.comm.nsdl.org/cgi-bin/wiki.pl?VocabDevel</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p></p>
|
|
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
|
<caption></caption>
|
|
<tbody>
|
|
<tr>
|
|
<td>Concept</td>
|
|
<td>NSDLEdLvl/1023</td>
|
|
</tr>
|
|
<tr>
|
|
<td>Label</td>
|
|
<td>Middle School</td>
|
|
</tr>
|
|
<tr>
|
|
<td>Top Concept</td>
|
|
<td>No</td>
|
|
</tr>
|
|
<tr>
|
|
<td>Status</td>
|
|
<td>published</td>
|
|
</tr>
|
|
<tr>
|
|
<td>history note</td>
|
|
<td>Term source: http://www.ed.gov</td>
|
|
</tr>
|
|
<tr>
|
|
<td>has narrower</td>
|
|
<td>Grade 6</td>
|
|
</tr>
|
|
<tr>
|
|
<td>has narrower</td>
|
|
<td>Grade 7</td>
|
|
</tr>
|
|
<tr>
|
|
<td>has broader</td>
|
|
<td>Grades Pre-K to 12</td>
|
|
</tr>
|
|
<tr>
|
|
<td>alternative label</td>
|
|
<td>Junior High School</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<p></p>
|
|
|
|
<hr />
|
|
|
|
<h3 id="Other">2.9 Other use cases</h3>
|
|
|
|
<p>The SWD Working Group maintains on its wiki site the complete list of
|
|
descriptions that were received following its call for use cases:</p>
|
|
<ul class="descriptions">
|
|
<li id="UC-Tgn">Geographical web service for hierarchical browsing
|
|
(contributed by Walter Koch). <br />
|
|
Summed up description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucTgn">http://www.w3.org/2006/07/SWD/wiki/EucTgn</a>.</li>
|
|
<li id="UC-TacticalSituationObject">Representation of Tactical Situation
|
|
Objects (contributed by Sean Barker). <br />
|
|
Summed up description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucTacticalSituationObject">http://www.w3.org/2006/07/SWD/wiki/EucTacticalSituationObject</a>.</li>
|
|
<li id="UC-GtaaBrowser">GTAA Web Browser (contributed by Véronique
|
|
Malaisé and Hennie Brugman). <br />
|
|
Summed up description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucGtaaBrowser">http://www.w3.org/2006/07/SWD/wiki/EucGtaaBrowser</a>.</li>
|
|
<li id="UC-Obi">Ontology for Biomedical Investigation (OBI) for for
|
|
describing methods in biomedical research (contributed by Trish Whetzel).
|
|
<br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucObiDetailed">http://www.w3.org/2006/07/SWD/wiki/EucObiDetailed</a>.</li>
|
|
<li id="UC-StarDust">The STAR:dust conceptual model (contributed by Irene
|
|
Celino, Emanuele Della Valle and Francesco Corcoglioniti). <br />
|
|
Summed up description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucStarDust">http://www.w3.org/2006/07/SWD/wiki/EucStarDust</a>.</li>
|
|
<li id="UC-UDC">UDC: the Universal Decimal Classification (contributed by
|
|
Antoine Isaac and Aida Slavic). <br />
|
|
Description for motivating <a
|
|
href="#R-ConceptCoordination">R-ConceptCoordination</a> available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucUDC">http://www.w3.org/2006/07/SWD/wiki/EucUDC</a>.</li>
|
|
<li id="UC-Rameau">the RAMEAU subject heading language (contributed by
|
|
Antoine Isaac). <br />
|
|
Description for motivating <a
|
|
href="#R-ConceptCoordination">R-ConceptCoordination</a> available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucRameau">http://www.w3.org/2006/07/SWD/wiki/EucRameau</a>.</li>
|
|
<li id="UC-XMDR">XMDR: Extended Metadata Registry Prototype (contributed by
|
|
John McCarthy). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucXmdrDetailed">http://www.w3.org/2006/07/SWD/wiki/EucXmdrDetailed</a>.</li>
|
|
<li id="UC-Hilt">High-level Thesaurus (HILT) Project (contributed by George
|
|
Macgregor). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucHiltDetailed">http://www.w3.org/2006/07/SWD/wiki/EucHiltDetailed</a>.</li>
|
|
<li id="UC-SeaLife">A Semantic Grid Browser for the Life Sciences Applied
|
|
to the study of Infectious Diseases (contributed by Simon Jupp). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucSeaLifeDetailed">http://www.w3.org/2006/07/SWD/wiki/EucSeaLifeDetailed</a>.</li>
|
|
<li id="UC-PersonalizedTv">Semantic-based Framework for Personalized TV
|
|
Content Management in a cross-media environment (contributed by Pieter
|
|
Bellekens). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucPersonalizedTvDetailed">http://www.w3.org/2006/07/SWD/wiki/EucPersonalizedTvDetailed</a></li>
|
|
<li id="UC-IntraLibrary">intraLibrary: Support for web-based Repository of
|
|
Learning Objects (contributed by Sarah Currier). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucIntraLibraryDetailed">http://www.w3.org/2006/07/SWD/wiki/EucIntraLibraryDetailed</a>.</li>
|
|
<li id="UC-Hanavi">Hybrid and Network-Assisted Vocabulary Interface
|
|
(HANAVI) and Japan National Diet Library List of Subject Headings (NDLSH)
|
|
(contributed by Mitsuharu Nagamori). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucHanaviDetailed">http://www.w3.org/2006/07/SWD/wiki/EucHanaviDetailed</a>.</li>
|
|
<li id="UC-Squiggle">Squiggle: an application framework for model-driven
|
|
development of real-world Semantic Search Engines (contributed by Irene
|
|
Celino). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucSquiggleDetailed">http://www.w3.org/2006/07/SWD/wiki/EucSquiggleDetailed</a>.</li>
|
|
<li id="UC-OpenHypermedia">Conceptual Open Hypermedia Service (COHSE)
|
|
(contributed by Sean Bechhofer). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucCohseDetailed">http://www.w3.org/2006/07/SWD/wiki/EucCohseDetailed</a>.</li>
|
|
<li id="UC-Swed">The Semantic Web Environmental Directory (SWED)
|
|
(contributed by Alistair Miles). <br />
|
|
Detailed description available at <a
|
|
href="http://www.w3.org/2006/07/SWD/wiki/EucSwedDetailed">http://www.w3.org/2006/07/SWD/wiki/EucSwedDetailed</a>.</li>
|
|
</ul>
|
|
<hr />
|
|
|
|
<h2 id="Requirements">3 Requirements</h2>
|
|
|
|
<p>The use cases presented in the previous section motivate a number of
|
|
requirements that the SKOS specification must or should meet in order to
|
|
fulfill its aim as a standard model for porting simple concept schemes on the
|
|
semantic web. Depending on the level of consensus reached in the Working
|
|
Group, these requirements were categorized into <em>accepted</em> and
|
|
<em>candidate</em> requirements. </p>
|
|
|
|
<p>This document reflects decisions that were made just after having received
|
|
the use cases, at the beginning of 2007. The requirements were subsequently
|
|
examined as <em>issues</em> by the Working Group, which decided on actions to
|
|
take—or not—in order to close them. The final status of the issues
|
|
mentioned in this document is accessible via the <em>SWD Issue Tracker</em>,
|
|
at <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues">http://www.w3.org/2006/07/SWD/track/issues</a>.</p>
|
|
|
|
<p>Note: in the following, to avoid ambiguities, <em>vocabulary</em> will be
|
|
used to refer to the <em>SKOS vocabulary</em>, that is, the set of constructs
|
|
(classes, properties) introduced in the SKOS model. <em>Concept Scheme</em>
|
|
will be used to refer to the objects built with SKOS, i.e. the
|
|
application-specific collections of concepts that are mentioned in SKOS use
|
|
cases.</p>
|
|
<hr />
|
|
|
|
<h3 id="Accepted">3.1 Accepted requirements</h3>
|
|
<dl>
|
|
<dt id="R-ConceptualRelations">R-ConceptualRelations</dt>
|
|
<dd><h5 id='_R-ConceptualRelations'>Representation of relationships between concepts</h5>
|
|
The SKOS model shall provide semantic relationships between concepts,
|
|
for display or search purposes. Typical examples are the hierarchical
|
|
relations <em>broader than</em> (BT), <em>narrower than</em> (NT) and
|
|
the non-hierarchical associative relation <em>related to</em> (RT).
|
|
<p><strong>Motivation</strong>: <a href="#UC-Tgn">Tgn</a>, <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a href="#UC-Aims">Aims</a>, <a
|
|
href="#UC-ProductLifeCycleSupport">ProductLifeCycleSupport</a>, <a
|
|
href="#UC-RankingForDescription">RankingForDescription</a>, etc.</p>
|
|
</dd>
|
|
<dt id="R-ConceptSchemeExtension">R-ConceptSchemeExtension</dt>
|
|
<dd><h5 id='_R-ConceptSchemeExtension'>Extension of concept schemes</h5>
|
|
A concept scheme might be locally extended with new concepts referring
|
|
to existing ones, e.g. as specializations of these.
|
|
<p><strong>Motivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a
|
|
href="#UC-BirnLex">BirnLex</a>, <a
|
|
href="#UC-ProductLifeCycleSupport">ProductLifeCycleSupport</a></p>
|
|
</dd>
|
|
<dt id="R-ConceptualMappingLinks">R-ConceptualMappingLinks</dt>
|
|
<dd><h5 id='_R-ConceptualMappingLinks'>Correspondence/Mapping links between concepts from different
|
|
concept schemes</h5>
|
|
In order to build links between concepts coming from different concept
|
|
schemes, SKOS should provide proper semantic relationships. Possible
|
|
links, similarly to the ones found existing SKOS and SKOS mapping
|
|
[<cite><a href="#SWBP-SKOS-MAPPING">SWBP-SKOS-MAPPING</a></cite>]
|
|
vocabularies, include concept equivalence and
|
|
specialization/generalization relations.
|
|
<p><strong>M</strong><strong>otivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a href="#UC-Aims">Aims</a>, <a
|
|
href="#UC-ProductLifeCycleSupport">ProductLifeCycleSupport</a>, <a
|
|
href="#UC-BirnLex">BirnLex</a>, <a
|
|
href="#UC-MetadataRegistry">MetadataRegistry</a></p>
|
|
<p><strong>Corresponding issues</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/39">39</a>, <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/71">71</a></p>
|
|
</dd>
|
|
<dt id="R-LabelRepresentation">R-LabelRepresentation</dt>
|
|
<dd><h5 id='_R-LabelRepresentation'>Representation of basic lexical values (labels) associated to
|
|
concepts</h5>
|
|
The SKOS model shall provide means to represent the labels (preferred
|
|
or not) of a concept, for display or search purposes.
|
|
<p><strong>Motivation</strong>: <a href="#UC-Tgn">Tgn</a>, <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a href="#UC-Aims">Aims</a>, <a
|
|
href="#UC-RankingForDescription">RankingForDescription</a>, etc.</p>
|
|
</dd>
|
|
<dt
|
|
id="R-MultilingualLexicalInformation">R-MultilingualLexicalInformation</dt>
|
|
<dd><h5 id='_R-MultilingualLexicalInformation'>Representation of lexical information in multiple natural
|
|
languages</h5>
|
|
The lexical information specified in concept schemes (labels, but also
|
|
definitions and notes) could come in different natural languages. A
|
|
typical example is the case of a multilingual concept scheme with
|
|
concepts having labels translated in several languages.
|
|
<p><strong>Motivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a> , <a href="#UC-Aims">Aims</a>,
|
|
<a href="#UC-RadLex">RadLex</a></p>
|
|
</dd>
|
|
<dt id="R-SkosSpecialization">R-SkosSpecialization</dt>
|
|
<dd><h5 id='_R-SkosSpecialization'>Local specialization of SKOS vocabulary</h5>
|
|
For particular situations, the designer of a SKOS concept scheme should
|
|
be able to introduce new model-level classes and properties, and link
|
|
them to existing SKOS constructs. Possible cases include the creation
|
|
of specific kinds of textual definitions or notes for concepts, or the
|
|
specification of new types of concepts.
|
|
<p><strong>Motivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a href="#UC-Tgn">Tgn</a>, <a
|
|
href="#UC-Aims">Aims</a>, <a href="#UC-Biozen">Biozen</a>, <a
|
|
href="#UC-RankingForDescription">RankingForDescription</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/37">37</a></p>
|
|
</dd>
|
|
<dt
|
|
id="R-TextualDescriptionsForConcepts">R-TextualDescriptionsForConcepts</dt>
|
|
<dd><h5 id='_R-TextualDescriptionsForConcepts'>Representation of textual descriptions attached to concepts</h5>
|
|
The SKOS model shall provide means to represent descriptive notes that
|
|
could help understanding the elements of concept schemes, e.g. scope
|
|
notes explaining the way concepts are used to describe documents.
|
|
<p><strong>Motivation</strong>: <a href="#UC-Aims">Aims</a>, <a
|
|
href="#UC-ProductLifeCycleSupport">ProductLifeCycleSupport</a>, <a
|
|
href="#UC-TacticalSituationObject">TacticalSituationObject</a>, <a
|
|
href="#UC-BirnLex">BirnLexDetailed</a>, etc.</p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/64">64</a></p>
|
|
</dd>
|
|
</dl>
|
|
<hr />
|
|
|
|
<h3 id="Candidate">3.2 Candidate requirements</h3>
|
|
<dl>
|
|
<dt id="R-AnnotationOnLabel">R-AnnotationOnLabel</dt>
|
|
<dd><h5 id='_R-AnnotationOnLabel'>Ability to represent annotations on lexical items</h5>
|
|
Labels, which are currently modeled as literals in SKOS, as well as
|
|
possibly other literals, are valid subjects of discourse when modeling
|
|
concept schemes, e.g. when recording the dates during which a
|
|
particular label was in common use. However, in RDF only resources may
|
|
be subjects of statements, and literals may only be objects of
|
|
statements. The question then arises, how are we to annotate labels and
|
|
other literals, that is to relate them as subjects, to other entities.
|
|
<p><strong>Motivation</strong>: <a href="#UC-RadLex">RadLex</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/27">27</a></p>
|
|
</dd>
|
|
<dt id="R-CompatibilityWithDC">R-CompatibilityWithDC</dt>
|
|
<dd><h5 id='_R-CompatibilityWithDC'>Compatibility between SKOS and Dublin Core Abstract Model</h5>
|
|
Using SKOS model shall be compatible with using Dublin Core Abstract
|
|
Model [<cite><a href="#DCAM">DCAM</a></cite>]. When there are links
|
|
between SKOS features and Dublin Core ones, these shall be specified.
|
|
<p><strong>Motivation</strong>: <a href="#UC-BirnLex">BirnLex</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/50">50</a></p>
|
|
</dd>
|
|
<dt id="R-CompatibilityWithISO11179">R-CompatibilityWithISO11179</dt>
|
|
<dd><h5 id='_R-CompatibilityWithISO11179'>Compatibility between SKOS and ISO11179[Part 3]</h5>
|
|
SKOS model shall be compatible with part 3 of ISO 11179 specifications
|
|
[<cite><a href="#ISO11179-3">ISO11179-3</a></cite>].
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/51">51</a></p>
|
|
</dd>
|
|
<dt id="R-CompatibilityWithISO2788">R-CompatibilityWithISO2788</dt>
|
|
<dd><h5 id='_R-CompatibilityWithISO2788'>Compatibility between SKOS and ISO2788</h5>
|
|
SKOS model shall be compatible with ISO 2788 specifications [<cite><a
|
|
href="#ISO2788">ISO2788</a></cite>].
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/52">52</a></p>
|
|
</dd>
|
|
<dt id="R-CompatibilityWithISO5964">R-CompatibilityWithISO5964</dt>
|
|
<dd><h5 id='_R-CompatibilityWithISO5964'>Compatibility between SKOS and ISO5964</h5>
|
|
SKOS model shall be compatible with ISO 5964 specifications [<cite><a
|
|
href="#ISO5964">ISO5964</a></cite>].
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/53">53</a></p>
|
|
</dd>
|
|
<dt id="R-CompatibilityWithOWL-DL">R-CompatibilityWithOWL-DL</dt>
|
|
<dd><h5 id='_R-CompatibilityWithOWL'>OWL-DL compatibility</h5>
|
|
SKOS should provide a legal OWL-DL ontology, to be compatible with most
|
|
common editors and reasoners.
|
|
<p><strong>Motivation</strong>: <a href="#UC-Biozen">Biozen</a>, <a
|
|
href="#UC-BirnLex">BirnLex</a>, <a href="#UC-RadLex">RadLex</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/38">38</a></p>
|
|
</dd>
|
|
<dt id="R-ConceptCoordination">R-ConceptCoordination</dt>
|
|
<dd><h5 id='_R-ConceptCoordination'>Coordination of concepts</h5>
|
|
SKOS should provide the ability to create new concepts from existing
|
|
ones, e.g. by using special qualifiers that add a shade of meaning to a
|
|
normal concept.
|
|
<p><strong>Motivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a
|
|
href="#UC-RadLex">RadLex</a>, <a href="#UC-UDC">UDC</a>, <a
|
|
href="#UC-Rameau">Rameau</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/40">40</a></p>
|
|
</dd>
|
|
<dt id="R-ConceptSchemeContainment">R-ConceptSchemeContainment</dt>
|
|
<dd><h5 id='_R-ConceptSchemeContainment'>Ability to explicitly represent the containment of any SKOS
|
|
individual or statement within a concept scheme</h5>
|
|
It shall be possible to explicitly represent the containment of any
|
|
individual which is an instance of a SKOS class (e.g. skos:Concept) or
|
|
statement that uses SKOS property as predicate (e.g. skos:broader)
|
|
within a concept scheme.
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/36">36</a></p>
|
|
</dd>
|
|
<dt id="R-ConsistencyChecking">R-ConsistencyChecking</dt>
|
|
<dd><h5 id='_R-ConsistencyChecking'>Checking the consistency of a concept scheme</h5>
|
|
Some SKOS applications might require testing the integrity of their
|
|
concept scheme data. For example, conceptual relationships should only
|
|
apply to individuals of type skos:Concept, and not for example between
|
|
the (non-preferred) labels of concepts.
|
|
<p><strong>Motivation</strong>: <a
|
|
href="#UC-GtaaBrowser">GtaaBrowser</a>, <a
|
|
href="#UC-MetadataRegistry">MetadataRegistry</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/35">35</a></p>
|
|
</dd>
|
|
<dt id="R-GroupingInConceptHierarchies">R-GroupingInConceptHierarchies</dt>
|
|
<dd><h5 id='_R-GroupingInConceptHierarchies'>Ability to include grouping constructs in concept hierarchies in
|
|
thesauri</h5>
|
|
Concept schemes can contain elements (<em>arrays</em>, <em>guide
|
|
terms</em>, etc.) used to group normal concepts together, e.g. based on
|
|
a shared semantic property. While these special elements cannot be used
|
|
for description purposes, they can be introduced in a concept scheme's
|
|
hierarchy by means of generalization and specialization links.
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/33">33</a></p>
|
|
</dd>
|
|
<dt
|
|
id="R-IndexingAndNonIndexingConcepts">R-IndexingAndNonIndexingConcepts</dt>
|
|
<dd><h5 id='_R-IndexingAndNonIndexingConcepts'>Ability to distinguish between concepts to be used for indexing
|
|
and for non-indexing</h5>
|
|
SKOS should provide different classes for conceptual entities that can
|
|
be used for indexing resources and for those that cannot be used for
|
|
such a purpose (e.g. specific qualifiers that can only be used to
|
|
narrow down the meaning of an existing concept).</dd>
|
|
<dd><strong>Motivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a href="#UC-UDC">UDC</a>, <a
|
|
href="#UC-Rameau">Rameau</a>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/46">46</a></p>
|
|
</dd>
|
|
<dt id="R-IndexingRelationship">R-IndexingRelationship</dt>
|
|
<dd><h5 id='_R-IndexingRelationship'>Ability to represent the indexing relationship between a resource
|
|
and a concept that indexes it</h5>
|
|
The SKOS model should contain mechanisms to attach a given resource
|
|
(e.g. corresponding to a document) to a concept the resource is about,
|
|
e.g. to query for the resources described by a given concept.
|
|
<p><strong>Motivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a
|
|
href="#UC-Biozen">Biozen</a>, <a href="#UC-Aims">Aims</a>, <a
|
|
href="#UC-BirnLex">BirnLex</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/48">48</a></p>
|
|
</dd>
|
|
<dt id="R-LexicalMappingLinks">R-LexicalMappingLinks</dt>
|
|
<dd><h5 id='_R-LexicalMappingLinks'>Correspondence mapping links between lexical labels of concepts
|
|
in different concept schemes</h5>
|
|
In the process of mapping different concept schemes, it should be
|
|
possible to identify correspondence links not only between concepts
|
|
from these concept schemes, but also between the labels that can be
|
|
attached to these concepts.
|
|
<p><strong>Motivation</strong>: <a href="#UC-RadLex">RadLex</a>, <a
|
|
href="#UC-BirnLex">BirnLex</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/49">49</a></p>
|
|
</dd>
|
|
<dt id="R-MappingProvenanceInformation">R-MappingProvenanceInformation</dt>
|
|
<dd><h5 id='_R-MappingProvenanceInformation'>Ability to record provenance information on mappings between
|
|
concepts in different concept schemes</h5>
|
|
It shall be possible to record provenance information on mappings
|
|
between concepts in different concept schemes.
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/47">47</a></p>
|
|
<p>Motivation: <a href="#UC-MetadataRegistry">MetadataRegistry</a></p>
|
|
</dd>
|
|
<dt id="R-RelationshipsBetweenLabels">R-RelationshipsBetweenLabels</dt>
|
|
<dd><h5 id='_R-RelationshipsBetweenLabels'>Representation of links between labels associated to concepts</h5>
|
|
The SKOS model shall provide means to represent relationships between
|
|
the terms associated with concepts. Typical examples are translation
|
|
links between labels from different languages, or the link between one
|
|
label and its abbreviation, when this stands for an alternative label
|
|
for the concept.
|
|
<p><strong>Motivation</strong>: <a
|
|
href="#UC-Manuscripts">Manuscripts</a>, <a href="#UC-Aims">Aims</a>, <a
|
|
href="#UC-RadLex">RadLex</a></p>
|
|
<p><strong>Corresponding issue</strong>: <a
|
|
href="http://www.w3.org/2006/07/SWD/track/issues/26">26</a></p>
|
|
</dd>
|
|
</dl>
|
|
<hr />
|
|
|
|
<h2 id="Conclusion">4 Conclusion</h2>
|
|
|
|
<p>To elicit the requirements that a new version of the Simple Knowledge
|
|
Organization System (SKOS) should meet, the Semantic Web and Deployment
|
|
Working Group has issued a call for use cases to the different communities
|
|
that are concerned by the use of SKOS.</p>
|
|
|
|
<p>More than 25 submissions have been sent to the working group, which
|
|
illustrates the variety of usages one can make of such a proposal. In this
|
|
document, eight of them were selected as being the most representative.</p>
|
|
|
|
<p>Some of these use cases have come with very high-quality descriptions, and
|
|
most correspond to development efforts that are presently being carried out,
|
|
going therefore beyond pure research hypotheses. This has given a sound basis
|
|
for the process of gathering requirements for SKOS, which the second part of
|
|
this document describes.</p>
|
|
|
|
<p>Requirements were divided into accepted and candidate requirements,
|
|
reflecting the level of consensus they had reached in the Working Group at
|
|
the time this document was first created (16 May 2007). In the following
|
|
months, the Working Group had to make a final decision regarding the
|
|
candidate requirements, either accepting them or rejecting them. It of course
|
|
had then to adapt the existing SKOS material so that it could meet the
|
|
accepted requirements.</p>
|
|
<hr />
|
|
|
|
<h2 id="References">References</h2>
|
|
<dl>
|
|
<dt><a name="DCAM" id="DCAM">[DCAM]</a></dt>
|
|
<dd><cite><a href="http://dublincore.org/documents/abstract-model/">DCMI
|
|
Abstract Model</a></cite>, A. Powell, M. Nilsson, A. Naeve, P.
|
|
Johnston, 7 March 2005.</dd>
|
|
<dt><a name="ISO11179-3" id="ISO11179-3">[ISO11179-3]</a></dt>
|
|
<dd><cite><a href="http://metadata-standards.org/11179/#A3">ISO/IEC
|
|
11179-3: 2003(E)</a></cite>, Information Technology – Metadata
|
|
Registries (MDR) – Part 3: Registry metamodel and basic attributes,
|
|
Second edition. R. Gates, Editor, 15 February 2003.</dd>
|
|
<dt><a name="ISO2788" id="ISO2788">[ISO2788]</a></dt>
|
|
<dd><cite><a
|
|
href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=7776">ISO
|
|
2788:1986</a></cite> Documentation - Guidelines for the establishment
|
|
and development of monolingual thesauri. Second edition. ISO TC 46/SC
|
|
9, 1986.</dd>
|
|
<dt><a name="ISO5964" id="ISO5964">[ISO5964]</a></dt>
|
|
<dd><cite><a
|
|
href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=12159">ISO
|
|
5964:1985</a></cite> Documentation - Guidelines for the establishment
|
|
and development of multilingual thesauri. First edition. ISO TC 46/SC
|
|
9, 1985.</dd>
|
|
<dt><a id="SKOS-REFERENCE">[SKOS-REFERENCE]</a></dt>
|
|
<dd><cite><a href="http://www.w3.org/TR/2009/REC-skos-reference-20090818">SKOS
|
|
Reference</a></cite>, Alistair Miles, Sean Bechhofer, Editors, W3C
|
|
Recommendation, 18 August 2009. <a
|
|
href="http://www.w3.org/TR/skos-reference"
|
|
title="Latest version of SKOS Reference">Latest version</a> available
|
|
at http://www.w3.org/TR/skos-reference .</dd>
|
|
<dt><a name="SWBP-SKOS-CORE-GUIDE"
|
|
id="SWBP-SKOS-CORE-GUIDE">[SWBP-SKOS-CORE-GUIDE]</a></dt>
|
|
<dd><cite><a
|
|
href="http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102">SKOS
|
|
Core Guide</a></cite>, A. Miles, D. Brickley, Editors, W3C Working
|
|
Draft (superseded), 2 November 2005. Available at
|
|
http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102.</dd>
|
|
<dt><a name="SWBP-SKOS-CORE-SPEC"
|
|
id="SWBP-SKOS-CORE-SPEC">[SWBP-SKOS-CORE-SPEC]</a></dt>
|
|
<dd><cite><a
|
|
href="http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102">SKOS
|
|
Core Vocabulary Specification</a></cite>, A. Miles, D. Brickley,
|
|
Editors, W3C Working Draft (superseded), 2 November 2005.
|
|
Available at
|
|
http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102.</dd>
|
|
<dt><a name="SWBP-SKOS-MAPPING"
|
|
id="SWBP-SKOS-MAPPING">[SWBP-SKOS-MAPPING]</a></dt>
|
|
<dd><cite><a
|
|
href="http://www.w3.org/2004/02/skos/mapping/spec/2004-11-11.html">SKOS
|
|
Mapping Vocabulary Specification</a></cite>, A. Miles, D. Brickley,
|
|
Editors, W3C Working Draft (superseded), 11 November 2004.
|
|
Available at
|
|
http://www.w3.org/2004/02/skos/mapping/spec/2004-11-11.html.</dd>
|
|
<dt><a id="SWBPD" name="SWBPD">[SWBPD]</a></dt>
|
|
<dd><a href="http://www.w3.org/2001/sw/BestPractices/"><cite>The Semantic
|
|
Web Best Practices and Deployment Working Group</cite></a>,
|
|
http://www.w3.org/2001/sw/BestPractices/.</dd>
|
|
<dt><a id="SWD" name="SWD">[SWD]</a></dt>
|
|
<dd><a href="http://www.w3.org/2006/07/SWD/"><cite>The Semantic Web
|
|
Deployment Working Group</cite></a>,
|
|
http://www.w3.org/2006/07/SWD/.</dd>
|
|
<dt><a id="SWD-Charter" name="SWD-Charter">[SWD-Charter]</a></dt>
|
|
<dd><a href="http://www.w3.org/2006/07/swdwg-charter"><cite>Semantic Web
|
|
Deployment Working Group (SWDWG) Charter</cite></a>,
|
|
http://www.w3.org/2006/07/swdwg-charter.</dd>
|
|
</dl>
|
|
<hr />
|
|
|
|
<h2 id="Acknowledgments">Acknowledgments</h2>
|
|
|
|
<p>The editors gratefully acknowledge contributions from Lora Aroyo, Hugh
|
|
Barnes, Bruce Bargmeyer, Sean Barker, Sean Bechhofer, Pieter Bellekens,
|
|
Hennie Brugman, Dario Cerizza, Irene Celino, Thierry Cloarec, Francesco
|
|
Corcoglioniti, Sarah Currier, Emanuele Della Valle, Diane Hillmann, Chris
|
|
Holmes, Bernard Horan, Julian Johnson, Simon Jupp, Johannes Keizer, Walter
|
|
Koch, Véronique Malaisé, George Macgregor, Frédéric Martin, John
|
|
McCarthy, Emma McCulloch, Alistair Miles, Mitsuharu Nagamori, Dennis
|
|
Nicholson, Matthias Samwald, Margherita Sini, Aida Slavic, Davide
|
|
Sommacampagna, Robert Stevens, Doug Tudhope, Andrea Turati, Bernard Vatant,
|
|
Anna Veronesi.</p>
|
|
</body>
|
|
</html>
|