Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bodies and targets clarification in content-state section linking HTTP GET Parameter #2294

Open
giacomomarchioro opened this issue May 10, 2024 · 1 comment
Labels
content-state Issue relates to the content state API editorial

Comments

@giacomomarchioro
Copy link

Just a clarification linked to IIIF/cookbook-recipes#485

In content state 3.1. Linking: HTTP GET (Query String) Parameter section:

When the intention is to initialize the viewer at a particular part of the resource, the client provides more than just a URI; it must provide either the full annotation as in 2.2.1., or, preferably (for brevity) the body of the annotation, as in 2.2.3

Section 2.2.1 refers actually to the target body.

I guess that section 3.1 is actually referring to target or target body not the body.

I was also wondering if it would be better to call the section just target because in WAD I cannot find any reference to targets bodies, but maybe I am wrong.

@azaroth42
Copy link
Member

I think this is a bug/typo in the spec. There's no such thing as a target body, should just be the target.

@azaroth42 azaroth42 added editorial content-state Issue relates to the content state API labels Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-state Issue relates to the content state API editorial
Projects
None yet
Development

No branches or pull requests

2 participants