Re: [web-annotation] avoid constraining HTTP

I'm not sure if I follow the reasoning for SHOULD. If I buy a double
quarter-pounder at mcdonald's it would be strange to find a big mac in it's
package when I got home...

Does that make sense?

If I ask a server for one kind of data and then magically get another, it
seems like it will be harder to build clients. Wouldn't that basically
reduce us to reinventing the web browser (because I might be getting
anything back from the server)?

_____________________________________________________
Jacob Jett
Research Assistant
Center for Informatics Research in Science and Scholarship
The Graduate School of Library and Information Science
University of Illinois at Urbana-Champaign
501 E. Daniel Street, MC-493, Champaign, IL 61820-6211 USA
(217) 244-2164
jjett2@illinois.edu

On Wed, Jul 8, 2015 at 2:41 PM, Randall Leeds via GitHub <sysbot+gh@w3.org>
wrote:

> I think the basic point @dret is making is that even if a server
> doesn't advertise support for certain things the client could still
> try throwing things at it and they might stick.
>
> But also, there seems to be a question we haven't answered here. I
> think one answer motivates the MUSTs.
>
> Must an annotation container only contain annotations?
>
> Even if the answer is "yes" then I think SHOULD might be more
> appropriate. If the answer is "no" then the MUST is _definitely_ not
> appropriate.
>
> --
> GitHub Notif of comment by tilgovi
> See
> https://github.com/w3c/web-annotation/issues/51#issuecomment-119709221
>
>