Open azaroth42 opened 2 years ago
Editors call 2022-02-24 -- can it actually just go in prezi 2 / prezi 3 context?
Additional issue - the use of type
for @type
is a problem in Presentation 2 as it's JSON-LD 1.0 not 1.1
If we define type: @type
in the context, then it will create that alias for all of the manifest. At the moment the 2.1 processor would ignore type
, and thus lose the class.
I think the human readable spec (what is currently in annex and moving to registry) needs to be updated with the following:
type
alias will be used in preference to the full @type
term. Which we can't do, so the spec should say to use @type
for prezi2, and type
for prezi 3. Could reference the service definition in prezi3 that has the same problem. (https://iiif.io/api/presentation/3.0/#service )full
and if used with image 3 then full
no longer exists, so should be max
I created the selectors context and it's available here: https://iiif.io/api/registry/selectors/context.json. The updated and migrated Registry of Selectors page is here: https://iiif.io/api/registry/selectors/. We should remove or archive the old annex page. In Eds discussions, we decided to write the context for prezi 3, with a note in the registry page re: Image API 2/3. Can we close this ticket?
In the Annotation Extensions document the selectors are in JSON-LD with their own properties, but those properties do not have a mapping in a context to predicate.
Questions/Tasks: