- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jul 2015 20:08:41 +0000
- To: public-annotation@w3.org
:-1: The point of the protocol is to provide additional constraints to make development easier, by making such probes unnecessary. The protocol document does not constrain Web Servers that implement HTTP, it constrains Annotation Servers that implement the specification. Without additional constraints there's no need for a protocol document at all, we would just reference the HTTP RFCs and be done with it. Most of our requirements are inherited from http://www.w3.org/TR/ldp/ which, admittedly has weaseling along these lines: >Per [RFC7231], this HTTP method is optional and this specification does not require LDP servers to support it. When a LDP server supports this method, this specification imposes the following new requirements for LDPCs. (From section 5.2.3) We could also do that, but it seems redundant and unhelpful. What use is an Annotation Server that doesn't support the creation of Annotations? -- GitHub Notif of comment by azaroth42 See https://github.com/w3c/web-annotation/issues/51#issuecomment-119320589
Received on Tuesday, 7 July 2015 20:08:43 UTC