api
api copied to clipboard
IIIF
Source for API and model specifications documents (api and model)
3.0 says that *all* resources must have `id`, however we introduce in 4 a LOT of new classes, including selectors, cameras, lights, unitValues and so on. The most egregious cases...
In the draft presentation 4 model, body, target, and motivation properties are not described even though they are linked to (in the Annotation class description, for example).
... to allow it to be captured on low / high poly count 3d models. For images height * width is a reasonable approximation of file size, but that's not...
This could be `metadata`, if we want to have multiple ways with labels in different languages to be seen by humans but less likely to be processed by machines: ```...
From Ruven's talk at the conference, a transform of the color space could be "negative". Useful for getting the positive of a digitized film negative, or (for some reason) the...
Currently it is only possible to represent a single ratio for scaling the unit lengths of canvases or scenes into physical dimensions. There are use cases, such as some X-Rays...
e.g. ``` {"unit": "m"} ``` is really a triple that relates the UnitValue instance via some predicate for 'has_unit' to some URI that identifies the concept of 'meters'.
We had this report through the website: "I found a problem with https://iiif.io/api/presentation/3/context.json. The JSON contains one occurrence of: ""@container" : "@set"," So, explicitly, there's a space before the colon....
In [Content State §3.1](https://github.com/IIIF/api/blob/main/source/content-state/1.0/index.md#31-linking-http-get-query-string-parameter), there appear to be two incorrect values for the `iiif-content` param. ## Example 1 The first is this example: ```html Link to Viewer ``` for which...
