SortablesCollection sortables See Schema for a sortable description(sortable.yaml) in that section vs yaml has name instead of id and yml lacks any of optional fields: language, type, spatial-types, temporal-types and links
Duplicated definitions
In https://github.com/opengeospatial/ogcapi-records/blob/master/core/openapi/openapi.yaml are defined some entities, like extent that are already defined in other files It happens the same for other entities, is there any reason for this duplication?The properties differ also in the 2 files. are different entities? Otherwise which one is the correct one?
Extent crsExtent and yaml has crs as part of spatial, while in the openapi.yml is a property of extent. Some other differences
pvgenuchten
commented
3 years ago
Below is a list with observed inconsistencies between example yaml and spec.
Links section Links in spec vs yaml lacks property title.
Name or Id for collections CollectionInfo vs yaml has name instead of id: see also.
No items operation /collections/{collectionId}/items is not available in the yml file
Sortables Collection sortables See Schema for a sortable description(sortable.yaml) in that section vs yaml has name instead of id and yml lacks any of optional fields: language, type, spatial-types, temporal-types and links Duplicated definitions In https://github.com/opengeospatial/ogcapi-records/blob/master/core/openapi/openapi.yaml are defined some entities, like extent that are already defined in other files It happens the same for other entities, is there any reason for this duplication?The properties differ also in the 2 files. are different entities? Otherwise which one is the correct one?
Extent crs Extent and yaml has crs as part of spatial, while in the openapi.yml is a property of extent. Some other differences