W3C home > Mailing lists > Public > public-sdwig@w3.org > December 2019

Re: [sdw] ssn:ext proposal comment: note on section 5.1 (#1154)

From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Dec 2019 21:49:54 +0000
To: public-sdwig@w3.org
Message-ID: <issue_comment.created-564274704-1576014592-sysbot+gh@w3.org>
Observed property is probably a dimension too - anything you would slice and dice, or characterise, an observation collection with is a dimension.

time could be a measure - if what you are doing is observing when something happened, as opposed to what is happening at a time ? This is certainly true for spatial aspects - observed loci of moving features have different dimensions to measurements of the state of a static feature. QB give you the opportunity to make this clear - thats its big advantage #1 IMHO (#2 is the ability to bind a property to a codelist - nothing else in the W3C canon seems to support this!)

I would re-write it as more like

For a collection of observations the datacube (qb:) model may be used to express aspects  of sampling - such as whether a set of samples are all  related to the same ultimateFeatureOfInterest, or the same type of FOI etc.  Feature of interest, phenomenon time, sampling procedure will typically be qb:dimension sub-properties, measures will be the observed properties and qb:ComponentDescriptions for measures may indicate result types. qb:attribute sub-properties may be used for qualifying and annotating information.  

In future a general model for the inter-relation of dimensions, sensors, observed properties, phenomena, units of measure, sampling precision, procedures, etc.  could use qb:dimension concepts to describe sampling strategies.  

-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/sdw/issues/1154#issuecomment-564274704 using your GitHub account
Received on Tuesday, 10 December 2019 21:49:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:17:55 UTC