Re: [web-annotation] avoid constraining HTTP

i don't want to hold up this work, so i will rest my case. but i am 
still confused why there even is a "protocol spec" talking about a 
server, and not just a mediatype/vocabulary spec. for example, right 
now it seems everything hinges on the fact that everything must be 
implemented by "the server". what if somebody for whatever reason 
serves different resources from different servers (physically or by 
switching domain names in some way)? does that make such an 
implementation non-conforming because there isn't one server 
satisfying all requirements? REST would say that such an 
implementation should be fine, and only broken clients (not following 
links but instead string-processing URIs) would have problems. but 
this is a very high-level question and i don't think one that can be 
discussed productively on github. so from a process point of view, 
feel free to consider this issue resolved.

-- 
GitHub Notif of comment by dret
See 
https://github.com/w3c/web-annotation/issues/51#issuecomment-135216418

Received on Thursday, 27 August 2015 00:26:32 UTC