Re: Progress on Time deliverable

Hi Simon,

Not sure if this is a "between the cracks" issue, or if you have considered
this and have some advice...

I am trying to determine an appropriate practice for using the time
ontology in the context of a RDF Datacube dimension specialisation, as per
https://www.w3.org/TR/vocab-data-cube/#dsd-dimensions.

This is a requirement implicit in the SDW charter
"The WG will develop a formal Recommendation for expressing discrete
coverage data conformant to the ISO 19123
<http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=40121>
 abstract model. Existing standard and *de facto* ontologies will be
examined for applicability; these will include the RDF Data Cube
<https://www.w3.org/TR/vocab-data-cube/>. "

Noting however that AFAICT there has yet to be a treatment of using
RDF-Datacube to express the metadata need to use WCS or similar API -
instead the discussion has so far related to prior experiences trying to
serialise the data into RDF.  Defining dimensions using a formalism such as
RDF-datacube does not imply any particular encoding of the data, or even
the encoding of the metadata.

The SDW-BP makes multiple mentions of examples of using time and spatial
objects in RDF datacube dimensions, without addressing the implication that
where applicable concepts should be exposed as skos:Concepts, From my
reading of these various pieces there seems to be a missing piece which
relates to the application of the Time ontology to the definition of
instances exposed as skos:Concepts, or appropriate measures that allow for
typical hierarchical  year/month/day etc applications.

Where in the SDW does the Use Case of defining a temporal dimension get
addressed?

cheers
Rob Atkinson


On Mon, 16 May 2016 at 08:28 <Simon.Cox@csiro.au> wrote:

> Dear WG –
>
>
>
> Apologies for the silence relating to progress on the OWL-Time
> deliverable.
>
>
>
> I can now report that a complete working draft is available in the Github
> repository, or in formatted view here: http://w3c.github.io/sdw/time/
>
>
>
> So far all that has been done is to take the 2006 Working Draft by Hobbs
> and Pan, re-arrange it to be a bit more systematic, and make modifications
> relating to TRS support that were described in my paper and briefed to the
> group I think three times now. The RDF version of the ontology has not yet
> been loaded into a W3C location, but the CSIRO-hosted version from the
> paper is available here: http://def.seegrid.csiro.au/ontology/time/new
> I’m not sure what the protocol is for loading an update over the existing
> version, but I guess it would be premature until we are a lot further along
> in the process.
>
>
>
> I have retained some of the language from the 2006 version, but it is
> distributed in various places in the new document.
>
> I also retained most of the examples – these have not been re-written at
> all, yet. I have added some new examples, some from my paper, and a new
> example using the ProperInterval class for the geologic time scale, to
> illustrate both the temporal topology handling, and also the TRS support.
>
>
>
> I’ve worked essentially by myself to get to this point - Chris has no
> responsibility for any errors. But thought it was worth advising the WG of
> this progress as it is now respectable enough to look at. Chris and I (and
> anyone else who is interested!) will now go back to the UCR document and
> consider what additional work is required.
>
>
>
> Simon
>
>
>
> *Simon J D Cox *
>
> Research Scientist
>
> Environmental Informatics
>
> Land and Water <http://www.csiro.au/en/Research/LWF>
>
> CSIRO
>
>
>
> *E* simon.cox@csiro.au *T* +61 3 9545 2365 *M* +61 403 302 672
>
> *   Physical: *Reception Central, Bayview Avenue, Clayton, Vic 3168
>
> *   Deliveries: *Gate 3, Normanby Road, Clayton, Vic 3168
>
>    *Postal:* Private Bag 10, Clayton South, Vic 3169
>
> people.csiro.au/Simon-Cox
>
> orcid.org/0000-0002-3884-3420
>
> researchgate.net/profile/Simon_Cox3
> <https://www.researchgate.net/profile/Simon_Cox3>
>
>
>
> *PLEASE NOTE*
>
> The information contained in this email may be confidential or privileged.
> Any unauthorised use or disclosure is prohibited. If you have received this
> email in error, please delete it immediately and notify the sender by
> return email. Thank you. To the extent permitted by law, CSIRO does not
> represent, warrant and/or guarantee that the integrity of this
> communication has been maintained or that the communication is free of
> errors, virus, interception or interference.
>
>
>
> *Please consider the environment before printing this email.*
>
>
>