W3C home > Mailing lists > Public > public-annotation@w3.org > October 2014

Re: In preparation to the F2F: Data Model status

From: Robert Sanderson <azaroth42@gmail.com>
Date: Mon, 27 Oct 2014 12:22:47 -0700
Message-ID: <CABevsUG4+4TK=K8Bk2nEOBhpUUN3Wo5KfO9z_GvdwbLh5s02gA@mail.gmail.com>
To: Frederick Hirsch <w3c@fjhirsch.com>
Cc: Benjamin Young <bigbluehat@hypothes.is>, Paolo Ciccarese <paolo.ciccarese@gmail.com>, W3C Public Annotation List <public-annotation@w3.org>
I think that Turtle in an appendix, and linked from each of the sections
would be fine.  It puts the JSON up front as that's the recommended
serialization (at the moment) but doesn't get rid of the turtle completely,
if that helps.

I'm not in favor of keeping both in the specification body directly, the
same content twice seems like it would add a lot of length for saving a few
click throughs to the appendix.

If there are more serializations defined in the future, we can use the same
approach with the click-throughs.

Rob


On Mon, Oct 27, 2014 at 11:52 AM, Frederick Hirsch <w3c@fjhirsch.com> wrote:

> 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
> >
> >
>
>
>


-- 
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305
Received on Monday, 27 October 2014 19:23:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:29 UTC