MOAT, Sindice and the Tag Ontology
I just commited two updates for the MOAT module for Drupal 5:
First, in order to add new URIs for a tag, the plugin now uses the sindice Widget that will query Sindice.com and suggests URIs for the used keyword. Then, simply chose the URI, and it will be added as a new meaning for your tag. A big thanks to the Sindice team and especially Adam for modifying the JS regarding the needs of the plugin (and for cool discussions we had about SW 
) !
The next step I want to add in this plug-in is the social networking aspect (since all Meaning instances are related to people that define it, the plug-in could list in priority meanings defined by your friends, using foaf:knows). I’ll certainly need some people to be part of the experiment, so if you’re interesting in it, drop me a mail here or on moat-dev - comment here.
Second change, the plug-in now exports RestrictedTagging objects, while the previous version only exports sioc:topic links. Here’s an example of such an export. It also implied some changes on the sioc module, so you’ll need to update both from cvs if you want to try it. I hope this example (since the website documentation is not that clear at the moment) can help to solve some misunderstood about MOAT, eg (from this this interesting post from Kanzaki Masahide):
You might think this looks more natural if a Tagging has a Meaning, and a person is associated with Tagging, not Meaning. However, since a Tagging can have multiple associatedTag, it is not possible to establish such one-to-one mapping.
Indeed, tagging do not have direct link(s) to Meaning instances, since the Meaning class is context independant (i.e. representing all the meanings a tag can have). Yet, each tagging can have a tagMeaning property, that links to the needed URI. Moreover, to represent this tagging, MOAT implies to use a RestrictedTagging instance, and not a Tagging one, so that there’s only one associated Tag. Person are associated with Tagging (thanks to SIOC in the example, but could be extended with FOAF), and the reason to keep Person associated with the Meaning, is to contextualize it (see the social networking part I mention just before):
<tag:RestrictedTagging> <tag:taggedResource rdf:resource=“http://apassant.net/drupal/drupal-5.5/?q=node/6″/> <sioc:has_creator rdf:resource=“http://apassant.net/drupal/drupal-5.5/?q=sioc/user/1%23_user”/> <tag:associatedTag rdf:resource=“http://tags.moat-project.org/tag/sparql”/> <moat:tagMeaning rdf:resource=“http://dbpedia.org/resource/SPARQL”/> </tag:RestrictedTagging>
Hope that’s more clear, and - this time, for sure - I’ll update the website with more relevant schemas / documents !
-
Current highlights
