search

opengeospatial / CoverageJSON

Public repo for CoverageJSON project
Apache License 2.0
10 stars 8 forks source link

Clarify Temporal RS definition #72

Closed jonblower closed 2 years ago

jonblower commented 2 years ago

Addresses #60

jonblower commented 2 years ago

The substantive change here is that the spec now makes the ISO8601-based string representation mandatory for the common case of using TemporalRS with a Gregorian calendar. The intention is to make it easier to develop clients that handle this common case, whilst not precluding the possibility of allowing other representations in future.

jonblower commented 2 years ago

Would benefit from a review from @letmaik too

chris-little commented 2 years ago

@letmaik @jonblower Are you happy to merge now, or would you rather wait until the team meeting 2022-05-18 to give others a chance to consider?

jonblower commented 2 years ago

Ideally it would be great to have input from @marqh with a view to merging early next week if poss? If Mark's not available then maybe we could just give it a final sanity check in the team meeting so people have had a chance to see it.

chris-little commented 2 years ago

@marqh Are you happy with the CoverageJSON backward-compatible compromise wording? Recognising that we will probably do a larger scale alignment of temporal things in the next versions.

chris-little commented 2 years ago

agreed at 2022-05-18 meeting