ISSUE-15: Time req. not clear - represent past, present and future

allaves

Time req. not clear - represent past, present and future

State:
CLOSED
Product:
Time ontology in OWL
Raised by:
Alejandro Llaves
Opened on:
2015-05-26
Description:
I don't fully understand this requirement and it has not been included in the UCR document yet: "represent past, present and future", tab Time, column K.

If the requirement refers to represent past, present and future as a time concept, a time reference is needed, e.g. the Spanish Civil war happened in the PAST wrt the current date, May 26th, 2015. Otherwise, if the requirement refers to represent temporal relations between, e.g. events, it may be covered by this other requirement addressing temporal reasoning: https://www.w3.org/2015/spatial/track/issues/14 (still under discussion).

Link to the spreadsheet: https://docs.google.com/spreadsheets/d/1PSnpJYQDgsdgZgPJEfUU0EhVfgFFYGc1WL4xUX9Dunk/edit?usp=sharing
Related Actions Items:
Related emails:
  1. ISSUE-15 RE: Time Ontology outstanding Issue 4 (from Simon.Cox@csiro.au on 2016-12-18)
  2. Time Ontology outstanding Issue 4 (from chris.little@metoffice.gov.uk on 2016-12-16)
  3. Time Ontology outstanding issues (from chris.little@metoffice.gov.uk on 2016-12-14)
  4. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-11)
  5. RE: Wanted: feedback on UCR requirements (from Simon.Cox@csiro.au on 2016-07-08)
  6. RE: Wanted: feedback on UCR requirements (from chris.little@metoffice.gov.uk on 2016-07-07)
  7. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-07)
  8. RE: Wanted: feedback on UCR requirements (from chris.little@metoffice.gov.uk on 2016-07-07)
  9. Re: [Minutes] 2016-02-03 (from frans.knibbe@geodan.nl on 2016-03-21)
  10. RE: [Minutes] 2016-02-03 (from Simon.Cox@csiro.au on 2016-03-20)
  11. Re: [Minutes] 2016-02-03 (from jlieberman@tumblingwalls.com on 2016-03-18)
  12. Re: [Minutes] 2016-02-03 (from frans.knibbe@geodan.nl on 2016-03-18)
  13. RE: [Minutes] 2016-02-03 (from L.Svensson@dnb.de on 2016-03-02)
  14. RE: [Minutes] 2016-02-03 (from chris.little@metoffice.gov.uk on 2016-03-02)
  15. Re: [Minutes] 2016-02-03 (from frans.knibbe@geodan.nl on 2016-02-18)
  16. RE: [Minutes] 2016-02-03 (from chris.little@metoffice.gov.uk on 2016-02-04)
  17. [Minutes] 2015-11-11 (from phila@w3.org on 2015-11-11)
  18. Re: ISSUE-15: Past, present and future (from frans.knibbe@geodan.nl on 2015-10-14)
  19. RE: ISSUE-15: Past, present and future (from Simon.Cox@csiro.au on 2015-10-07)
  20. Re: ISSUE-15: Past, present and future (from frans.knibbe@geodan.nl on 2015-10-07)
  21. RE: ISSUE-15: Past, present and future (from Simon.Cox@csiro.au on 2015-10-06)
  22. Re: ISSUE-15: Past, present and future (from frans.knibbe@geodan.nl on 2015-10-05)
  23. [Minutes] 2015-09-02 (from phila@w3.org on 2015-09-02)
  24. Re: SDWWG Next meeting - Welcome back everyone ! (from antoine.zimmermann@emse.fr on 2015-09-01)
  25. SDWWG Next meeting - Welcome back everyone ! (from eparsons@google.com on 2015-09-01)
  26. RE: ISSUE-15: Past, present and future (from chris.little@metoffice.gov.uk on 2015-08-26)
  27. Re: ISSUE-15: Past, present and future (from frans.knibbe@geodan.nl on 2015-08-17)
  28. RE: ISSUE-15: Past, present and future (from chris.little@metoffice.gov.uk on 2015-08-12)
  29. Re: ISSUE-15: Past, present and future (from frans.knibbe@geodan.nl on 2015-08-07)
  30. RE: ISSUE-15: Past, present and future (from chris.little@metoffice.gov.uk on 2015-08-05)
  31. Re: ISSUE-15: Past, present and future (from frans.knibbe@geodan.nl on 2015-08-05)
  32. RE: ISSUE-15: Past, present and future (from chris.little@metoffice.gov.uk on 2015-08-05)
  33. ISSUE-15: Past, present and future (from frans.knibbe@geodan.nl on 2015-08-04)
  34. Re: Editorial amendments to UCR (from allaves@fi.upm.es on 2015-06-03)
  35. How to refer to issues on the tracker from the Use Case doc (from jeremy.tandy@gmail.com on 2015-06-02)
  36. Re: Editorial amendments to UCR (from phila@w3.org on 2015-06-02)
  37. Re: Editorial amendments to UCR (from jeremy.tandy@gmail.com on 2015-06-02)
  38. [Minutes] 2015-05-27 (from phila@w3.org on 2015-06-01)

Related notes:

Proposed phrasing for a new requirement:

"It should be possible to declare that a web resource is in the past, present or future with respect to another web resource"

Frans Knibbe, 2 Sep 2015, 12:54:43

We have established that the current version of OWL Time already meets the proposed requirement ("It should be possible to declare that a web resource is in the past, present or future with respect to another web resource"). Therefore it is questionable whether this requirement should be added.

Frans Knibbe, 26 Oct 2015, 10:07:18

[frans]: time

11 Nov 2015, 20:16:23

This Issue was resolved into two requirements:

1. "It should be possible to declare that a web resource is in the past, present or future with respect to another web resource". this was followed up in Action-70 https://www.w3.org/2015/spatial/track/actions/70 .

2. A reqirement to label events as being in the future compared to the context, as some form of prediction. That future time may have passed, and now be in the past.

Chris Little, 4 Feb 2016, 11:53:17

This Issue was resolved into two requirements:

1. "It should be possible to declare that a web resource is in the past, present or future with respect to another web resource". this was followed up in Action-70 https://www.w3.org/2015/spatial/track/actions/70 .

2. A reqirement to label events as being in the future compared to the context, as some form of prediction. That future time may have passed, and now be in the past.

Chris Little, 4 Feb 2016, 11:54:35

The propesed new requirement for the OWL Time deliverable remains

"It should be possible to declare that a web resource is in the past, present or future with respect to another web resource"

Frans Knibbe, 21 Mar 2016, 13:56:16

Porposal: we keep the basic requirement as it is ("It should be possible to describe time points and intervals in a vague, imprecise manner."). A more extensive list of examples will be supplied to illustrate what we mean by that. Examples to list are:
- An event happend at the second quarter of the 9th century (the calendar used for this fact is unknown)
- Something occured in the afternoon of july 1st, 2011 (the time interval 'afternoon' is not precisely defined)
- A photo is known to be taken on a Christmas day, but the year is unknown.
- An event took place in the later part of the Jurassic (with 'later part' being imprecise, as opposed to 'Late Jurassic')

Frans Knibbe, 21 Mar 2016, 14:04:52

Issue-15. A new requirement for the OWL-Time deliverable will be added to the
UCR document:

"*It should be possible to declare that a web resource is in the past, present or future with respect to another web resource*".

The OWL-Time ontology already supports this functionality, so no change. It does not include any predicates to link the time resources to objects/entities/features, or web-resources.

Some predicates could be defined to give some concrete examples as to how one would use OWL-Time to relate some resources, in any appropriate syntax, but it is probably inappropriate to standardize them.

Chris Little, 7 Jul 2016, 14:23:15

Issue-15. A new requirement for the OWL-Time deliverable will be added to the
UCR document:

"*It should be possible to declare that a web resource is in the past, present or future with respect to another web resource*".

The OWL-Time ontology already supports this functionality, so no change. The ontology does not include any predicates to link the time resources to objects/entities/features, or web-resources.

Some predicates could be defined to give some concrete examples as to how one would use OWL-Time to relate some resources, in any appropriate syntax, but it is probably inappropriate to standardize them.

Chris Little, 7 Jul 2016, 14:24:57

Closed since all detailed reviews indicate that the requirement is met by the ontology

Simon Cox, 18 Dec 2016, 12:05:56

Display change log ATOM feed


Ed Parsons <eparsons@google.com>, Kerry Taylor <kerry.taylor@anu.edu.au>, Chairs, Fran├žois Daoust <fd@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $