search

opengeospatial / ogcapi-records

An open standard for the discovery of geospatial resources on the Web.
https://ogcapi.ogc.org/records
Other
59 stars 28 forks source link

clarify time vs. properties.created/properties.updated #189

Closed tomkralidis closed 1 year ago

tomkralidis commented 1 year ago

Table 10 defines time / properties.created / properties.updated as follows:

Queryable Requirement Description GeoJSON key
time required The temporal extent of the resource. Can be null. time
created optional The date the resource was created. properties.created
updated optional The more recent date on which the resource was changed. properties.updated

What would be the difference? I would time being closer to supporting temporal searching.

kalxas commented 1 year ago

I think this roots back to DublinCore including those time elements separately. It would be good to keep for backward compatibility, but yes we should probably define where the temporal search is applied.

doublebyte1 commented 1 year ago

I think there was a discussion to use "created" and "updated" referring to the time the record was created, in order to align it with stac: https://github.com/opengeospatial/ogcapi-records/issues/178

pvretano commented 1 year ago

This issue is resolved by PR #179. The PR renames recordCreated and recordUpdated to created and updated to align with STAC and removes created and updated from Table 10. The created and updated fields from Table 10 (which refer to the resource) are moved into the link structure.

pvretano commented 1 year ago

28-NOV-2022: Agreed to merge PR #179. @tomkralidis can then review and close this issue.

pvretano commented 1 year ago

12-DEC-2022: Closing with @tomkralidis consent.