RE: ISSUE-125: Update datatypes in OWL Time

Simon,

On Monday, January 23, 2017 2:10 AM, Simon.Cox@csiro.au [mailto:Simon.Cox@csiro.au] wrote:

> I propose to resolve this issue by
> (i)                 Cloning the property time:inXSDDateTime as
> time:inXSDDateTimeStamp, using the new datatype that was built-in to OWL2
> (ii)               Deprecating time:inXSDDateTime in order to encourage people to be
> careful about timezones, while protecting the legacy.
> 
> OK?

I'm fine with those changes and also propose that we add at least time:inXSDDate and preferably time:inXSDgYear and time:inXSDgYearMonth, too,  so that those-of-us-that-don’t-have-data-with-second-precision can have an easy way to express our temporal information.

Best,

Lars

Received on Monday, 23 January 2017 17:05:46 UTC