- From: Kanai, Takeshi <Takeshi.Kanai@jp.sony.com>
- Date: Wed, 2 Sep 2015 10:39:26 +0000
- To: Ivan Herman <ivan@w3.org>
- CC: Robert Sanderson <azaroth42@gmail.com>, W3C Public Annotation List <public-annotation@w3.org>
Hi Ivan, Thank you for the reply. I'm afraid that I just misunderstood the definition when I read FPWD. I didn't think "property" written in FPWD 3.2.1 included @language in JSON-LD. Then, I personally merged it into the FPWD 3.2.3. Actually, this is the first time for me to read a spec which prohibits its base format definitions, and it makes difficult to review the spec for me. I'm very sorry for making the discussion noisy, but I just wanted to make sure the details to make it work with general JSON-LD/RDF tools. Thanks, Takeshi Kanai -----Original Message----- From: Ivan Herman [mailto:ivan@w3.org] Sent: Tuesday, September 1, 2015 6:00 PM To: Kanai, Takeshi Cc: Robert Sanderson; W3C Public Annotation List Subject: Re: Basic Roles Proposal Hi Takeshi, > On 01 Sep 2015, at 10:34 , Kanai, Takeshi <Takeshi.Kanai@jp.sony.com> wrote: > > Hi Ivan and Rob, > > “role” is not mandatory and we can still put dc:language into “content” nodes, these are my understandings. Yes, that is my understanding, too. And, if we accept 3.2.3, then the content node can be replaced by a direct text, ie, "body" : { "language" :"en", "text" : "My comment" } is also valid. > Having “language” in body was “recommended” in the FPWD, but it is prohibited in the newly provided scheme 3.1.9, besides I found no language descriptions in the new document, then I got confused. I am not sure what you mean by 'recommended' and 'prohibited'. In the FPWD[1], if you use a simple textual body, then there is no language associated to it either; it explicitly says • The string body must be an xsd:string and must not have a language associated with it. I do not think 3.1.9 in the roles' document introduces any change on that. But I may misunderstand what you mean. Thanks Ivan [1] http://www.w3.org/TR/2014/WD-annotation-model-20141211/#simple-textual-body > Thank you for confirming it. > > > Regards, > Takeshi Kanai > > From: Robert Sanderson [mailto:azaroth42@gmail.com] > Sent: Saturday, August 29, 2015 12:06 AM > To: Ivan Herman > Cc: Kanai, Takeshi; W3C Public Annotation List > Subject: Re: Basic Roles Proposal > > > > On Fri, Aug 28, 2015 at 5:47 AM, Ivan Herman <ivan@w3.org> wrote: > Hi Takeshi, > > Let me confirm. If a person/system would like to set language to the body text for some reasons, the person/system has to take 3.1.2 or 3.1.3 approach and add unknown role property. Correct? > > Although I am not Rob, but… > I believe it is not necessary to add an unknown property. Ie, > > "body": { > "content": { > "text": "I love this thing", > "language" : "en" > } > } > > is also fine. > > Yes, this is exactly correct :) > > Or the exact same structure in Turtle: > > _:anno a oa:Annotation ; > oa:hasBody [ > oa:hasSource [ > oa:text "I love this thing" ; > dc:language "en" > ] > ] > ] > > Though I expect that most annotations will at least be able to say that it's commenting versus tagging. > > > Actually, if we accept 3.2.3, then we can also say > "body": { > "text": "I love this thing", > "language" : "en > } > > Yep. > > Rob > > > -- > Rob Sanderson > Information Standards Advocate > Digital Library Systems and Services > Stanford, CA 94305 ---- Ivan Herman, W3C Digital Publishing Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Wednesday, 2 September 2015 10:40:15 UTC