Abstract
The SIOC (Semantically-Interlinked Online Communities) Core Ontology provides the main concepts and properties required to describe information from online communities (e.g., message boards, wikis, weblogs, etc.) on the Semantic Web. This document contains a brief description of the relationship between SIOC and other selected relevant ontologies or vocabularies.
Status of this document
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 can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document is a part of the SIOC Ontology Submission, and is based on the SIOC Related Ontologies page on the ESW wiki.
Authors welcome suggestions on the SIOC Core Ontology Specification and this document. Please send comments to the SIOC developers' mailing list (SIOC-Dev), public archives are available. This document may be updated or added to based on implementation experience, but no commitment is made by the authors regarding future updates.
Please consult the namespaces.zip archive, a part of this submission, for a snapshot of the SIOC Ontology namespaces referenced in this document. Live namespace documents are located at relevant namespace URIs.
By publishing this document, W3C acknowledges that the Submitting Members have made a formal Submission request to W3C for discussion. Publication of this document by W3C indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. This document is not the product of a chartered W3C group, but is published as potential input to the W3C Process. A W3C Team Comment has been published in conjunction with this Member Submission. Publication of acknowledged Member Submissions at the W3C site is one of the benefits of W3C Membership. Please consult the requirements associated with Member Submissions of section 3.3 of the W3C Patent Policy. Please consult the complete list of acknowledged W3C Member Submissions.
Table of contents
1. Introduction
SIOC aims to incorporate and reuse existing vocabularies as far as possible in order to avoid redundancies and to enable the use of richer metadata descriptions for specific domains. In this document, we outline concrete relations to other existing RDF vocabularies and describe overlaps with SIOC terms.
This document refers to version 1.26 of the SIOC Core Ontology Namespace from 12 June 2007.
1.1. Terminology and Notation
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Namespace URIs of the general form "http://www.example.com/" represent some application-dependent or context-dependent URI as defined in RFC 2396.
2. Dublin Core
The Dublin Core Metadata Initiative (DCMI) provides a basic set of properties and types for annotating documents.
2.1. Linking to and reusing Dublin Core
SIOC has many hooks to Dublin Core. Posts, Forums, and other SIOC terms can be annotated with particular information about coverage, creation, etc. using DC elements and their refinements. Particularly, SIOC recommends the reuse of Dublin Core elements (dc) and refinements (dcterms) for describing properties such as creation date (dcterms:created), modification date (dcterms:modified), parts (dcterms:hasPart / dcterms:isPartOf), title (dc:title), and subject keywords (dc:subject), thereby deprecating proprietary properties in earlier versions of SIOC. Also, content types of sioc:attachment(s) can be further specified via DCMI Types, and sioc:avatar can have resources of type dctype:Image.
2.2. Example
Describing some sioc:Post properties using Dublin Core:
<sioc:Post rdf:about="http://example.org/blog/2006/08/09/104-sample-post">
<dc:title>Sample Post</dc:title>
<dcterms:created>2006-08-03T22:50:32Z</dcterms:created>
<dcterms:modified>2006-09-19T23:36:05Z</dcterms:modified>
<dc:subject>Paris, France</dc:subject>
[...]
</sioc:Post>
3. FOAF
The FOAF vocabulary specifies the most important features related to people acting in online communities. The vocabulary allows us to specify properties about people commonly appearing on personal homepages, and to describe links between people who know each other.
3.1. Linking to and reusing FOAF
The sioc:User concept is a subclass of the foaf:OnlineAccount concept, so linking a sioc:User to a foaf:Person can be done using the foaf:holdsAccount property (or in the reverse direction using sioc:account_of). By means of this link, one can refer further to properties of the real person behind a user. Note that a sioc:User can also be related to a foaf:Agent and its subclass foaf:Group, so that a group of people can share a common account.
3.2. Using both FOAF and SIOC
When linking a sioc:Post to its creator, two options are offered:
- The first one is to use a "sioc:Post sioc:has_creator sioc:User" statement.
- The second one is to use a "sioc:Post foaf:maker foaf:Person" statement.
Even if the second statement could be inferred from the first one (using the foaf:holdsAccount property), we suggest that exporters use both, and use only the foaf:maker statement when describing a post created by a non-registered user (e.g., a blog comment).
3.3. Example
Using both FOAF and SIOC for a post / creator relationship:
<sioc:Post rdf:about="http://example.org/blog/2006/08/09/104-sample-post">
<dc:title>Sample Post</dc:title>
<dcterms:created>2006-08-03T22:50:32Z</dcterms:created>
<sioc:has_creator>
<sioc:User rdf:about="http://example.org/blog/#bob">
<rdfs:seeAlso rdf:resource="http://example.org/blog/sioc.php?type=user&user_id=bob"/>
</sioc:User>
</sioc:has_creator>
<foaf:maker>
<foaf:Person rdf:about="http://example.org/blog/#foaf_bob">
<rdfs:seeAlso rdf:resource="http://example.org/blog/sioc.php?type=user&user_id=bob"/>
</foaf:Person>
</foaf:maker>
[...]
</sioc:Post>
RDF Site Summary, also known as "Really Simple Syndication", is a web content syndication format used to describe lists (so called channels) of news items via syndicated feeds, very similar to how forum entries are treated in SIOC. While there is an RDF format developed by the RSS-Dev group, RSS 1.0 (which we refer to here), nowadays the XML format RSS 2.0, released in 2003 through Harvard under a Creative Commons license, is more widely adopted and is supported by all major browsers or special feed readers.
SIOC exceeds RSS somewhat in terms of its expressivity for the content found in online communities, but RSS terms are very useful for reuse in SIOC due to their wide usage and support (especially RSS 2.0).
SIOC also encourages the use of the RSS 1.0 Content Module, using content:encoded for describing the rich content of a sioc:Post, while sioc:content is used for a plain text rendering.
Using both sioc:content and content:encoded (from the RSS 1.0 Content Module) to display the content of a sioc:Post:
<sioc:Post rdf:about="http://example.org/blog/2006/08/09/104-sample-post">
<dc:title>Sample Post</dc:title>
<dcterms:created>2006-08-03T22:50:32Z</dcterms:created>
<content:encoded><![CDATA[<p>This is a <b>sample post</b></p>]]></content:encoded>
<sioc:content>This is a sample post</sioc:content>
[...]
</sioc:Post>
5. SKOS
SKOS, a W3C Working Draft, is developing specifications and standards to support the use of knowledge organisation systems (KOS) such as thesauri, classification schemes, subject heading lists, taxonomies, other types of controlled vocabulary, as well as terminologies and glossaries, within the framework of the Semantic Web.
5.1. Linking to and reusing SKOS
SIOC recommends that sioc:topic(s) link to categories defined in a SKOS category hierarchy.
5.2. Example
Linking a sioc:Post to a SKOS concept defined for Paris:
<sioc:Post rdf:about="http://example.org/blog/2006/08/09/104-sample-post">
<dc:title>Sample Post</dc:title>
<dcterms:created>2006-08-03T22:50:32Z</dcterms:created>
<sioc:topic>
<skos:Concept rdf:about="http://example.org/skos/concepts#Paris">
<skos:prefLabel xml:lang="fr">Paris</skos:prefLabel>
<skos:prefLabel xml:lang="en">Paris</skos:prefLabel>
</skos:Concept>
</sioc:topic>
[...]
</sioc:Post>
6. Other ontologies
SIOC can also link sioc:Post(s) to any ontology instances or classes using the sioc:topic property in order to define what the topic of a Post is.
6.1. Example
Linking a sioc:Post to the geonames.org instance for Paris:
<sioc:Post rdf:about="http://example.org/blog/2006/08/09/104-sample-post">
<dc:title>Sample Post</dc:title>
<dcterms:created>2006-08-03T22:50:32Z</dcterms:created>
<sioc:topic>
<geoname:Feature rdf:about="http://sws.geonames.org/2988507/">
<rdfs:seeAlso rdf:resource="http://sws.geonames.org/2988507/about.rdf"/>
<geoname:Feature>
</sioc:topic>
[...]
</sioc:Post>
7. Sample sioc:Post
Here is the complete sample document used for the examples in this document, using a number of different ontologies within a single sioc:Post definition:
<sioc:Post rdf:about="http://example.org/blog/2006/08/09/104-sample-post">
<dc:title>Sample Post</dc:title>
<dcterms:created>2006-08-03T22:50:32Z</dcterms:created>
<dcterms:modified>2006-09-19T23:36:05Z</dcterms:modified>
<dc:subject>Paris, France</dc:subject>
<sioc:has_creator>
<sioc:User rdf:about="http://example.org/blog/#bob">
<rdfs:seeAlso rdf:resource="http://example.org/blog/sioc.php?type=user&user_id=bob"/>
</sioc:User>
</sioc:has_creator>
<foaf:maker>
<foaf:Person rdf:about="http://example.org/blog/#foaf_bob">
<rdfs:seeAlso rdf:resource="http://example.org/blog/sioc.php?type=user&user_id=bob"/>
</foaf:Person>
</foaf:maker>
<content:encoded><![CDATA[<p>This is a <b>sample post</b></p>]]></content:encoded>
<sioc:content>This is a sample post</sioc:content>
<sioc:topic>
<skos:Concept rdf:about="http://example.org/skos/concepts#Paris">
<skos:prefLabel xml:lang="fr">Paris</skos:prefLabel>
<skos:prefLabel xml:lang="en">Paris</skos:prefLabel>
</skos:Concept>
</sioc:topic>
<sioc:topic>
<geoname:Feature rdf:about="http://sws.geonames.org/2988507/">
<rdfs:seeAlso rdf:resource="http://sws.geonames.org/2988507/about.rdf"/>
</geoname:Feature>
</sioc:topic>
</sioc:Post>
8. Conclusion and future work
In this document, we discussed some important related vocabularies. The ExpertFinder Initiative plans to further investigate overlaps and correlations between existing RDF vocabularies as future work.
A related topic is the creation of machine-readable definitions for describing how ontologies could optionally be used with each other, for example: suggesting external properties that can be used with local domain or range classes (plus external ones if required); suggesting external classes (and local ones if required) that could be used as the domain or range for local properties; providing sample RDF instance data for such suggestions, etc.
As there are some incompatibilities between RDFS and OWL DL (e.g., there exists a validation conflict when defining the sioc:topic object property as a subtype of the dc:subject datatype property), we also recommend that future OWL working groups should examine any such incompatibilities and also issue some best practices on how to address these when combining RDFS and OWL DL ontologies.
9. Ontology namespaces referenced
10. References
- [RFC 2119] S. Bradner,
"Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, Harvard University, March 1997, http://www.ietf.org/rfc/rfc2119.txt.
- [RFC 2396] T. Berners-Lee et al., "Uniform Resource Identifiers
(URI): Generic Syntax", RFC 2396, Internet Engineering Task Force, August 1998, http://www.ietf.org/rfc/rfc2396.txt.
11. Change log
- 2006-10-12: Initial version of this document.
- 2006-10-22: Added part on other ontologies and various examples.
- 2007-05-30: Revisions for member submission.
uldis.bojars@deri.org
john.breslin@deri.org