Suggested formatting around allowing open ranges for the temporal property

[willpugh]

This pull request has been automatically generated by Prose.io.

[jpmckinney]

Why not conform to ISO 8601 and use a solidus (forward slash) as the separator? http://dotat.at/tmp/ISO_8601-2004_E.pdf

[willpugh]

Using ISO 8601 seems reasonable to me. . .

[jpmckinney]

Alternatively, as mentioned in #49, having an object with start and end keys may be clearer.

[willpugh]

Yeah. Missed that suggestion in #49. I do like using objects instead of string munging when ever possible.

So, I think an object with start and end makes a lot of sense. However, I would prefer for them to be things that look more like the dates in ISO 8601, rather than the broader definition of PeriodOfTime (which I believe can include epochs, etc).

As an implimentor, it seems more tractable to work with.

[jpmckinney]

Yeah definitely stick to ISO. The current dates aren't even ISO 8601 (which I'm pretty sure is what JSON uses).

[MarinaNitze]

In the final 1.0 schema being submitted internally for approval, all date fields use ISO 8601 of least resolution, and temporal includes the solidus for indicating range. Thanks for your thoughtful feedback on this!