IIIF/discovery

Content State in a POST

tomcrane opened this issue · 3 comments

Should POST be in the body, or as www-form-encoded?

Content State section 3.1.2 doesn't specify this.

Scenario: A citation search engine sending a content state to another page that then generates a view.

(breaking this out of #51)

Call on 11 Nov - www-form-encoded supports some real use cases (people emailing chunks of JSON to each other) so this should be the mechanism supported by the spec.

Agreed on Discovery call - addressed so OK to close!