search

AKSW / cubevizjs

CubeViz.js is the successor of the CubeViz and provides statistical data exploration and visualization. Its completely written in JavaScript.
Other
16 stars 4 forks source link

Attribute handling #8

Closed k00ni closed 7 years ago

k00ni commented 8 years ago

(is related to #4)

We are currently struggling with the many ways to define an attribute. There are multiple cases how to express attribute information:

Case 1 (is supported)

attribute is defined in DSD and is used in an observation explicitly 

DSD qb:attribute ex:Attribute .
attr1 a ex:Attribute
obs1 ex:Attribute attr1

Reference to specification: https://www.w3.org/TR/vocab-data-cube/#dsd-dsd

Case 2

Attribute is defined using a measurement (implicit):

DSD qb:measure ex:Measure .
ex:Measure ??? ex:Attribute . (<=== unclear, research!)
attr1 a ex:Attribute ;
        rdfs:label "kilometer".
obs1 ex:Measure "400"

In this obs1 means that it outlines 400 kilometers.

Reference to specification: https://www.w3.org/TR/vocab-data-cube/#dsd-mm

Attributes can also be attached directly to the qb:MeasureProperty itself (e.g. to indicate the unit of measure for that measure) but that attachment applies to the whole data set (indeed any data set using that measure property) and cannot vary for different observations.

k00ni commented 7 years ago

@GeorgesAlkhouri : please re-check if case 2 solved.

GeorgesAlkhouri commented 7 years ago

Nope, unfortunately case 2 is not solved.

DSD qb:measure ex:Measure . ex:Measure ??? ex:Attribute . (<=== unclear, research!) attr1 a ex:Attribute ; rdfs:label "kilometer". obs1 ex:Measure "400"

The relation of ex:Measure and ex:Attribute should by qb:attribute, right?

k00ni commented 7 years ago

The relation of ex:Measure and ex:Attribute should by qb:attribute, right?

Yes, you are right.