Requirement for 'Valid Time'

Dear colleagues,
 
Unfortunately, tomorrow I will be travelling by train, with rubbish phone connections, so it will be highly unlikely that I can join in, so I will add my views on UCR-16 here:

1. I agree that 'Valid Time' is outside the scope of the Time OWL ontology, as are lots of other time semantics (verification time, time of last update, creation time, publication time, etc).

2. There are widely used ontologies that recognise different kinds of time e.g. Dublin Core.

3. It seems to be out of scope for spatial data as opposed to just 'data on the Web'. However, there are lots of examples in the spatial domain, such as environmental observational data and weather forecasts. Increasingly, to know a location, one needs to know when.

4. The Met Ocean Domain WG of OGC produced a Best Practice profile of the OGC WMS1.3 standard to capture some of these time concepts and improve interoperability arising from real world experience of interoperability problems. The BP gave a standard name for these non-standard time semantics ("Reference Time").

5. I do not know if there is a generic 'framework' for capturing different time application level semantics in Data on the Web.

6. I think this is important for enough SDWWG Use Cases that it should not be ruled out of scope unless some other 'owner' is identified to take it forward.

HTH, Chris


Chris Little
Co-Chair, OGC Meteorology & Oceanography Domain Working Group

IT Fellow - Operational Infrastructures
Met Office  FitzRoy Road  Exeter  Devon  EX1 3PB  United Kingdom
Tel: +44(0)1392 886278  Fax: +44(0)1392 885681  Mobile: +44(0)7753 880514
E-mail: chris.little@metoffice.gov.uk  http://www.metoffice.gov.uk


I am normally at work Tuesday, Wednesday and Thursday each week

Received on Tuesday, 10 November 2015 16:48:07 UTC