SCOT Model and Folksonomy
From Suk Hyung’s comment, he and I try to represent intuitively the SCOT ontology.
In his comment he use three elements for defining a folksonomy as the following:
F = (P, T, R, Y)
where, P : the set of People
T : the set of Words(i.e. “Tags”)
R : the set of Resources
Y \subset P \times T \times R : it represents “tagging”.
There are lots of efforts to define formal model of a folksonomy. For example, Andreas defines the term personomy and folksonomy as a formal concept in his paper(Bibsonomy: A Social Bookmark and Publication Sharing System).
See Definition 1, 2 See Definition 3
I think the basic elements for the folksonomy should be a combination of (user, tag, resource). But when we use folksonomy from del.icio.us, flickr etc a resource is linked by a unique namespace, and user and tag is not a single value. I think it might be hard to describe three elements together.
Ok. what is a main purpose of the SCOT model? The SCOT model aims to represent a folksonomy model. A folksonomy consists of a set of users, a set of tags, and a set of resources, and the set of tag must have frequencies of the individual tags.
To do so, the SCOT model should have a container for three elements. The Tagcloud class has two core properties (scot:tagcloudOf, scot:locatedIn) to describe user, site information and the Tag class has a number of properties to describe semantics of tags. A specific resource can be linked the unique namespace in conjuntion with the tagcloud’s namespace and tag.
Based on James’ model, we try to make abstract relation model for SCOT, SIOC, FOAF, SKOS, and folksonomy. Basically SOCT may has entire elements of folksonomy and could be connected to other RDF vocabularies.
