- From: Takeshi Kanai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jun 2016 07:28:14 +0000
- To: public-annotation@w3.org
tkanai has just created a new issue for https://github.com/w3c/web-annotation: == (Protocol) Editorial issues about IRI == Minor editorial issues. The second paragraph in Section 5.1 says > Upon receipt of an Annotation, the server may assign HTTPS IRIs to all resources and blank nodes in the Annotation, and must assign a IRI to the Annotation resource, even if it already has one provided in the entity body description. - "HTTPS IRIs" should be "IRIs" I can't find any reasons to set HTTPS restriction in this line. - "a IRI" must be "an IRI" Right? By the way, I'm afraid the process "must assign a IRI to the Annotation resource" might be a little bit hard to imagine what it is necessary to do. I think "must assign an id property to the Annotation resource" is much easier to imagine, and it helps reading the next paragraph, my two cents... Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/299 using your GitHub account
Received on Friday, 10 June 2016 07:28:19 UTC