W3C home > Mailing lists > Public > public-sdw-wg@w3.org > February 2017

RE: OWL-Time ISSUE-127 TimeZone model

From: <Simon.Cox@csiro.au>
Date: Sun, 26 Feb 2017 05:51:10 +0000
To: <Simon.Cox@csiro.au>, <chris.little@metoffice.gov.uk>, <public-sdw-wg@w3.org>
Message-ID: <0d1ec89609d7470090c1616c8cbb8504@exch1-mel.nexus.csiro.au>
ISSUE-127 closed.

From: Simon.Cox@csiro.au [mailto:Simon.Cox@csiro.au]
Sent: Monday, 20 February, 2017 13:46
To: chris.little@metoffice.gov.uk; public-sdw-wg@w3.org
Subject: [ExternalEmail] RE: OWL-Time ISSUE-127 TimeZone model

Having implemented all the suggestions in this thread, I propose to close ISSUE-127 if I hear no objections by the end of the week.

From: Little, Chris [mailto:chris.little@metoffice.gov.uk]
Sent: Friday, 23 December, 2016 01:05
To: Cox, Simon (L&W, Clayton) <Simon.Cox@csiro.au<mailto:Simon.Cox@csiro.au>>; public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>
Subject: RE: OWL-Time ISSUE-127 TimeZone model

And maybe mention the IANA and IETF sites as examples of ‘not very webby’ at all?

From: Little, Chris
Sent: Thursday, December 22, 2016 12:49 PM
To: 'Simon.Cox@csiro.au'; 'public-sdw-wg@w3.org'
Subject: RE: OWL-Time ISSUE-127 TimeZone model

Simon,


1.       If we keep the Time Zone examples, we need to change all ‘GMT’ and ‘Greenwich Mean Time’ to ‘UTC’ and ‘Universal Coordinated Time’.


2.       I also suggest we place a marker for the useful and semmingly persistent resources at IETF https://www.ietf.org/timezones/data/ and also IANA http://www.iana.org/time-zones ? what do you think?


Chris


From: Little, Chris
Sent: Wednesday, December 21, 2016 2:56 PM
To: 'Simon.Cox@csiro.au'; public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>; 'Phil Archer'
Subject: RE: OWL-Time ISSUE-127 TimeZone model

Simon, Phila,

Do we need to ask the worldclock people whether we can quote them? I know it is polite anyway.

Is there a W3C policy about it?

I notice that their API does not specify UoM and they use both decimal hours and seconds for the same purpose, though I understand why.

Are you suggesting that we edit Appendix B with the informative examples, or abolish it and put the examples in the body of the document?

Chris

From: Simon.Cox@csiro.au<mailto:Simon.Cox@csiro.au> [mailto:Simon.Cox@csiro.au]
Sent: Wednesday, December 21, 2016 4:20 AM
To: public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>
Subject: OWL-Time ISSUE-127 TimeZone model

I’ve created a specific issue for discussion of the time-zone model issue raised by Chris as (local) Issue-12.

I am inclined to go along with Chris’s proposal to remove Appendix B which described the TimeZone ontology, since it is limited in scope and incomplete. However, some of the examples need links to timezone definitions, so we need to point them somewhere. Options:


(a)   Fix the timezone ontology – lots of work, no expertise

(b)   Keep it, but mark it ‘informative’ – but we already know it is slightly broken

(c)    Find an alternative.

An excellent, well maintained, source of timezone definitions is the list here: https://www.timeanddate.com/time/zones/


Individual timezones appear to have stable URIs, like https://www.timeanddate.com/time/zones/aedt

Furthermore,

1.      these guys have been maintaining this resource pretty well for quite a few years now,

2.      the site URL at least has been stable over at least one change in ownership (it changed from a hobby to a commercial site)

3.      after all, it’s just a collation from sources of varying jurisdictional status and solidity[*] as there is no global governance arrangement
I doubt we could find a better source. There are IATA codes – see https://en.wikipedia.org/wiki/International_Air_Transport_Association_code#IATA_timezone_codes but (a) these are not the same as the customary codes (EST, AEST etc) and (b) I can’t find any corresponding linked resources.
So, for the time being, I propose to use the timeanddate URIs in the examples.

Note that TimeAndDate also provides an API to get descriptions like

      <timezone offset="+11:00">
        <zoneabb>AEDT</zoneabb>
        <zonename>Australian Eastern Daylight Time</zonename>
        <zoneoffset>36000</zoneoffset>
        <zonedst>3600</zonedst>
        <zonetotaloffset>39600</zonetotaloffset>
      </timezone>

which appears to show that their data model is less sophisticated than their HTML pages (which are very nice)!

[*] some customary timezones actually have zero legal status – e.g. https://www.timeanddate.com/time/zones/acwst


Simon J D Cox
Research Scientist
Environmental Informatics
CSIRO Land and Water<http://www.csiro.au/Research/LWF>

E simon.cox@csiro.au<mailto:simon.cox@csiro.au> T +61 3 9545 2365 M +61 403 302 672
   Mail: Private Bag 10, Clayton South, Vic 3169
   Visit: Central Reception, Research Way, Clayton, Vic 3168
   Deliver: Gate 3, Normanby Road, Clayton, Vic 3168
people.csiro.au/Simon-Cox<http://people.csiro.au/Simon-Cox>
orcid.org/0000-0002-3884-3420<http://orcid.org/0000-0002-3884-3420>
researchgate.net/profile/Simon_Cox3<https://www.researchgate.net/profile/Simon_Cox3>
github.com/dr-shorthair<https://github.com/dr-shorthair>

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.


Received on Sunday, 26 February 2017 05:51:55 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:30 UTC