- From: Jacob Jett <jgjett@gmail.com>
- Date: Mon, 27 Oct 2014 08:07:59 -0500
- To: Paolo Ciccarese <paolo.ciccarese@gmail.com>
- Cc: W3C Public Annotation List <public-annotation@w3.org>
- Message-ID: <CABzPtB+3oynV=6Zfn5W1NYND+=3yeORTf7Dkq+AvUcJbqD8q1A@mail.gmail.com>
Hi Paolo, How are we to express the oa:Composite entity in JSON-LD? It's nothing like a list entity and I'm pretty confidant that expressing it as an array is not the correct way to express it. Regards, Jacob On Mon, Oct 27, 2014 at 7:39 AM, Paolo Ciccarese <paolo.ciccarese@gmail.com> wrote: > Dear all, > in the process of defining the first draft of the model, the plan emerged > in the last call is to (i) start from the Community draft ( > http://www.openannotation.org/spec/core/), (ii) get rid of the SPARQL > queries and (iii) replace the turtle with JSON-LD. > > Also, after the email discussions, the current orientation is to > > 1) replace the Choice/Composite/List constructs with one simple list-based > construct as follows: > { > "@type": "oa:List", > "members": ["eg:target1", "eg:target2", "eg:target3"] > } > > Choice as list of descending priority > > { > "@type" : "oa:Choice", > "members": ["eg:option1", "eg:option2", "eg:option3"] > } > > 2) Replace ContentAsText with something like: > { > "@type": "oa:Content", > "value": "I love this book!", > "format": "text/plain", > "language": "en" > } > > Where: > * rdf:value -- for recording the content (required) > * dc:format -- for the media type of the content (optional) > * dc:language -- for the language of the content (optional) > > Content encoded using UTF-8. > > See you tomorrow for further discussions, > Paolo > > >
Received on Monday, 27 October 2014 13:09:12 UTC