I am happy to announce that RELAX SEO Services have been released some applications using tags and SCOT(not officially, but you can test them).

Two examples are currently online: http://relaxseo.com/relax-seo-front-page.php and http://relaxseo.com/ac-module-y.php

David Hambly said:

I would characterize our work as a demonstration of the separation between the display (lens) and the source (content). Everything goes through the engine which is RDF aware. It is not a faceted browser but it could be. At present, it does not consult a triples store … but it could.

As an endpoint, it may represent a cloud of relevant links (Knowledge Domains) rendered as a scot ontology (prefered).

The objective shall provide a dynamic representation of knowledge contained within a web site and relationship with other entities (RDF or non-RDF) … as a compliment to dynamic content such as Exhibit, Dapper etc. We care as much about non-RDF as we do RDF and intend to ‘flatten’ wherever possible.

Also you can find more details in here and The Semantic Web comes of age.

I’ve talked with David Hambly from the initial stage of the SCOT project. He gave me great feedback. Thanks, David.
I think we can find out more useful cases from RELAX SEO sooner or later.

We have changed many part of the SCOT ontology. As we mentioned before, SCOT has connected Tag Ontology to describe a tagging activity and links sioc:Item directly using scot:tag_of property.

We will summarize the changes when we release the spec officially. Since this is a draft version for SCOT, some additional changes will happen.

Please feel free to give us any comments and feedbacks.

see SCOT Draft Version

Update

Alexandre Passant gives three comments

• Cardinality issue for tag label: should consider how to apply
• tag name: scot:tag_label is subproperty of tags:name
• scot:created_by: this property is subproperty of foaf:maker

Richard Cyganiak points out that scot:created_by property is confused with scot:has_usergroup. As Alex suggests this property is subproperty of foaf:maker. It might be clear. And he also points out the usefulness of inverse properties. John Breslin already mentioned it.

We are happy to announce that now SCOT has a logo.
When we launched this project, we introduced the folksonomy triangle consisting of a user, a tag, a resource.

Basically, SCOT aims to represent folksonomies beyond individual tagging covered these three components.
The logos illustrates this perspective. Each triangle in the logo means individual taging and each triangle can be connected each other.

John, Sungkwon and I have talked many times to improve SCOT ontology. There are several tag ontologies such as Tag Ontology, MOAT, and even Gruber’s Conceptual Model.

We need to provide a method for interlinking among the existing tag ontologies and also to consider overall pictures for linking among existing RDF vocabularies such as SIOC, FOAF, SKOS, etc. Although we didn’t finish this work at this moment, we would like to give some idea for discussion.

1. Relationship between Tag Ontology and SCOT

Currently, we don’t provide a method to describe individual tagging activity consisted of a user, tags, a resource, and date. The Tag ontology already supports it. So it would be better to use the classes and properties of Tag Ontology. The change is that scot:Tagcloud connects to tags:Tagging class with scot:taggingActivity and also scot:Tag is subclass of tags:Tag.

2. We will change two properties scot:taggedItem (subproperty of tags:taggedResource and scot:tagUsed (subproperty of tags:associatedTag).

3. The following picture illustrates simplified view of SCOT vocabularies.

4. We will change the properties associated with scot:Tagcloud and scot:Tag.

Tagcloud class

Tag class

Cooccurrence class

We are happy to hear any comments and feedbacks.
updated: March 7, 2008.

SCOT used in the OpenLink system. More details see New Features in OpenLink Data Spaces.

@From Kingsley’s comment. It’s so good example to use SCOT and other RDF vocabularies. See OpenLink RDF Browser:

We released the SCOT Exporter for WordPress v0.7.
The main change is that there is an option to set a location to save a SCOT instance. In v0.6, the location is fixed in http://yourhost/scot/scot.rdf. But some people have wanted to change the location what they want. Well, it might be easy, but after changing the location, it cannot be connected to resources with tags. Now, the problem has fixed. You can change the location in scot-setting.php.

define(”SCOT_REL_PATH”, “wp-content/”);

Just put a folder name instead of “wp-content”.

And also we support the Ultimate Tag Warrior for WordPress. There are two types of exporter.

SCOT Exporter for WordPress: It aims to generate SCOT instance based on categories of WordPress

SCOT Exporter for UTW: Ultimate Tag Warrior provides comprehensive tagging features for WordPress. The exporter for UTW create SCOT instance using real tags based on the UTW plugin.

We released the SCOT Exporter for WordPress v0.6.

Some functionalities are changed and added:

• scot.rdf is located in “http://yourhost/scot/scot.rdf”
• skos:narrower and skos:broader property
• scot:tagspace property
• scot:totalPosts
• scot:totalTags
• scot:totalTagFrequency
• scot:Cooccurrences
• scot:CooccurFrequency
• rdfs:seealso for tag navigation

The main change is that broader-narrower relationship can be automatically represented in a scot ontology. It is based on a tag frequencies and its co-occurrence frequencies.
In addition, there is a simple linking method between a tag and a resouce using scot ontology. For instance, if there is ‘web‘ as a tag it will be represented

scot:Tag rdf:about=”http://yourhost/tag/web”

Also it has rdfs:label like “http://yourhost/scot/tag.php?tag=web” to be linked to resources in your blog. It is very simple method to combine tag-resource based on scot ontology. We have a plan to improve the method in next version.

Please test it and feel free to give any comment.

We are happy to inform that http://int.ere.st is launching. The main objective of int.ere.st is to demonstrate how Semantic Web and Web2.0 technologies can be combined to provide better metadata creating and sharing support across online communities. With int.ere.st, you can save, tag and bookmark your own as well as others’ SCOT ontologies. The tag meta search allows you to look for similar patterns of tagging of persons with their interest based on tags. Various functionalities are given as following:

various tag search: and(&), or(space), co-occurrence(+), broader(>), and narrower(<)
User search
Meta tagging
Resource search
Ontology bookmark
Integrate tagged data across communities
Share FOAF, SIOC, and SCOT ontologies

You can try it at http://int.ere.st
We will release a next version of the SCOT exporter as soon as possible.

We are happy the TagCommons added the link of SCOT project in the web site. The TagCommons has the goal as following.

The goal of this effort is to specify an agreement that specifies a common semantics and possible means for sharing or computing over tag data from heterogeneous, independently developed sources. This is a technology stack of a conceptualization, ontologies that formally specify it, and bridges to symbol-level formats and APIs.

The SCOT project has almost same goal. We try to provide the framework for sharing and reusing social tagging data and to provide the APIs. We will find out how to interlink different tag ontologies.

There are some changes in the SCOT as following:

• Add and make up for the descriptions of properties
• Add scot:associatedBy property (11-06-2007)
• Change property name
• scot:totalPosts -> scot:totalItems
• scot:totalTag -> scot:totalTags
• scot:equivalentTag -> scot:spellingVariant(07-06-2007)
• Add the subProperty and subClassOf relation
• scot:composedOf is a subProperty of dcterms:hasPart
• scot:name is a subProperty of dc:title
• scot:Tagcloud is subclass of sioc:Container
• scot:synonym is subProperty of “http://www.holygoat.co.uk/owl/redwood/0.1/tags/equivalentTag” (07-06-2007)
• Change domain values
• scot:frequency, scot:AFrequency, and scot:RFrequency have the domain value as scot:Tagcloud