RE: ISSUE-39 (QB-skos:Collection): Data Cube: Allow skos:Collections as value of qb:codeList [Data Cube Vocabulary]

Benedikt,

Shouldn't all code sets be skos:ConceptSchemes?  Conceptually speaking, that is what they are.  In XKOS, we made Level a kind of Collection, if memory serves.  However, I now see that all kinds of inconsistencies or extra work can arise through this.  This is because a Level could also be a code set itself.

I am not sure I am answering your question.

Yours,
Dan

-----Original Message-----
From: Benedikt Kaempgen [mailto:kaempgen@fzi.de] 
Sent: Thursday, January 17, 2013 11:24 AM
To: Gillman, Daniel - BLS; Government Linked Data Working Group
Subject: AW: ISSUE-39 (QB-skos:Collection): Data Cube: Allow skos:Collections as value of qb:codeList [Data Cube Vocabulary]

Thanks, Dan.

This helps to understand the motivation. But does it argue for having skos:Collection as a qb:codeList? One could still have all these (higher) values in a skos:ConceptScheme.

Best, 

Benedikt

________________________________________
Von: Gillman, Daniel - BLS [Gillman.Daniel@bls.gov]
Gesendet: Samstag, 12. Januar 2013 00:59
An: Benedikt Kaempgen; Government Linked Data Working Group
Betreff: RE: ISSUE-39 (QB-skos:Collection): Data Cube: Allow  skos:Collections as value of qb:codeList [Data Cube Vocabulary]

Benedikt,

If, for instance, data representing some of the values in a dimension are too small in some sense (say counts of people having some characteristic), a designer will aggregate those small values into one in the level above.  The idea is to raise the counts to avoid possible problems with disclosing proprietary information.  Therefore, one cannot know for certain if the values in some dimension all come from the same level.

Yours,
Dan

-----Original Message-----
From: Benedikt Kaempgen [mailto:kaempgen@fzi.de]
Sent: Friday, January 11, 2013 7:46 AM
To: Government Linked Data Working Group
Subject: AW: ISSUE-39 (QB-skos:Collection): Data Cube: Allow skos:Collections as value of qb:codeList [Data Cube Vocabulary]

Hello,

Is there a concrete use case of this issue?

XKOS defines levels as subClassOf skos:Collection [1]. On first sight it would make sense to restrict the values of a dimension to all members of a certain level.

I have added a requirement at [2].

Best,

Benedikt

[1] <https://github.com/linked-statistics/xkos/blob/master/xkos.ttl>
[2] <http://www.w3.org/2011/gld/wiki/Data_Cube_Vocabulary/Use_Cases#Data_Cube:_Allow_skos:Collections_as_value_of_qb:codeList>

________________________________________
Von: Government Linked Data Working Group Issue Tracker [sysbot+tracker@w3.org]
Gesendet: Sonntag, 21. Oktober 2012 15:50
An: public-gld-wg@w3.org
Betreff: ISSUE-39 (QB-skos:Collection): Data Cube: Allow skos:Collections as value of qb:codeList [Data Cube Vocabulary]

ISSUE-39 (QB-skos:Collection): Data Cube: Allow skos:Collections as value of qb:codeList [Data Cube Vocabulary]

http://www.w3.org/2011/gld/track/issues/39

Raised by: Richard Cyganiak
On product: Data Cube Vocabulary

Some complex industrial classifications use skos:Collection for additional structure; for example, in a multi-level classification, all concepts at a certain level could be grouped into a skos:Collection. Wanting to specify that the values of a QB dimension are all from such a collections seems reasonable and should be supported.

Received on Thursday, 17 January 2013 16:32:09 UTC