W3C home > Mailing lists > Public > public-esw-thes@w3.org > January 2008

Re: [Dbpedia-discussion] RE : [ISSUE-77] [ISSUE-48] Re: Skos subject properties are deprecated

From: Mikael Nilsson <mikael@nilsson.name>
Date: Fri, 25 Jan 2008 10:09:16 +0100
To: kidehen@openlinksw.com
Cc: Richard Cyganiak <richard@cyganiak.de>, Antoine Isaac <Antoine.Isaac@KB.nl>, dbpedia-discussion@lists.sourceforge.net, SKOS <public-esw-thes@w3.org>, Simon Spero <sesuncedu@gmail.com>
Message-Id: <1201252156.11008.5.camel@daneel>

On tor, 2008-01-24 at 14:25 -0500, Kingsley Idehen wrote:
> What abot making a generic association via a properly that carries the 
> "Association" or "associatedWith" name and appropriate labeling which 
> also carries natural language comprehension benefits?
> We are trying to tag but in a formal sense. Tagging is about 
> Association, but the association's actual intent lies in the hands of 
> the tagger.

I also think this is the right approach.

I also agree now with Richard that skos:subject and dcterms:subject
convey too much "aboutness". In fact, in many cases, the kind of
relationship implied between a resource and the concept highly depends
on the kind of KOS used:

* for a classification scheme - classifiedAs works well
* for a thesaurus - keyword works well
* in some cases instanceOf works well
* and in other cases subject works well

I think there might be a point in having a generic property attaching a
resource to a Concept, but it has to be as general as "associatedWith".
I also agree with the tagging comparison. In fact, it's not just an
analogy - a tag cloud *is* a KOS, and can be implemented using SKOS.
"subject" will surely be wrong in a number of cases.

I would support a new property with domain Resource, range Concept,
called something like skos:associatedWith.


> A generic property of this nature will mesh with SKOS and MOAT etc..
> Through MOAT and Yago we should be able to make DBpedia tag predicates 
> (whatever is used for categorization) clearer. This will also kill the 
> Person vs Document issue since DBpedia will not implicitly or explicitly 
> infer anyting beyond basic Association across Data Objects (resources) 
> in the Data Graph.


Plus ça change, plus c'est la même chose
Received on Friday, 25 January 2008 09:10:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 13:32:09 UTC