search

IIIF / discovery

8 stars 3 forks source link

Is a full manifest a content state? #71

Closed tomcrane closed 3 years ago

tomcrane commented 3 years ago

https://preview.iiif.io/api/content-state-comments/api/content-state/0.2/#initialization-mechanisms-paste

In the examples following the above link (3.1.3 onwards), a client could quite easily accept a full Manifest as a drop/paste/upload action. Not just a URL, or a JSON annotation pointing at a Manifest, but the full thing. Should the Content State API discuss that? In other words, can a full Manifest be a content state target, as well as the id-and-type-only version in 2.2.3?

https://preview.iiif.io/api/content-state-comments/api/content-state/0.2/#223-target-body

This permits the following content state:

{
    "id": "https://example.org/iiif/item1/manifest",
    "type": "Manifest"
}

(just the target of an implied annotation). Why not accept the rest of it, using the embedded/referenced distinction from the Presentation API?

Or, is the ability to accept a full manifest there an implementation decision? No need for spec but maybe for recipes.

tomcrane commented 3 years ago

Discussed on call - "no" is the answer, at least for now. Let viewers decide to do this if they want to.