Christopher Hanna Johnson

Side note: OPTIONS should also not return a response body for `info.json`, so the correct server response would be a 204 not a 200.

AWS OpenSearch supports only Elasticsearch clients up to 7.13.4 in `compatibility mode`: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/samplecode.html#client-compatibility

even though `requiredStatement` replaces `attribution` in the 3.0 API, the property `attribution` itself cannot be deprecated since it is valid in 2.1. Therefore, I do not agree with the method...

Using String Enums and putting them in a reusable npm is a good idea. This is what I have done previously in Java with [iiif.vocabulary](https://mvnrepository.com/artifact/de.ubleipzig/iiif.vocabulary/0.1.1) . I guess it is...

@edsilv thank you for the reply. I added a test that checks if it loads correctly, and that resources can be read (I reused getManifestType() and getSequenceByIndex(0) ). See lines...

[SHACL](https://www.w3.org/TR/shacl/) could also be used. Here is an example that tests the Image API `exif:width` and `exif:height` properties for cardinality, datatype and inclusion. ```turtle @prefix rdf: . @prefix rdfs: ....

@azaroth42 I believe that the Presentation API should provide `@type` for the service class. Similarly, an Image API service does not provide an `@type`, though doing so would make the...

@zimeon true, but the server throws `Server Side Error: encoder error -2 when writing image file ` when it is retrieved (for me)... I agree that the service should be...

As a point of reference for this issue, I have been working on a generalized [JSON-LD API test](https://github.com/ub-leipzig/api-constraint-validator) suite with Presentation API 2.1.1 manifests as the first test cases. I...