Right now we expose a "compact API" where all collections are represented as a parameter in the collection related paths.
Another approach is to expose a few explicit paths in document, on a per collection basis (one for the collection description, one for the items, eventually the tiles one too). This is done by Interactive Instruments, generating a huge API document (600+ KB):
If we do this, then we can expose attribute based filtering (allow adding attributeName=value in the requests), but this would also require listing the attributes in the API document, and then go through another round of CITE testing, as there are tests covering that functionality that we are not skipping.
aaime
commented
5 years ago
Right now we expose a "compact API" where all collections are represented as a parameter in the collection related paths. Another approach is to expose a few explicit paths in document, on a per collection basis (one for the collection description, one for the items, eventually the tiles one too). This is done by Interactive Instruments, generating a huge API document (600+ KB):
If we do this, then we can expose attribute based filtering (allow adding attributeName=value in the requests), but this would also require listing the attributes in the API document, and then go through another round of CITE testing, as there are tests covering that functionality that we are not skipping.