but at that point the response body has not been defined to it's confusion to read this statement. It is defined in Req. 10 through the link to collections.yaml.
2) The other small inconsistency is that Req. 9A requires itemType to be record, but the schema in Req. 10 doesn't actually enforce this.
I think the following should be added to the properties:
itemType:
enum:
- record
3) Lastly, req. 10 is confusing because it talks about the response body in general and the individual collection encoding in the same sentence:
The body of the response SHALL contain a description of the catalogue based upon the following schema fragment which extends the collections.yaml schema defined in the OGC API - Features - Part 1: Core standard:
The collections.yaml (with s) finally defines the response body, but the following yaml provided in Req. 10 only extends/overrides the collection.yaml (without s). It should be made more clear that this is an extension to the collection.yaml that is linked to from the collections.yaml.
1) Req. 9A talks about
but at that point the response body has not been defined to it's confusion to read this statement. It is defined in Req. 10 through the link to collections.yaml.
2) The other small inconsistency is that Req. 9A requires
itemTypeto berecord, but the schema in Req. 10 doesn't actually enforce this.I think the following should be added to the properties:
3) Lastly, req. 10 is confusing because it talks about the response body in general and the individual collection encoding in the same sentence:
The collections.yaml (with s) finally defines the response body, but the following yaml provided in Req. 10 only extends/overrides the collection.yaml (without s). It should be made more clear that this is an extension to the collection.yaml that is linked to from the collections.yaml.