W3C home > Mailing lists > Public > public-gld-wg@w3.org > April 2013

ISSUE-59 (FC-HierarchicalCodeList): Last Call comment. Frank Cotton on qb:HierarchicalCodeList [Data Cube Vocabulary]

From: Government Linked Data Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 10 Apr 2013 12:49:38 +0000
Message-Id: <E1UPuT4-00012R-7T@tibor.w3.org>
To: public-gld-wg@w3.org
ISSUE-59 (FC-HierarchicalCodeList): Last Call comment. Frank Cotton on qb:HierarchicalCodeList [Data Cube Vocabulary]


Raised by: Dave Reynolds
On product: Data Cube Vocabulary

Last Call comment from Frank Cotton: http://lists.w3.org/Archives/Public/public-gld-comments/2013Apr/0061.html

On the whole, I am very hesitant about the introduction of the qb:HierarchicalCodeList class and associated properties. This raises the more general problem of how to derive SKOS concept schemes from sets of resources that have some kind of "real world" hierarchical relations that are not hierarchies between codes in a code list, but hierarchies in some specific sense between objects. The example of geographic territories is a good one: here you have the territorial inclusion relation that induces a broader/narrower relation between associated items in a code list, but of course we do not want to make a confusion between a region, for example, and an item in a code scheme, nor between territorial inclusion and "broader concept". It seems to me that the approach you describe fuels a bit the confusion.

A different approach would be to explicitely generate a SKOS concept scheme parallel to the "real world" hierarchy and to use a property like foaf:focus to link the concepts to the things they represent (see http://lists.w3.org/Archives/Public/public-esw-thes/2010Aug/0002.html).

I think that this is a very general problem that should be addressed in an ad hoc W3C or other group aimed at developing a recommanded practice, rather than treated here and there in different fashions.
Received on Wednesday, 10 April 2013 12:49:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:52:07 UTC