W3C home > Mailing lists > Public > public-openannotation@w3.org > January 2013

Re: New Draft comments: textual bodies

From: Robert Sanderson <azaroth42@gmail.com>
Date: Fri, 11 Jan 2013 08:31:02 -0700
Message-ID: <CABevsUE-+9ZX2_QHW_QBw4DWxVucuvWydxZrSWA86uoKGOwsHw@mail.gmail.com>
To: Bernhard Haslhofer <bernhard.haslhofer@cornell.edu>
Cc: Antoine Isaac <aisaac@few.vu.nl>, public-openannotation@w3.org
The blank node solution provides a *single* simple pattern, rather than
requiring multiple simple patterns to be checked for for *every* annotation.

If someone, or some group, can propose a single, coherent model that can
accomodate the multiplicity constructs, tags being different from short
comments, can be cleanly expressed in a JSON-LD context, and preferably
also embedded resources such as CssStyle and SvgSelector that does not use
the Content as Text method, then the current method will be reconsidered at
that point.

If someone from flickr or company with a similarly extensive set of
annotations comes in and says that they will adopt Open Annotation, but
ONLY if we support text body as literal and NOT if they're required to use
a blank node, that would provide some additional weight.

But the difference between

{"@type" : "oa:Annotation",
 "body" : "I like this.",
 "target" : {"@id" : "http://flickr.com/images/1"}

{"@type" : "oa:Annotation",
 "body" : {"chars" : "I like this."},
 "target" : {"@id" : "http://flickr.com/images/1"}

is hardly a burden to support.

In short, please feel free to propose another method that works across the
entire model.


On Fri, Jan 11, 2013 at 8:11 AM, Bernhard Haslhofer <
bernhard.haslhofer@cornell.edu> wrote:

> Hi Rob,
> On Thursday, January 10, 2013 at 6:22 PM, Robert Sanderson wrote:
> > Then there's Markdown, various wiki languages, RTF, various XML or JSON
> dialects for mark up, etc etc. I don't see a client could be expected to
> know even that it can't properly render a comment without some level of
> metadata.
> >
> > Unless literals are restricted to *only* text/plain. So no markup at all.
> Take Flickr commons (http://www.flickr.com/commons) and look at the
> thousands of notes people provided for the images there.
> Those are real-world annotation examples all of them being simple plain
> strings. They could easily be represented as...
> flickr:note1 a oa:Annotation ;
> oa:hasBody "what are those holes for?" ;
> oa:hasTarget <
> http://www.flickr.com/photos/nationalmediamuseum/3588905866#xywh=160,120,320,240>
> # sample pixel values
>  > ;
> …without missing information a client needs to render an annotation.
> This should show that plain string annotations occur in the real world and
> I think OA should take this account and support this kind of simple
> annotations.
> But again: this is not against the existing ContentAsText approach for
> more complex requirements, which, I certainly agree, must be supported. It
> is, as Antoine said, just about providing simple patterns for simple,
> real-world needs.
> Bernhard
Received on Friday, 11 January 2013 15:31:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:03 UTC