W3C home > Mailing lists > Public > public-gld-wg@w3.org > March 2012

RE: Observations and Measurement - draft

From: Benedikt Kämpgen <kaempgen@fzi.de>
Date: Wed, 21 Mar 2012 18:54:50 +0100
To: <public-gld-wg@w3.org>
Message-ID: <00e101cd078b$b68d1400$23a73c00$@fzi.de>
Dear Luis,

Thanks for your feedback regarding "Modeling quantity, measurement,
observation" in the data cube use case document [1].

I understand that the modeling I cite there is not as elaborate as the
Observations and Measurements (OM) model. Still, I thought it to be
sufficiently general for explaining the overall problem of modeling
statistics. 

Is your feedback not more related to UC 4 [2] (Publishing sensor data as
statistics)? There we already mention OM. If we had a use case where OM has
been applied, we could describe it in UC 4 to derive issues and requirements
for QB.

Best,

Benedikt

[1]
<http://dvcs.w3.org/hg/gld/raw-file/default/data-cube-ucr/index.html#publish
ing-general-statistics-in-a-machine-readable-and---application-independent-w
ay--uc-1>   
[2]
<http://dvcs.w3.org/hg/gld/raw-file/default/data-cube-ucr/index.html#publish
ing-sensor-data-as-statistics--uc-4> 


> -----Original Message-----
> From: Luis Bermudez [mailto:lbermudez@opengeospatial.org]
> Sent: Thursday, March 01, 2012 5:10 PM
> To: Benedikt Kämpgen
> Cc: public-gld-wg@w3.org
> Subject: Observations and Measurement - draft
> 
> All,
> 
> Comments about Observations and Measurement related to:
> 
> - Section: Publishing Statistical Data
> - http://www.w3.org/2011/gld/track/issues/32
> - @@TODO: Are there any statements about compatibility and
> interoperability between O&M and Data Cube that can be made to give
> guidance to such organizations?
> 
> Suggest to use Observations and Measurements (OM) model.
> 
> An Observation is an event whose result is an estimate of the value of
some
> property of a feature of interest, obtained using a specified procedure.
> 
> An Observation has essentially the following parts:
> 
> Procedure: e.g. person, sensor, observatory, model, macro.
> Property: e.g. temperature, color, weight.
> Feature of Interest: e.g. body, world, Washington DC, banana, specimen
123,
> Monterey Bay.
> Result: The actual value. Includes categories and quantities results, time
> series, multimedia (video, audio), one single value, a file, etc.
> 
> So in the figure: "Modeling quantity, measurement, observation" we can do
> the following:
> 
> Add Procedure, Result, Feature of Interest and Property
> Model Person as a type of Procedure
> Remove Measurement
> Category and Quantity are subclass of result.
> Phenomenon Type is same as Property
> 
> 
> Luis
> -------------
> Luis Bermudez
> lbermudez@opengeospatial.org
> +1 (301) 760-7323
> 
> The OGC: Making Location Count...
> http://www.opengeospatial.org/contact
> 
> 
> 
> 
> On Feb 22, 2012, at 11:38 AM, Benedikt Kämpgen wrote:
> 
> > Hello,
> >
> > We have further refined the Data Cube use cases and copied the content
> from
> > the wiki into an Editor's Draft for "Use Cases and Requirements for the
Data
> > Cube Vocabulary" [1].
> >
> > Feedback of any kind would be well appreciated.
> >
> > Best,
> >
> > Benedikt
> >
> > [1] <http://dvcs.w3.org/hg/gld/raw-file/default/data-cube-
> ucr/index.html>
> >
> >
> >
> > --
> > AIFB, Karlsruhe Institute of Technology (KIT)
> > Phone: +49 721 608-47946
> > Email: benedikt.kaempgen@kit.edu
> > Web: http://www.aifb.kit.edu/web/Hauptseite/en
> >
> >
> >
> >
> >
Received on Wednesday, 21 March 2012 17:55:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 9 December 2014 23:03:31 UTC