Describe patterns for cross version Collections?

[azaroth42]

Can a v2 Collection contain a v3 Manifest? What about vice versa? Which context do the member resources use?

What if there are viewingHint values from v3, but the collection is v2?

And similar annoying forwards/backwards compatibility issues.

[azaroth42]

Related to IIIF/api#1064, IIIF/api#518 for cross-version weirdness

[azaroth42]

Ed's discussion: Yes we should be able to do this, and the embedding resource's version should be able to be used directly for the description, even if the referenced resource's version is different. Describe in cookbook.

e.g. v3 collection can use id for the id of a v2 manifest that it includes.

[azaroth42]

Closed by IIIF/api#1408

[azaroth42]

@mixterj and I think that this doesn't work for a v2 collection that includes v3 manifests. We should determine if this is necessary, and if so then figure out a solution.

[azaroth42]

Not going to write into v3 spec that v3 clients should support v2. Also not going to go back and change v2 specs, which is where it would need to be. So this is at best a cookbook issue.

[azaroth42]

Removing presentation as meaningless -- all cookbook entries are somehow presentation related

[glenrobson]

Cookbook discussion: previously made decision to not include version 2 recipes but this could is exception as its version 3.0 recipes with 2.0 assets.