- From: Takeshi Kanai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jul 2015 02:18:55 +0000
- To: public-annotation@w3.org
@azaroth42 You are right. We "can" use the annotation context URI and make a valid JSON-LD. It is not necessary to list up all URIs in JSON-LD packets. On the other hand, as you admitted, the JSON-LD I wrote is also the valid data from grammatical view point. The Question is whether the JSON-LD I wrote is.valid as Annotation response or not. According to the spec, it sounds to me that the response is invalid because it does not describe the annotation URI, as context. The data was published from a LDP server while I was evaluating the protocol spec (I didn't put the iana staff though) Do I have to turn it to publish the annotation URI context only? Will the updated server pass the LDP tests? As @dret suggested, I think utilizing LDP properties, or available existing properties as much as possible is a huge plus to accelerate the adaption of Web Annotation protocol, and I think that is why Web Annotation Protocol is based on LDP, am I wrong? -- GitHub Notif of comment by tkanai See https://github.com/w3c/web-annotation/issues/52#issuecomment-119785491
Received on Thursday, 9 July 2015 02:19:02 UTC