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

Re: AW: [QB] ISSUE-32 relation to O&M

From: Dave Reynolds <dave.e.reynolds@gmail.com>
Date: Sat, 02 Mar 2013 21:20:30 +0000
Message-ID: <51326D1E.4030901@gmail.com>
To: Richard Cyganiak <richard@cyganiak.de>
CC: Benedikt Kaempgen <kaempgen@fzi.de>, Government Linked Data Working Group <public-gld-wg@w3.org>
On 02/03/13 18:30, Richard Cyganiak wrote:
> On 1 Mar 2013, at 12:04, Dave Reynolds wrote:
>> On 01/03/13 10:13, Benedikt Kaempgen wrote:
>>>> Proposed approach: Address this via a working group Note.
>>
>> Interesting thought.
>>
>> The advantage of a separate note is that I'm more likely to be able to get people from the TC/211 community to review it if it is self-contained.  But maybe it is too short to justify a full Note.
>
> I'm also concerned that this might be too short for a separate document.
>
> Putting this into the UC&R seems like a good solution to me, if there's not enough time for putting it into the main spec. To make it easy for TC/211 to review the section (which I agree is a good idea), a separate temporary document could be created outside of W3C space, for the sole purpose of presenting it to TC/211.

Accepted. I will postpone work on the O&M note until we have finished to 
current burst of work on the QB spec itself, will draft something for 
inclusion in UC&R, will initially do that as a wiki page or some such to 
enable review.

Dave

>>> On a site note regarding a review of a refined specification: I am not in the office from 2nd until 6th of March.
>>
>> OK, will aim to have a sufficiently stable version by 6th March for you to review.
>>
>> Thanks,
>> Dave
>>
>>> Best,
>>>
>>> Benedikt
>>>
>>> [1] <https://dvcs.w3.org/hg/gld/raw-file/default/data-cube-ucr/data-cube-ucr-20130227/index.html#VocabularyshoulddefinerelationshiptoISO19156ObservationsMeasurements>
>>>
>>> ________________________________________
>>> Von: Dave Reynolds [dave.e.reynolds@gmail.com]
>>> Gesendet: Donnerstag, 28. Februar 2013 18:55
>>> An: Government Linked Data Working Group
>>> Betreff: [QB] ISSUE-32 relation to O&M
>>>
>>> ISSUE-32 [1] concerns the relationship between Data Cube and ISO 19156
>>> Observations and Measurements.
>>>
>>> Proposed approach: Address this via a working group Note.
>>>
>>> [I had previously proposed a non-normative appendix to the spec, but on
>>> reflection making this a WG Note allows it to proceed to a separate
>>> timescale and is then not slowing down LC.]
>>>
>>> The note would roughly say ...
>>>
>>> o Data Cube can also be used for things like sensor measurements and
>>> forecasting, it is not limited to statistics.
>>>
>>> o A well known standard for measurement information is OGC Observations
>>> and Measuresments (O&M), ISO19156.
>>>
>>> o How does Data Cube relate to O&M?
>>>
>>> o Since Data Cube has a concept qb:Observation it might be tempting to
>>> think of this as being an Observation in the sense of O&M. In some cases
>>> that may be appropriate but not always.
>>>
>>> o O&M provides a representation for a how to describe the measurement
>>> process, the phenomenon being measured and the domain ("feature of
>>> interest") over which the observation takes place together with the
>>> result of the measurement. The result may be a simple value but can be,
>>> and often is, a set of values (Discrete Coverage) for example over time
>>> or over space or both.
>>>
>>> o Thus one approach to using both specifications together is to use Data
>>> Cube as a representation for O&M Discrete Coverage. O&M provides the
>>> contextual metadata describing the measurement process and measured
>>> phenomena. Data Cube provides the representation for the values which
>>> result from the observation, allowing us to give e.g. the time, location
>>> of each sample within the result. The two complement each other.
>>>
>>> Dave
>>>
>>>
>>> [1] http://www.w3.org/2011/gld/track/issues/32
>>>
>>>
>>
>>
>
Received on Saturday, 2 March 2013 21:21:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:38 UTC