RE: Time Ontology outstanding issues: Notes to be removed or incorporated

Thanks, Simon

Linking requirements to ‘solution’ is a good suggestion. I will figure out how to do it.

Re Notes, Phil Archer said Notes are perfectly acceptable content for W3C documents, so I think it appropriate that the 5.6 Note could stay as such.

Chris

From: Simon.Cox@csiro.au [mailto:Simon.Cox@csiro.au]
Sent: Thursday, December 15, 2016 1:17 AM
To: Little, Chris; public-sdw-wg@w3.org
Cc: sdwwg@lists.opengeospatial.org
Subject: RE: Time Ontology outstanding issues: Notes to be removed or incorporated

A couple of quick comments on process/record keeping:


>  Propose to delete as the Ontology is intended to be used separately from the Requirements document

Yes. But this information should be relocated into whatever becomes the response to the requirements document – i.e. there is a link from requirements to solution which needs to be recorded, though it should not be embedded in the solution.


>  Propose to leave as a useful Note unless there is a W3C policy against this, or incorporate into main body of text

That depends on what the rule or convention for use of ‘Note’ is within W3C recs.

Simon

From: Little, Chris [mailto:chris.little@metoffice.gov.uk]
Sent: Thursday, 15 December, 2016 02:56
To: SDW WG Public List <public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>>
Cc: sdwwg@lists.opengeospatial.org<mailto:sdwwg@lists.opengeospatial.org>; Cox, Simon (L&W, Clayton) <Simon.Cox@csiro.au<mailto:Simon.Cox@csiro.au>>
Subject: RE: Time Ontology outstanding issues: Notes to be removed or incorporated

Dear Time Ontologists,

Many of the following Notes have already been incorporated into the body of the Editor’s Draft text of the Time Ontology, so I propose to remove them next week, unless anyone can think of a reason to keep them.

Chris
-------------
2. Changes from previous versions
Note The SDWWG requirement 5.49 Temporal vagueness relates to this.
Propose to incorporate into text of Issue 3.

4.3 Time position and time units
Note DateTimeDescription covers the case that was defined in the original note, and retains the original class name.
Propose to delete as the Ontology is intended to replace the previous version

Note These classes address the 'date' and 'time' requirement from 5.7 Date, time and duration
Propose to delete as the Ontology is intended to be used separately from the Requirements document

4.4 Duration
Note DurationDescription covers the case that was in the original note, and retains the original class name.
Propose to delete as the Ontology is intended to replace the previous version

Note These classes address the 'duration' requirement from 5.7 Date, time and duration
Propose to delete as the Ontology is intended to be used separately from the Requirements document

5. Vocabulary specification
Note The SDWWG requirement 5.25 Multilingual support relates to the documentation of the ontology.
Propose to delete as covered by W3C documentation policy

5.6 Class: TRS [Temporal Reference System]
Note A taxonomy of temporal reference systems is provided in ISO 19108:2002 [ISO-19108], including (a) calendar + clock systems; (b) temporal coordinate systems; (c) temporal ordinal reference systems.
Propose to leave as a useful Note unless there is a W3C policy against this, or incorporate into main body of text

Note This TRS support addresses the following requirements from the SDWWG: 5.9 Different time models, 5.48 Temporal reference system, 5.28 Nominal temporal references.
Propose to delete as the Ontology is intended to be used separately from the Requirements document

5.9 Class: DayOfWeek
Note In this version of the ontology, membership of the class DayofWeek is open, to allow for alternative week lengths and different day names.
Propose to incorporate into main body of text

5.11 Class: TemporalUnit
Note In this version of the ontology, membership of the class TemporalUnit is open, to allow for additional temporal units used in some technical applications (e.g. millions of years, Baha'i month).
Propose to incorporate into main body of text

5.16 Datatype: generalYear
Note While this pattern achieves the correct lexical form, the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
Propose to delete. Already incorporated into main body of text

5.17 Datatype: generalMonth
Note While this pattern achieves the correct lexical form, the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
Propose to delete. Already incorporated into main body of text

5.18 Datatype: generalDay
Note While this pattern achieves the correct lexical form, the value-space is not defined, so a generic OWL2 processor cannot compute ordering relationships of values of this type.
Propose to delete. Already incorporated into main body of text

6. Examples
6.1 iCalendar
Note This example replaces the one from [OWL-T].
Propose to delete as the Ontology is intended to replace the previous version

6.3 DateTimeDescription vs. dateTime
Note This example carried over from [OWL-T].
Propose to delete as the Ontology is intended to replace the previous version

6.6 A Use Case for Scheduling
Note This example carried over from [OWL-T].
Propose to delete as the Ontology is intended to replace the previous version

6.7 Web commerce applications
Note This example carried over from [OWL-T].
Propose to delete as the Ontology is intended to replace the previous version

B. Time Zone Vocabulary
Note This section unaltered from [OWL-T].
Propose to delete as the Ontology is intended to replace the previous version
----------------
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<mailto:chris.little@metoffice.gov.uk>  http://www.metoffice.gov.uk


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