index.html 45.5 KB

Raw Blame History Permalink

<?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" xml:lang="en" lang="en">

<head>
	<meta name="RCS-Id" content="$Id: Overview.html,v 1.13 2009/10/24 11:37:02 apassant Exp $" />
	<title>SIOC, SIOC Types and Health Care and Life Sciences</title>
	<style type="text/css">
table {
  border-width: 1px;
  border-style: solid;
  border-color: black;
  border-collapse: collapse;
}

table th, table td {
  border:1px solid black;
  text-align: left;
  padding: 5px;
}

.todo {
	color: #f00;
	font-weight: bold;
}

.figref {
  font-style: italic;
  font-size: 90%;
}
	</style>
	<!-- link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base" / -->
	<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-IG-NOTE"/>
</head>

<body>

<div class="head">
	<p><a href="http://www.w3.org/">
	<img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a></p>

	<h1 id="main">SIOC, SIOC Types and Health Care and Life Sciences</h1>
      <h2 class="no-num no-toc" id="w3c-doctype">W3C Interest Group Note 20 October 2009</h2>

<dl>
	<dt>This version:</dt>
	<dd><a href="http://www.w3.org/TR/2009/NOTE-hcls-sioc-20091020/">http://www.w3.org/TR/2009/NOTE-hcls-sioc-20091020/</a></dd>
	<dt>Latest version:</dt>
	<dd><a href="http://www.w3.org/TR/hcls-sioc/">http://www.w3.org/TR/hcls-sioc/</a></dd>

	<dt>Editor:</dt>
	<dd><a href="http://apassant.net/">Alexandre Passant</a>, <a href="http://www.deri.ie/">DERI Galway at the National University of Ireland, Galway, Ireland</a> &lt;<a href="mailto:alexandre.passant@deri.org">alexandre.passant@deri.org</a>&gt;</dd>

	<dt>Contributors:</dt>
	<dd><a href="http://captsolo.net/">Uldis Bojars</a>, <a href="http://www.deri.ie/">DERI Galway at the National University of Ireland, Galway, Ireland</a> &lt;<a href="mailto:uldis.bojars@deri.org">uldis.bojars@deri.org</a>&gt;</dd>
	<dd><a href="http://www.johnbreslin.org/">John G. Breslin</a>, <a href="http://www.deri.ie/">DERI Galway at the National University of Ireland, Galway, Ireland</a> &lt;<a href="mailto:john.breslin@deri.org">john.breslin@deri.org</a>&gt;</dd>
</dl>

<p class="copyright">

	<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &#169; 2008 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&#174;</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 title="Separator for header" />

<div>
<h2 class="notoc" id="abstract">Abstract</h2>
<p>
As in several other scientific domains, the use of social software (such as blogs or wikis) and social networking applications is now commonly accepted in the Health Care and Life Science (HCLS) research community, with services such as <a href="http://hypothesis.alzforum.org/swan/">the SWAN Alzheimer Knowledge Base</a>, <a href="http://www.myexperiment.org/">myExperiment</a>, <a href="http://www.wikiprofessional.org/">WikiProfessional Concept Web</a>, <a href="http://www.connotea.org/">Connotea</a> and <a href="http://network.nature.com/">Nature Networks</a>.
In general, however, these applications suffer from a lack of interoperability, and this makes the reuse of information a complex task.
The SIOC Ontology - Semantically-Interlinked Online Communities - aims to solve these issues and provides a comprehensive model to represent online communities and related user-generated content items thanks to Semantic Web technologies. This note describes the changes to the SIOC Core Ontology since its <a href="http://www.w3.org/Submission/2007/02/">W3C Member Submission</a> in June 2007, the SIOC Types Module, and their relevance in the Health Care and Life Sciences context.
</p>
</div>

    <div>
      <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 http://www.w3.org/TR/.</em></p>

      <p>This W3C Interest Group Note describes how one can use the Semantic Web to express and integrate scientific data.  These techniques can be used for modeling any data, and the benefits of integration and model consistency apply to other diverse, distributed data domains.  It is hoped that this document will inspire further contributions to the ongoing work at Neurocommons and the Health Care and Life Sciences Interest Group, as well as inspire those in other domains to exploit the Semantic Web.</p>

      <p class="notetoeditor">This document describes the <em>SIOC</em> ontology for semantically-interlinked online communities. The companion document <a href="/TR/2009/NOTE-hcls-swan-20091020/">Semantic Web Applications in Neuromedicine (SWAN) Ontology</a> describes the <em>SWAN</em> ontology for expressing scientific discourse, and <a href="/TR/2009/NOTE-hcls-swansioc-20091020/">SWAN/SIOC: Alignment Between the SWAN and SIOC Ontologies</a> describes the the use of <em>SWAN</em> and <em>SIOC</em> together to model discourse within scientific communities.</p>

<p>The document was produced by the <a href="http://www.w3.org/2001/sw/hcls/">Semantic Web in Health Care and Life Sciences Interest Group (HCLS)</a>, part of the <a href="http://www.w3.org/2001/sw/">W3C Semantic Web Activity</a> (<a href="http://www.w3.org/2008/05/HCLSIGCharter">see charter</a>). Comments may be sent to the <a href="http://lists.w3.org/Archives/Public/public-semweb-lifesci/">publicly archived</a> <a href="mailto:public-semweb-lifesci@w3.org">public-semweb-lifesci@w3.org</a> mailing list. In addition, the authors welcome suggestions on the SIOC Core Ontology and the SIOC Types Module; please send comments to the <a href="http://groups.google.com/group/sioc-dev">SIOC developers' mailing list</a> (SIOC-Dev), <a href="http://groups.google.com/group/sioc-dev/topics">public archives</a> are available.
</p>

<p>The SIOC Core Ontology as well as the SIOC Types Module may be updated in the future, but no commitment is made by the authors regarding future updates.</p>

<p>Publication as an Interest 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>The disclosure obligations of the Participants of this group are described in the <a href="http://www.w3.org/2008/05/HCLSIGCharter.html">charter</a>.</p>

    </div>

<hr/>

<div class="toc">
	<h2 id="contents">Table of Contents</h2>
	<ul class="toc">
		<li class="tocline1"><a href="#intro">1. Introduction</a>
		<ul>
			<li class="tocline2"><a href="#intro_motivations">1.1. Motivations for the SIOC Project in Health Care and Life Sciences</a></li>
			<li class="tocline2"><a href="#intro_organization">1.2. Organization of the SIOC Ontology</a></li>
		</ul>
		</li>
		<li class="tocline1"><a href="#sioc">2. The SIOC Core Ontology</a>
		<ul>
			<li class="tocline2"><a href="#sioc_core">2.1. Overview of the SIOC Core Ontology</a></li>
			<li class="tocline2"><a href="#sioc_changes">2.2. Changes since the Member Submission</a></li>
		</ul>
		</li>
		<li class="tocline1"><a href="#types">3. The SIOC Types Module</a>
		<ul>
			<li class="tocline2"><a href="#types_aims">3.1. Aims of the Types Module</a></li>
			<li class="tocline2"><a href="#types_classes">3.2. Classes and mappings with existing vocabularies</a></li>
			<li class="tocline2"><a href="#types_example">3.3. Example of RDF data using the SIOC Types module</a></li>
			<li class="tocline2"><a href="#types_query">3.4. Querying RDF data using the SIOC Types Module</a></li>
		</ul>
		</li>
		<li class="tocline1"><a href="#usecases">4. Use cases for SIOC and its Types Module in HCLS</a>
		<ul>
			<li class="tocline2"><a href="#usecases1">4.1. Integrating information from Web 2.0 services in a pharmaceutical company</a></li>
			<li class="tocline2"><a href="#usecases2">4.2. Sharing patient information on the Web</a></li>
		</ul>
		</li>
		<li class="tocline1"><a href="#conclusion">5. Conclusion</a></li>
	</ul>
</div>

<div class="toc">
	<h2 id="appendices">Appendices</h2>
	<ul class="toc">
		<li class="tocline1"><a href="#namespaces">A1. Namespaces used in this document</a></li>
		<li class="tocline1"><a href="#references">A2. References</a></li>
		<li class="tocline1"><a href="#ack">A3. Acknowledgements</a></li>
	</ul>
</div>

<hr/>

<h2 id="intro">1. Introduction</h2>

<h3 id="intro_motivations">1.1. Motivations for the SIOC Project in Health Care and Life Sciences</h3>

<p>Social media is now a well-accepted paradigm, not only for
leisure-oriented Web 2.0 applications but also in scientific communities,
especially in the Health Care and Life Sciences context. Researchers
can share their experiments and opinions using weblogs, build knowledge
collaboratively through the use of wikis, use social networking tools to gather
information around topics and publications, etc., hence using social
media as a complement to traditional paper publications. Some popular social media tools for researchers include <a href="http://hypothesis.alzforum.org/swan/">the SWAN Alzheimer Knowledge Base</a>, <a href="http://www.myexperiment.org/">myExperiment</a>, <a href="http://www.wikiprofessional.org/">Wiki Professional</a>, and <a href="http://connotea.org/">Connotea</a>.
</p>

<p>However, social media services generally act as independent and
disconnected data silos that cannot communicate very efficiently with
each other. There are no bridges between them that could be used, for
example, to retrieve from a wiki a list of items about topics retrieved
from several weblogs. Moreover, sharing information between these
services is also an important issue: generally, when people upload some
content to a service, it can only be commented on (or sometimes only be
viewed) by people registered on that service.
</p>

<p>The SIOC Project (Semantically-Interlinked Online Communities) aims
to provide models and tools to achieve this goal of interoperability
between online communities and related user-generated content. It uses
Semantic Web technologies including a set of ontologies, tools and related
services. Complete information about SIOC can be found on the <a href="http://sioc-project.org/">SIOC Project</a> website as well as on the <a href="http://wiki.sioc-project.org/">SIOC Wiki</a>, and some background is given in the paper entitled "<a href="http://www.w3.org/2008/09/msnws/papers/sioc.html">SIOC: Content Exchange and Semantic Interoperability Between Social Networks</a>" from the W3C Workshop on the Future of Social Networking.
</p>

<p>
In particular in the context of the Health Care and Life Sciences community,
SIOC enables integration between different platforms and communities of
researchers that share information, experience and publications on
various topics.
By providing a common and machine-readable format for modeling
communities and their data via Semantic Web technologies, it also
permits advanced querying and browsing capabilities over this data, as
well as re-use in other contexts.
</p>

<h3 id="intro_organization">1.2. Organization of the SIOC Ontology</h3>

<p>The SIOC Ontology is the foundation of the SIOC Project. The various
tools and services from the project are based on this data model in
order to publish, exchange and consume data between social media
websites and applications.
This ontology is defined in two main parts:
</p>
<ul>
	<li>The SIOC Core Ontology, available at <a href="http://rdfs.org/sioc/ns">http://rdfs.org/sioc/ns</a></li>
	<li>The SIOC Ontology Modules</li>
</ul>
<p>Four modules for SIOC have been designed so far, a fifth one being the
module defining mappings with the SWAN ontology, described in detail in
[<a href="#ref-swansioc">SWAN-SIOC</a>].
The four other modules are defined as follows:
</p>
<ul>
	<li>The Types Module: <a href="http://rdfs.org/sioc/types">http://rdfs.org/sioc/types</a>.
This module provides advanced content types to be used when defining
user-generated content from online communities. It will be described in
detail in a <a href="#sioctypes">following section</a> of this document</li>
	<li>The Access Module: <a href="http://rdfs.org/sioc/access">http://rdfs.org/sioc/access</a>. This module provides the notions of <a href="http://rdfs.org/sioc/types#Role">Role</a> and <a href="http://rdfs.org/sioc/types#Permission">Permission</a> as a simple way to define access rights and permissions in online communities.</li>
	<li>The Services Module: <a href="http://rdfs.org/sioc/services">http://rdfs.org/sioc/services</a>. This module provides a way to represent Web services related to online communities (APIs, SPARQL endpoints, etc.).</li>
	<li>The Argumentation Module: <a href="http://rdfs.org/sioc/argument">http://rdfs.org/sioc/argument</a>. This module provides a way to represent simple argumentative discussions in online communities.</li>
</ul>

<h2 id="sioc">2. The SIOC Core Ontology</h2>

<h3 id="sioc_core">2.1. Overview of the the SIOC Core Ontology</h3>

<p>
Since further details about the SIOC Core Ontology itself can be found on its related Member Submission [<a href="#ref-siocsubmission">SIOC-MemberSubmission</a>] and on its current live specification [<a href="#ref-siocspec">SIOC-Specification</a>], we will simply give a brief overview of the model in this note.
</p>

<p>
The SIOC Core Ontology [<a href="#ref-siocspec">SIOC-Specification</a>] currently consists of 11 classes and about 50 properties.
The following schema represents the main classes and properties of the SIOC Core Ontology.
Two classes are not shown here: the <a href="http://rdfs.org/sioc/ns#Community">sioc:Community</a> class, that aims at representing a collection of people, services and content around a particular topic of interest, and the <a href="http://rdfs.org/sioc/ns#Thread">sioc:Thread</a> class, a subclass of <a href="http://rdfs.org/sioc/ns#Container">sioc:Container</a> dedicated to representing threaded discussions, such as those that occur on bulletin boards.
</p>

<div class="figure">
<img src="main_classes_properties.png" alt="The SIOC Core Ontology"/>
<p class="figref">
  Figure 1: The SIOC Core Ontology
</p>
</div>

<p>
The SIOC Ontology also has strong ties with other vocabularies, such as FOAF [<a href="#ref-foaf">FOAF</a>], SKOS [<a href="#ref-skos">SKOS</a>] and Dublin Core [<a href="#ref-dc">DublinCore</a>].
The [<a href="#ref-siocmappings">SIOC-Mappings</a>]
document provides an overview of the different mappings between SIOC
and these models. As an example, the following source code represents
how an item on a web site can be modeled with SIOC and these related
vocabularies using N3 notation.
</p>

<div class="figure">

<p id="sioc-ex-core" class="figref">
Table 1: Example of SIOC data using the SIOC Core Ontology
</p>

<pre class="example" style="border: 1px dotted #0C0C0C; padding: 15px; background: rgb(217, 227, 233) none repeat scroll 0% 0%;">@prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
@prefix sioc: &lt;http://rdfs.org/sioc/ns#&gt; .
@prefix dct: &lt;http://purl.org/dc/terms/&gt; .
@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .

&lt;http://example.org/blog/2009/03/hcls&gt; rdf:type sioc:Post ;
  dct:title "Upcoming HCLS events" ;
  dct:created "2009-03-12"^^xsd:date ;
  sioc:has_creator &lt;http://example.org/user/bob&gt; ;
  sioc:has_container &lt;http://example.org/blog&gt; ;
  sioc:has_reply &lt;http://example.org/comment/42&gt; ;
  sioc:content "The following events might be of interest for the HCLS community..." ;
  sioc:topic &lt;http://example.org/topics/hcls&gt; .

&lt;http://example.org/bob&gt; rdf:type sioc:User ;
  sioc:name "Bob" .

&lt;http://example.org/blog&gt; rdf:type sioc:Forum ;
  sioc:name "Bob's blog" .

&lt;http://example.org/comment/42&gt; rdf:type sioc:Post ;
  dct:title "Alice's comment" .
</pre>

</div>

<h3 id="sioc_changes">2.2. Changes Since the Member Submission</h3>

<p>
Several changes have happened since the SIOC Core Ontology was published as a <a href="http://www.w3.org/Submission/2007/SUBM-sioc-spec-20070612/">W3C Member Submission</a>.
Most
enhancements have been based on discussions that happened on the
SIOC developers mailing list based on implementation needs and experience.
While no new classes have been introduced (in order to keep the model
lightweight), the following changes have been made to the SIOC Core
Ontology's classes and properties (changes are ordered by alphabetical
order for properties and classes):
</p>

<dl>

<dt>Adding new properties</dt>
<dd>The following properties have been added:
	<ul>
		<li><a href="http://rdfs.org/sioc/spec/#term_has_discussion">sioc:has_discussion</a>:
The has_discussion property links any sioc:Item to a related
discussion. The discussion can be anything, for example, a sioc:Forum,
a sioct:WikiArticle or simply a foaf:Document.</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_earlier_version">sioc:earlier_version</a>:
The earlier_version property links any sioc:Item to any earlier (i.e.
older) version. This is a transitive property. The related
non-transitive property that links any sioc:Item to its immediately
older version is previous_version. previous_version is a subproperty of
earlier_version.</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_later_version">sioc:later_version</a>:
The later_version property links any sioc:Item to any later (i.e.
newer) version. This is a transitive property. The related
non-transitive property, that links any sioc:Item to its immediately
newer version is next_version. next_version is a subproperty of
later_version.</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_latest_version">sioc:latest_version</a>:
The latest_version property links a sioc:Item to its latest version.
This can be used to link a previous version of an item (e.g. a wiki
page) to its latest version.</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_follows">sioc:follows</a>: Indicates that one User follows another User (e.g. for microblog posts or other content item updates).</li>
	</ul>
</dd>

<dt>Changing the domain (rdfs:domain) and range (rdfs:range) of existing properties</dt>
<dd>The domain and / or range following properties have been edited:
	<ul>
		<li><a href="http://rdfs.org/sioc/spec/#term_related_to">sioc:related_to</a>: Removed domain and range</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_has_creator">sioc:has_creator</a>: Removed domain</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_creator_of">sioc:creator_of</a>: Removed range</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_scope_of">sioc:scope_of</a>: Removed domain and range</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_has_scope">sioc:has_scope</a>: Removed domain and range</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_num_replies">sioc:num_replies</a>: Removed domain</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_content">sioc:content</a>: Changed domain to sioc:Item</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_attachment">sioc:attachment</a>: Changed domain to sioc:Item</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_note">sioc:note</a>: Removed domain</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_has_owner">sioc:has_owner</a>: Removed domain</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_owner_of">sioc:owner_of</a>: Removed range</li>
	</ul>
</dd>

<dt>Internal mappings</dt>
<dd>The following mappings have been defined:
	<ul>
		<li><a href="http://rdfs.org/sioc/spec/#term_reply_of">sioc:reply_of</a> property has been defined as a subproperty of <a href="http://rdfs.org/sioc/spec/#term_related_to">sioc:related_to</a></li>
		<li><a href="http://rdfs.org/sioc/spec/#term_has_reply">sioc:has_reply</a> property has been defined as a subproperty of <a href="http://rdfs.org/sioc/spec/#term_related_to">sioc:related_to</a></li>
	</ul>
</dd>

<dt>Mappings with other vocabularies</dt>
<dd>As a way to improve the mappings with existing vocabularies, the following changes have been committed:
	<ul>
		<li><a href="http://rdfs.org/sioc/spec/#term_account_of">sioc:account_of</a>: Defined as an inverse property of foaf:holdsAccount</li>
		<li><a href="http://rdfs.org/sioc/spec/#term_avatar">sioc:avatar</a>: Defined as a subproperty of foaf:depiction.</li>
	</ul>
In addition, while the specification originally used both the Dublin
Core Element Set and the Dublin Core Terms namespaces, these were
recently combined and we now simply use the single Dublin Core Terms namespace.
</dd>

</dl>

<p>
Another major update is the OWL-DL compliance of the model, which was previously OWL-Full.
Further details about this change are detailed in the SWAN/SIOC document.
</p>

<p>Finally we want to emphasize that more changes may happen in the
future, even regarding the properties and classes that are mentioned in
the previous inventory of SIOC changes.
</p>

<h2 id="types">3. The SIOC Types Module</h2>

<h3 id="types_aims">3.1. Aims of the Types Module</h3>

<p>While the SIOC Core Ontology defines a set of classes that can be
used to represent user-generated content, both in terms of items (<a href="http://rdfs.org/sioc/ns#Post">sioc:Post</a> and <a href="http://rdfs.org/sioc/ns#Item">sioc:Item</a>) and containers (<a href="http://rdfs.org/sioc/ns#Forum">sioc:Forum</a> and <a href="http://rdfs.org/sioc/ns#Container">sioc:Container</a>), these may still not be fine-grained enough for some knowledge representation purposes.
For example, using the <a href="http://rdfs.org/sioc/ns#Item">sioc:Item</a> class does not differentiate between a blog post, a wiki page or a post on a bulletin board.
In a similar way, using <a href="http://rdfs.org/sioc/ns#Container">sioc:Container</a> does not provide a way to differentiate (when querying information) between a weblog, a wiki, or a photo gallery.
</p>

<p>
In order to provide more fine-grained modeling of user-generated
content, the SIOC Types Module defines a set of classes that extend the
main classes of the SIOC Core Ontology.
The following figure represents how both a wiki and a wiki article can
be represented using the SIOC Types Module, respectively using the <a href="http://rdfs.org/sioc/types#Wiki">sioct:Wiki</a> and the <a href="http://rdfs.org/sioc/types#WikiArticle">sioct:WikiArticle</a> classes, defined respectively as subclasses of <a href="http://rdfs.org/sioc/ns#Forum">sioc:Forum</a> and <a href="http://rdfs.org/sioc/ns#Post">sioc:Post</a>, themselves being defined as subclasses of <a href="http://rdfs.org/sioc/ns#Container">sioc:Container</a> and <a href="http://rdfs.org/sioc/ns#Item">sioc:Item</a>.
</p>


<div class="figure" id="core-types">
<img src="core-types.png" alt="Relationships between the SIOC Core Ontology and the Types module"/>
<p class="figref">
  Figure 2: Relationships between the SIOC Core Ontology and the Types module
</p>
</div>

<h3 id="types_classes">3.2. Classes in the Types Module and mappings with existing vocabularies</h3>

<p>
This section provides a complete list of the different classes defined
in the Types Module, as well as their mappings with related classes in
the SIOC Core Ontology.
</p>

<h4 id="types_containers">3.2.1. Containers and forums</h4>

<p>The following lists introduce the various containers and forums
introduced in the SIOC Types Module.
It also presents for each Container and Forum the related items that could be
contained therein.
As one can see, some items are defined within the SIOC namespace (hence
being described in the next section), while some of them are existing
concepts from different vocabularies.
It is important to mention that there are no constraints in the
ontology so that these relationships between container and items are
informative only and not subject to any kind of reasoning at the
moment.
</p>

<div class="figure">

<p class="figref">
Table 2: List of subclasses of sioc:Container defined in the SIOC Types Module
</p>

<table>
<tbody><tr>
	<th>Container</th>
	<th>Related Item</th>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#AddressBook">sioct:AddressBook</a></td>
	<td>none</td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#AnnotationSet">sioct:AnnotationSet</a></td>
	<td><a href="http://www.w3.org/2000/10/annotation-ns#Annotation">annot:Annotation</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#AudioChannel">sioct:AudioChannel</a></td>
	<td><a href="http://purl.org/dc/dcmitype/Sound">dcmit:Sound</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#BookmarkFolder">sioct:BookmarkFolder</a></td>
	<td><a href="http://www.w3.org/2002/01/bookmark#Bookmark">bookmark:Bookmark</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#Briefcase">sioct:Briefcase</a></td>
	<td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#EventCalendar">sioct:EventCalendar</a></td>
	<td><a href="http://www.w3.org/2002/12/cal/icaltzd#">ical:VEVENT</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#ImageGallery">sioct:ImageGallery</a></td>
	<td><a href="http://www.w3.org/2003/12/exif/ns#IFD">exif:IFD</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#ProjectDirectory">sioct:ProjectDirectory</a></td>
	<td><a href="http://usefulinc.com/ns/doap#Project">doap:Project</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#ResumeBank">sioct:ResumeBank</a></td>
	<td><a href="http://captsolo.net/semweb/resume/cv.rdfs#">resume:Resume</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#ReviewArea">sioct:ReviewArea</a></td>
	<td><a href="http://purl.org/stuff/rev#Review">rev:Review</a> and <a href="http://www.isi.edu/webscripter/communityreview/abstract-review-o#Review">abr:Review</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#SubscriptionList">sioct:SubscriptionList</a></td>
	<td><a href="http://bblfish.net/work/atom-owl/2006-06-06/AtomOwl.rdf#Feed">owl:Feed</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#SurveyCollection">sioct:SurveyCollection</a></td>
	<td><a href="http://rdfs.org/sioc/types#Poll">sioct:Poll</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#VideoChannel">sioct:VideoChannel</a></td>
	<td><a href="http://purl.org/dc/dcmitype/Image">dcmit:Image</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#Wiki">sioct:Wiki</a></td>
	<td><a href="http://rdfs.org/sioc/types#WikiArticle">sioct:WikiArticle</a></td>
</tr>
</tbody></table>

</div>


<div class="figure">

<p class="figref">
Table 3: Subclasses of <a href="http://rdfs.org/sioc/ns#Forum">sioc:Forum</a> from the SIOC Types Module
</p>

<table>
<tbody><tr>
	<th>Forum</th>
	<th>Related Item (Post)</th>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#ArgumentativeDiscussion">sioct:ArgumentativeDiscussion</a></td>
	<td><a href="http://purl.org/ibis#Idea">ibis:Idea</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#ChatChannel">sioct:ChatChannel</a></td>
	<td><a href="http://rdfs.org/sioc/types#InstantMessage">sioct:InstantMessage</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#MailingList">sioct:MailingList</a></td>
	<td><a href="http://rdfs.org/sioc/types#MailMessage">sioct:MailMessage</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#MessageBoard">sioct:MessageBoard</a></td>
	<td><a href="http://rdfs.org/sioc/types#BoardPost">sioct:BoardPost</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#Microblog">sioct:Microblog</a></td>
	<td><a href="http://rdfs.org/sioc/types#MicroblogPost">sioct:MicroblogPost</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#Weblog">sioct:Weblog</a></td>
	<td><a href="http://rdfs.org/sioc/types#BlogPost">sioct:BlogPost</a></td>
</tr>
</tbody></table>

</div>

<h4 id="types_items">3.2.2. Items and posts</h4>

<p>To a similar extent, the SIOC Types Module defines subclasses of
sioc:Item and sioc:Post as shown below along with their related
containers.
As in the previous section, there is no formal relationship between the
proposed items and containers.
</p>

<div class="figure">

<p class="figref">
Table 4: Subclasses of <a href="http://rdfs.org/sioc/ns#Item">sioc:Item</a> from the SIOC Types Module
</p>

<table>
<tbody><tr>
	<th>Item</th>
	<th>Related Container</th>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#Poll">sioct:Poll</a></td>
	<td><a href="http://rdfs.org/sioc/types#SurveyCollection">sioct:SurveyCollection</a></td>
</tr>
</tbody></table>

</div>

<div class="figure">

<p class="figref">
Table 5: Subclasses of <a href="http://rdfs.org/sioc/ns#Post">sioc:Post</a> from the SIOC Types Module
</p>

<table>
<tbody><tr>
	<th>Post</th>
	<th>Related Container</th>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#BlogPost">sioct:BlogPost</a></td>
	<td><a href="http://rdfs.org/sioc/types#Weblog">sioct:Weblog</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#BoardPost">sioct:BoardPost</a></td>
	<td><a href="http://rdfs.org/sioc/types#MessageBoard">sioct:MessageBoard</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#Comment">sioct:Comment</a></td>
	<td><a href="http://rdfs.org/sioc/types#Forum">sioct:Forum</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#InstantMessage">sioct:InstantMessage</a></td>
	<td><a href="http://rdfs.org/sioc/types#ChatChannel">sioct:ChatChannel</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#MailMessage">sioct:MailMessage</a></td>
	<td><a href="http://rdfs.org/sioc/types#MailingList">sioct:MailingList</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#MicroblogPost">sioct:MicroblogPost</a></td>
	<td><a href="http://rdfs.org/sioc/types#Microblog">sioct:Microblog</a></td>
</tr>
<tr>
	<td><a href="http://rdfs.org/sioc/types#WikiArticle">sioct:WikiArticle</a></td>
	<td><a href="http://rdfs.org/sioc/types#Wiki">sioct:Wiki</a></td>
</tr>
</tbody></table>

</div>

<p>
In addition, the module introduces the three following classes (as subclasses of <a href="http://rdfs.org/sioc/ns#Post">sioc:Post</a>) to model questions and answers in online communities:
</p>

<ul>
	<li><a href="http://rdfs.org/sioc/types#Question">sioct:Question</a>: A post that asks a question.</li>
	<li><a href="http://rdfs.org/sioc/types#Answer">sioct:Answer</a>: A post that provides an answer in reply to a question.</li>
	<li><a href="http://rdfs.org/sioc/types#BestAnswer">sioct:BestAnswer</a>: A post that is the best answer to a question, as chosen by the user who asked the question or as voted by a community of users.</li>
</ul>

<p>Finally, in order to represent the topics and tags that can be
assigned to such items, the Types Module introduces these two classes:
</p>

<ul>
	<li><a href="http://rdfs.org/sioc/types#Category">Category</a>:
Category is used on the object of sioc:topic to indicate that this
resource is a category on a site. This class is used in order to define
categories that can be assigned, e.g. to a blog post or wiki page, and
generally pre-defined by administrators of the service. <a href="http://rdfs.org/sioc/types#Category">sioct:Category</a> is a subclass of <a href="http://www.w3.org/2008/05/skos#Concept">skos:Concept</a>, hence categories can be ordered hierarchically.</li>
	<li><a href="http://rdfs.org/sioc/types#Tag">Tag</a>:
Tag is used on the object of sioc:topic to indicate that this resource
is a tag on a site. This class is used in order to represent free-text
tags, but assign them a particular URI. For more advanced tagging
capabilities, models such as the Tag Ontology [<a href="#ref-tagong">TagOntology</a>], [<a href="#ref-scot">SCOT</a>], [<a href="#ref-moat">MOAT</a>] or [<a href="#ref-ctag">CommonTag</a>] can be considered.</li>
</ul>

<h3 id="types_example">3.3. Example of RDF data using the SIOC Types Module</h3>

<p>
The following example extends <a href="#sioc-ex-code">the previous one</a>, using the Types module to model more precisely the different objects that have been created.
It uses <a href="http://rdfs.org/sioc/types#BlogPost">sioct:BlogPost</a> (instead of the more generic <a href="http://rdfs.org/sioc/ns#Post">sioc:Post</a>), <a href="http://rdfs.org/sioc/types#Weblog">sioct:Weblog</a> (a subclass of <a href="http://rdfs.org/sioc/ns#Container">sioc:Container</a>), <a href="http://rdfs.org/sioc/types#Comment">sioct:Comment</a> and <a href="http://rdfs.org/sioc/types#Category">sioct:Category</a>.
As one can see, it does not imply any other changes, neither in terms of properties nor mappings with other vocabularies.
</p>

<div class="figure">

<p class="figref">
Table 6: Example of SIOC data using the SIOC Types Module
</p>

<pre class="example" style="border: 1px dotted #0C0C0C; padding: 15px; background: rgb(217, 227, 233) none repeat scroll 0% 0%;">@prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
@prefix sioc: &lt;http://rdfs.org/sioc/ns#&gt; .
@prefix sioct: &lt;http://rdfs.org/sioc/types#&gt; .
@prefix dct: &lt;http://purl.org/dc/terms/&gt; .
@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .

&lt;http://example.org/blog/2009/03/hcls&gt; rdf:type sioct:BlogPost ;
  dct:title "Upcoming HCLS events" ;
  dct:created "2009-03-12"^^xsd:date ;
  sioc:has_creator &lt;http://example.org/user/bob&gt; ;
  sioc:has_container &lt;http://example.org/blog&gt; ;
  sioc:has_reply &lt;http://example.org/comment/42&gt; ;
  sioc:content "The following events might be of interest for the HCLS community..." ;
  sioc:topic &lt;http://example.org/topics/hcls&gt; .

&lt;http://example.org/bob&gt; rdf:type sioc:User ;
  sioc:name "Bob" .

&lt;http://example.org/blog&gt; rdf:type sioct:Weblog ;
  sioc:name "Bob's blog" .

&lt;http://example.org/comment/42&gt; rdf:type sioct:Comment ;
  dct:title "Alice's comment" .

&lt;http://example.org/topics/hcls&gt; rdf:type sioct:Category .
</pre>

</div>

<h3 id="types_query">3.5. Querying RDF data using the SIOC Types Module</h3>

<p>
As an example of how SIOC can be used when querying data, the following
SPARQL query retrieves all the blog posts (as well as their creators and
titles) that have at least one reply, as well as the related reply.
</p>

<div class="figure">

<p class="figref">
Table 7: Example of SPARQL query for SIOC data
</p>

<pre class="example" style="border: 1px dotted #0C0C0C; padding: 15px; background: rgb(217, 227, 233) none repeat scroll 0% 0%;">PREFIX sioc: &lt;http://rdfs.org/sioc/ns#&gt;
PREFIX sioct: &lt;http://rdfs.org/sioc/types#&gt;
PREFIX dct: &lt;http://purl.org/dc/terms/&gt;
PREFIX rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;

SELECT ?post ?creator ?title ?reply
WHERE {
  ?post rdf:type sioct:BlogPost ;
    sioc:has_creator ?creator ;
    dct:title ?title ;
    sioc:has_reply ?reply .
  ?reply rdf:type sioct:Comment .
}
</pre>

</div>

<p>
Applied to the previous example, the following answer will be retrieved.
</p>

<div class="figure">

<p class="figref">
Table 8: Example of SPARQL query results for SIOC data
</p>

<table>
<tbody><tr>
	<th>?post</th>
	<th>?creator</th>
	<th>?title</th>
	<th>?reply</th>
</tr>
<tr>
	<td>http://example.org/blog/2009/03/hcls</td>
	<td>http://example.org/user/bob</td>
  <td>Upcoming HCLS events</td>
	<td>http://example.org/comment/42</td>
</tr>
</tbody></table>

</div>

<h2 id="usecases">4. Use cases for SIOC in HCLS</h2>

<h3 id="usecases1">4.1. Integrating information from Web 2.0 services in a pharmaceutical company</h3>

<p>ACME Pharma uses various blogs, wikis and microblogging applications
to enable communication and knowledge sharing between its different
research teams.
However, since various tools have been implemented and deployed, based on
the different needs of the internal communities, it is difficult to query and
retrieve information from all of these systems.
By providing SIOC exports for all of this data, and through the use of existing
applications / APIs [<a href="#ref-siocapps">SIOC-Applications</a>]
and a single RDF repository to store this data, it is then possible to
query the data from a single place using uniform SPARQL queries.
Moreover, these queries can take advantage of the SIOC Types module,
for example, to retrieve only instances of <a href="http://rdfs.org/sioc/types#WikiArticle">sioct:WikiArticle</a> or <a href="http://rdfs.org/sioc/types#BlogPost">sioct:BlogPost</a>, depending on the kind of information that is to be retrieved.
This use case is similar to what is described in [<a href="#sweo-edf">SWEO-EDF</a>]
and can be implemented with currently-available Semantic Web
technologies, especially the ones described in this document, i.e. SIOC
and its Types Module.
</p>

<h3 id="usecases2">4.2 Sharing patient information on the Web</h3>

<p>Alice and Bob suffer from diabetes, and often blog about research
findings, the drugs they are using, their treatments, etc. As a matter
of transparency and in order to share their experiences with other
patients, as well as with their doctors, they provide SIOC exports of
their blog data.
Each conversation is therefore available as open and machine-readable
information.
Thanks to this openness, this data can be consumed by pharmaceutical
companies via existing SIOC tools [<a href="#ref-siocapps">SIOC-Applications</a>] so that they can track discussions about the drugs that people are using, and provide feedback if needed.
Thanks to the use of the SIOC Types Module, people consuming the data can distinguish the original blogged information (<a href="http://rdfs.org/sioc/types#BlogPost">sioct:BlogPost</a>) from the comments (<a href="http://rdfs.org/sioc/types#Comment">sioct:Comment</a>).
It is worth noting that, for each blog post, Alice and Bob have the
ability - to ensure privacy - to not export it as SIOC data.
</p>

<h2 id="conclusion">5. Conclusion</h2>

<p>In this note, we described the changes to the SIOC Ontology since
its Member Submission as well as the SIOC Types Module. In particular, we
focused on the use of SIOC in the context of communities of researchers
and scientists from the Health Care and Life Science domain. As shown
in the use cases section, SIOC can be efficiently deployed as a means
to integrate information from various applications and communities in a
unified, machine-readable and comprehensive way, offering new
possibilities in terms of scientific knowledge management.
</p>

<h2 id="namespaces">A1. Namespaces used in this document</h2>

<table>
<tr>
	<th>Prefix</th>
	<th>XML Namespace (linked to the RDF schema)</th>
	<th>Specification (human-readable)</th>

</tr>
<tr>
	<td>abr</td>
	<td><a href="http://www.isi.edu/webscripter/communityreview/abstract-review-o">http://www.isi.edu/webscripter/communityreview/abstract-review-o#</a></td>
	<td><a href="http://www.isi.edu/webscripter/communityreview/">The Semantic Web Community Review Project</a></td>
</tr>
<tr>
	<td>annot</td>
	<td><a href="http://www.w3.org/2000/10/annotation-ns#">http://www.w3.org/2000/10/annotation-ns#</a></td>

	<td><a href="http://www.w3.org/2000/10/annotation-ns#">Annotea Annotation Schema</a></td>
</tr>
<tr>
	<td>aowl</td>
	<td><a href="http://bblfish.net/work/atom-owl/2006-06-06/AtomOwl.rdf">http://bblfish.net/work/atom-owl/2006-06-06/#</a></td>
	<td><a href="http://bblfish.net/work/atom-owl/2006-06-06/AtomOwl.html">AtomOwl Vocabulary Specification</a></td>
</tr>
<tr>
	<td>bookmark</td>

	<td><a href="http://www.w3.org/2002/01/bookmark#">http://www.w3.org/2002/01/bookmark#</a></td>
	<td><a href="http://www.w3.org/2002/01/bookmark#">Bookmark schema</a></td>
</tr>
<tr>
	<td>content</td>
	<td><a href="http://purl.org/rss/1.0/modules/content/">http://purl.org/rss/1.0/modules/content/</a></td>
	<td><a href="http://purl.org/rss/1.0/modules/content/">RSS 1.0 Content Module</a></td>

</tr>
<tr>
	<td>doap</td>
	<td><a href="http://usefulinc.com/ns/doap#">http://usefulinc.com/ns/doap#</a></td>
	<td><a href="http://trac.usefulinc.com/doap">DOAP Vocabulary</a></td>
</tr>
<tr>
	<td>dc</td>
	<td><a href="http://purl.org/dc/elements/1.1/">http://purl.org/dc/elements/1.1/</a></td>

	<td><a href="http://dublincore.org/documents/dces/">The Dublin Core Metadata Element Set</a></td>
</tr>
<tr>
	<td>dcmit</td>
	<td><a href="http://purl.org/dc/dcmitype/">http://purl.org/dc/dcmitype/</a></td>
	<td><a href="http://dublincore.org/documents/dcmi-terms">DCMI Metadata Terms</a></td>
</tr>
<tr>
	<td>dct</td>
	<td><a href="http://purl.org/dc/terms/">http://purl.org/dc/terms/</a></td>
	<td><a href="http://dublincore.org/documents/dcmi-terms">DCMI Metadata Terms</a></td>
</tr>
<tr>
	<td>ical</td>
	<td><a href="http://www.w3.org/2002/12/cal/icaltzd#">http://www.w3.org/2002/12/cal/icaltzd#</a></td>
	<td><a href="http://www.w3.org/2002/12/cal/">RDF Calendar</a></td>

</tr>
<tr>
	<td>exif</td>
	<td><a href="http://www.w3.org/2003/12/exif/ns#">http://www.w3.org/2003/12/exif/ns#</a></td>
	<td><a href="http://www.w3.org/2003/12/exif/">Exif RDF Schema</a></td>
</tr>
<tr>
	<td>foaf</td>
	<td><a href="http://xmlns.com/foaf/0.1/index.rdf">http://xmlns.com/foaf/0.1/</a></td>

	<td><a href="http://xmlns.com/foaf/0.1/spec">Friend of a Friend (FOAF) Vocabulary</a></td>
</tr>
<tr>
	<td>ibis</td>
	<td><a href="http://purl.org/ibis#">http://purl.org/ibis#</a></td>
	<td><a href="http://hyperdata.org/xmlns/ibis/">IBIS Vocabulary</a></td>
</tr>
<tr>
	<td>resume</td>
	<td><a href="http://captsolo.net/semweb/resume/cv.rdfs#">http://captsolo.net/semweb/resume/cv.rdfs#</a></td>
	<td><a href="http://rdfs.org/resume-rdf/">ResumeRDF vocabulary</a></td>
</tr>
<tr>
	<td>rev</td>
	<td><a href="http://www.purl.org/stuff/rev#">http://www.purl.org/stuff/rev#</a></td>
	<td><a href="http://vocab.org/review/terms.html">http://vocab.org/review/terms.html</a></td>

</tr>
<tr>
	<td>sioc</td>
	<td><a href="http://rdfs.org/sioc/ns#">http://rdfs.org/sioc/ns#</a></td>
	<td><a href="http://rdfs.org/sioc/spec">SIOC Core Ontology</a></td>
</tr>
<tr>
	<td>skos</td>
	<td><a href="http://www.w3.org/2004/02/skos/core#">http://www.w3.org/2004/02/skos/core#</a></td>
	<td><a href="http://www.w3.org/TR/skos-reference/skos.html">SKOS Namepasce Document</a></td>
</tr>
</table>

<h2 id="references">A2. References</h2>

<dl>

<dt><a name="ref-Schemes">[FOAF]</a></dt>
<dd>
The Friend of a Friend (FOAF) Project. See <a href="http://www.foaf-project.org/">http://www.foaf-project.org/</a>

</dd>

<dt><a name="ref-Schemes">[SKOS]</a></dt>
<dd>
Alistair Miles, Sean Bechhofer (eds.),
SKOS Simple Knowledge Organization System,
W3C Proposed Recommendation 15 June 2009,
<a href="http://www.w3.org/TR/skos-reference/">http://www.w3.org/TR/skos-reference/</a>
</dd>

<dt><a name="ref-ctag">[CommonTag]</a></dt>
<dd>
The Common Tag Project. See <a href="http://commontag.org">http://commontag.org</a>
</dd>

<dt><a name="ref-dc">[DublinCore]</a></dt>
<dd>
Dublin Core Metadata Initiative. See <a href="http://dublincore.org/">http://dublincore.org/</a>
</dd>

<dt><a name="ref-moat">[MOAT]</a></dt>
<dd>
The Meaning Of A Tag (MOAT) Project. See <a href="http://moat-project.org/">http://moat-project.org/</a>
</dd>

<dt><a name="ref-scot">[SCOT]</a></dt>
<dd>
The Social Semantic Cloud of Tags (SCOT) Project. See <a href="http://scot-project.org/">http://scot-project.org/</a>
</dd>

<dt><a name="ref-siocapps">[SIOC-Applications]</a></dt>
<dd>
SIOC Applications,
The SIOC Wiki,
<a href="http://wiki.sioc-project.org/index.php/Category:Applications">http://wiki.sioc-project.org/index.php/Category:Applications</a>
</dd>

<dt><a name="ref-siocmappings">[SIOC-Mappings]</a></dt>

<dd>
Uldis Bojars, John G. Breslin, Alexandre Passant, Axel Polleres (eds.),
SIOC Ontology: Related Ontologies and RDF Vocabularies,
W3C Member Submission 12 June 2007,
<a href="http://www.w3.org/Submission/2007/SUBM-sioc-related-20070612/">http://www.w3.org/Submission/2007/SUBM-sioc-related-20070612/</a>
</dd>

<dt><a name="ref-siocsubmission">[SIOC-MemberSubmission]</a></dt>
<dd>
Uldis Bojars, John G. Breslin (eds.),
SIOC Core Ontology Specification,
W3C Member Submission 12 June 2007,
<a href="http://www.w3.org/Submission/2007/SUBM-sioc-spec-20070612/">http://www.w3.org/Submission/2007/SUBM-sioc-spec-20070612/</a>
</dd>

<dt><a name="ref-siospec">[SIOC-Specification]</a></dt>
<dd>

Uldis Bojars, John G. Breslin (eds.),
SIOC Core Ontology Specification,
Evolving document,
<a href="http://rdfs.org/sioc/spec">http://rdfs.org/sioc/spec</a>
</dd>

<dt><a name="ref-swansioc">[SWAN-SIOC]</a></dt>
<dd>
Alexandre Passant, Paolo Ciccarese (eds.),
SWAN/SIOC: Alignment between the SWAN and SIOC ontologies,
W3C HCLS IG Editor's Draft,
<a href="http://www.w3.org/2001/sw/hcls/notes/swansioc/">http://www.w3.org/2001/sw/hcls/notes/swansioc/</a>
</dd>

<dt><a name="ref-sweo">[SWEO-EDF]</a></dt>
<dd>
Alexandre Passant,
Case Study: Enhancement and Integration of Corporate Social Software Using the Semantic Web,
W3C Semantic Web Education and Outreach Case-Study,

<a href="http://www.w3.org/2001/sw/sweo/public/UseCases/EDF/">http://www.w3.org/2001/sw/sweo/public/UseCases/EDF/</a>
</dd>

<dt><a name="ref-tagont">[TagOntology]</a></dt>
<dd>
The Tag Ontology. See <a href="http://www.holygoat.co.uk/projects/tags/">www.holygoat.co.uk/projects/tags/</a>
</dd>

</dl>

<h2 id="ack">A3. Acknowledgements</h2>

<p>
We would like to particularly thank (in alphabetical order) Paolo
Ciccarese, Tim Clark, Scott Marshall and Susie Stephens for their
valuable comments and feedback during the writing and editing of this
note. We also thank Eric Prud'hommeaux for the subversion magic and
technical assistance with the creation of this document, as well as the
entire Scientific Discourse Task Force, and more generally the Health
Care and Life Science Interest Group within the W3C.
</p>

</body>

</html>