personally (not as chair) I found that this as well, it helped me understand the deeper benefits of the model. Turtle in an appendix would probably do this as well.
regards, Frederick
Frederick Hirsch, Nokia
@fjhirsch
On Oct 27, 2014, at 8:28 AM, Benjamin Young <bigbluehat@hypothes.is> wrote:
>
> On Oct 27, 2014 5:40 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.
>
> Could we present both turtle and JSON-LD? I did that seeing turtle (or similar) helps me understand JSON-LD.
>
> But that might just be me. :)
>
> Thanks,
> Benjamin
>
> >
> > 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
> >
> >
>