New property-based time model. Fixes #499

[rjyounes]

No description provided.

[rjyounes]

Anyone who wants to review in addition to the assigned reviewers, please do!

I've added a few skos:editorialNotes to weigh in on.

[mkumba]

I'm having a heck of a time figuring out how and where to put comments, hope this is it.

I'm good with changes. In terms of the editorial notes that were in the presentation and didn't make the file, yeah I think that's a good idea.

Also on the question of atDateTime being just gist:dateTime I'm ok with that.

[rjyounes]

@mkumba @marksem @DanCarey404: @uscholdm and I both think CurrentEvent is preferable to and clearer than ContemporaryEvent, and I've made that update to the file. Please comment if you don't like it.

[uscholdm]

I suggest using "OngoingEvent" because a very recent event will generally be regarded a current. The term 'current event' refers to a general time period not whether the event is still happening. E.g. a trial that was just completed, its over but it's in the news and is regarded as a current event.

[rjyounes]

@uscholdm I think I agree with you. However, does "ongoing" lend a sense of continuing over some significant period of time? E.g., I am currently stopped at a red light, but I wouldn't call that an ongoing event. Is this too much of a quibble?

[rjyounes]

I think the advantage of Contemporary is it contrasts more naturally with Historical. But I'm OK with Contemporary, Ongoing, or Current, whatever others prefer.

[uscholdm]

Let's hope the event of discussing this is not ongoing for too much longer :-)

[rjyounes]

Question: If the date predicates have precision +/- 12 hours, shouldn't the minute predicates have precision +/- 30 seconds rather than 1 minute?

[bpelakh]

Just a voice from the peanut gallery, but it's about time (heh) that this change was made. 👍

[rjyounes]

@bpelakh Since this is a public repository, you would have been welcome to submit a PR!

[DanCarey404]

I went with the term "contemporary" because I had an essentially boolean category :Contemporaneity. And I had that because there was no real word for "currentness". I prefer contemporary or current, but not ongoing.

[DanCarey404]

I used :atDateTime versus just :dateTime because the latter looks too much like a datatype, in my opinion. Also, the subproperties I have created in my projects feel more natural with the "at" included. :startAtDateTime, validateAtDateTime, changeAtDateTime, etc.

[rjyounes]

@DanCarey404 Regarding the property names, datatype property names are nouns by convention, and startDateTime is a noun, whereas startAtDateTime is verbal. It's also less awkward, IMO. I had the same concern about gist:dateTime but Dave thought it was fine, and I wanted to keep the names parallel. I'd be OK with gist:atDateTime and gist:startDateTime, etc., though.

[DanCarey404]

This property name is definitely not a hill to die on. I just wanted to explain the origin in case anyone found it persuasive.

[uscholdm]

See inline. A few key things.

• there is some stuff in this PR that belongs elsewhere - how did it get here?
• need more details in release notes

All requested changes have been addressed.

[rjyounes]

Closing this PR because history has gotten screwed up. Have re-opened as PR #629 with a clean history.