- From: Bruce Bannerman <B.Bannerman@bom.gov.au>
- Date: Mon, 18 May 2015 22:58:22 +0000
- To: "Kerry.Taylor@csiro.au" <Kerry.Taylor@csiro.au>, "jlieberman@tumblingwalls.com" <jlieberman@tumblingwalls.com>
- CC: "public-sdw-wg@w3.org" <public-sdw-wg@w3.org>
- Message-ID: <D180A871.1E85A%B.Bannerman@bom.gov.au>
Hi Kerry, Provenance is particularly important for climate data related issues, and no doubt for many more domains as well. >From a climate perspective, when I publish a scientific paper, I need to be able to reference all the data that underpins the analysis that the paper was based on. So this may be: * Published paper * Claims in Published paper based on Analytical Data (perhaps a multi dimensional array/grid/coverage) * Analytical data is derived from quality assured observations data (with details as to why each change to the QA obs were made) * Quality assured observations data is derived from 'raw' observations data which has details as to the conditions, sensors etc that the observation was made under. There are many nuances to provenance here. Including an understanding of what algorithms were used to process the data and ideally a reference to the source code of these algorithms as they were at the time of the analysis. And to make things more interesting, the analysis and data is typically time-series (observations and coverages). This reminds me I posted on a potential climate use case several months ago, but forgot to add it. If there is still interest in this, let me know and I'll put something together. Bruce From: "Kerry.Taylor@csiro.au<mailto:Kerry.Taylor@csiro.au>" <Kerry.Taylor@csiro.au<mailto:Kerry.Taylor@csiro.au>> Date: Wednesday, 13 May 2015 23:59 To: "jlieberman@tumblingwalls.com<mailto:jlieberman@tumblingwalls.com>" <jlieberman@tumblingwalls.com<mailto:jlieberman@tumblingwalls.com>> Cc: "public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>" <public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>> Subject: RE: UCR isssue: Is provenance in scope? Resent-From: <public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>> Resent-Date: Thursday, 14 May 2015 00:00 (Resending -missed the list cc) From: Taylor, Kerry (Digital, Acton) Sent: Wednesday, 13 May 2015 10:53 PM To: 'Joshua Lieberman' Subject: RE: UCR isssue: Is provenance in scope? +1 I think we need only to make sure (and perhaps show how) our deliverables can deal with provenance by attaching/linking some W3C Prov-o. I would not suggest we need to show to encode spatial data provenance in PROv-o though. Provenance is a first class issue in a great deal of spatial data applications. Kerry From: Joshua Lieberman [mailto:jlieberman@tumblingwalls.com] Sent: Wednesday, 13 May 2015 10:38 PM To: Frans Knibbe Cc: SDW WG Public List Subject: Re: UCR isssue: Is provenance in scope? Perhaps we can discuss the general issue of scope today on the call. There are many aspects of spatiotemporal data that in general are similar to issues with other data, but that clearly require specialization for our case. For example, provenance of spatial data must address not only how a feature and a spatial reference such as a geometry were formed, but how they were associated and under what assumptions for representation of the physical world. This is quite specialized to spatial and a significant semantic interoperability issue. We will miss addressing critical points in our work if we subsume them too often into general ones and deem them out of scope. Josh Joshua Lieberman, Ph.D. Principal Tumbling Walls jlieberman*tumblingwalls.com<http://tumblingwalls.com> +1 617 431 6431 On May 13, 2015, at 8:21 AM, Frans Knibbe <frans.knibbe@geodan.nl<mailto:frans.knibbe@geodan.nl>> wrote: Hello all, I have raised an issue for the UCR document: ISSUE-11<http://www.w3.org/2015/spatial/track/issues/11>. Again, all help in getting this issue resolved is very welcome. Regards, Frans -- Frans Knibbe Geodan President Kennedylaan 1 1079 MB Amsterdam (NL) T +31 (0)20 - 5711 347 E frans.knibbe@geodan.nl<mailto:frans.knibbe@geodan.nl> www.geodan.nl<http://www.geodan.nl/> disclaimer<http://www.geodan.nl/disclaimer>
Received on Monday, 18 May 2015 22:58:57 UTC