Hi,
after reading #851, #147 etc, I understood that
Unless otherwise noted, objects defined by this specification MUST NOT contain any additional members. Client and server implementations MUST ignore members not recognized by this specification.
This schema is as restrictive as possible, but has flexibility to be extended within your documentation. Validation will not yield false negatives, but could yield false positives for the sake of flexibility.
so to confirm, for Pagination links
the spec said:
The following keys MUST be used for pagination links:
first
: the first page of datalast
: the last page of dataprev
: the previous page of datanext
: the next page of data
But something like the following could pass the validation
"links": {
"next": "http://xxx/2",
"otherLinks": {
"3": "http://xxx/3",
"4": "http://xxx/4"
}
}
Questions:
-
can Pagination have keys other than âfirstâ, âlastâ, âprevâ, ânextâ to be regarded as compliant with the spec (or media type âapplication/vnd.api+jsonâ)?
-
similarly, can Error Source property have keys other than âpointerâ and âparameterâ? (e.g., other keys like âheaderâ)