...
| Id. | Author | Section/Page number | Title | Comment |
|---|---|---|---|---|
| 1 | JM | STAC-CORE-GEN-REC-0020 | Use of mixed case in e.g. platform values | Mis-alignment with the "searchable identifiers" recommendations here: https://github.com/radiantearth/stac-spec/blob/master/best-practices.md. Perhaps the recommendation should be that the naming follows GCMD but best practice for the case sensitivity is that of STAC. (Open for discussion) |
| 2 | Mario Winkler (DLR) | STAC-CORE-COL-REC-0110 | Collection Identifier | The specific collection names for each EOF Service should be defined in the corresponding EOF Service ICDs since the set of collections is known in advance. |
| 3 | Mario Winkler (DLR) | STAC-CORE-COL-REC-0120 STAC-CORE-ITEM-REQ-0180 STAC-CORE-ITEM-REC-0190 | Semantics of "created" and "published" | The semantics of the "created" and "published" properties may differ between the EOF services. This should be reflected in the individual EOF Service ICDs. |
| 4 | Mario Winkler (DLR) | STAC-CORE-ITEM-REC-0190 | Additional timestamp information | There is a difference between data not being valid and not being available any more. Maybe differentiate this by also using the "unpublished" property from the Timestamps extension. |
| 5 | Mario Winkler (DLR) | STAC-API-ADVSRCH-CREQ-0630 | Set of fields returned by default | The default fields may differ between the various EOF Services and should be defined in the service-level ICDs. |
| 6 | Mario Winkler (DLR) | STAC-API-ADVSRCH-CREQ-0640 STAC-API-ADVSRCH-CREQ-0650 | Empty or no "fields" directive | Maybe consider to allow an EOF Service to tailor this behavior e.g. to optimize query performance. |
| 7 | ||||
| 8 | ||||
| 9 | ||||
| 10 | ||||
| 11 | ||||
| 12 | ||||
| 13 | ||||