Start property in collection context

[altomator]

The start property doesn't work when used in a collection context to open a manifest at a specific canvas.

Collection: https://raw.githubusercontent.com/altomator/IIIF/main/collection/collection-bd.json Sub-collection using the start property: https://raw.githubusercontent.com/altomator/IIIF/main/collection/collection-nemo.json

[cbeer]

Thanks for the report; a feature like this seems like it may be quite useful for constructing some more guided IIIF collections.

I'm concerned, however, that I'm not seeing anything in the IIIF Presentation API specification that states that a collection could provide additional or alternative properties than the referenced manifest, how to address conflict between difference sources, or which properties should have precedence. That said, the most I've seen to the contrary is the definition of referenced resources:

referenced: When a resource (A) is referenced from a referencing resource (B), an incomplete JSON representation of resource A is present within the JSON representation of resource B, and dereferencing the URI of resource A will result in additional information. Example: Manifest A is referenced from Collection B.

Elsewhere, there's a requirement that collections MUST use referenced manifests, but I'm not sure if incomplete/additional intend to limit how properties in each context may or may not vary. Perhaps this should be referred upstream to the IIIF editors to offer guidance or clarification?

[enriquediaz]

What's being done here isn't supported in Mirador — this may be a question for the IIIF specification editors.