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

Re: Checking the RDF for a video annotation

From: Paolo Ciccarese <paolo.ciccarese@gmail.com>
Date: Wed, 15 May 2013 11:46:56 -0400
Message-ID: <CAFPX2kD=dJPsDoLDsFVx3m6wSdPXB=iUMqdydRJM6nzP5Xzzog@mail.gmail.com>
To: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Cc: James Smith <jgsmith@gmail.com>, public-openannotation <public-openannotation@w3.org>
Hi James,
I believe video annotation is of growing interest in our community so I was
wondering if you could help me out in creating an entry in the Cookbook
with your example.

This is the code I have at the moment

<anno> a <oa:Annotation> ;
       oa:hasBody _:body ;
       oa:hasTarget _:target .

_:body a <oa:Body> ;
       cnt:chars "I like that!" ;
       cnt:characterEncoding "utf-8" ;
       dc:format "text/plain" .

_:target a <oa:SpecificResource> ;
         oa:hasSource <videoURL> ;
         oa:hasSelector _:selector ;
         oa:hasScope <pageURL>.

_:selector a <oa:Composite> ;
           oa:item _:svgSelector ;
           oa:item _:fragSelector .

_:svgSelector a <oa:SvgSelector> ;
              cnt:chars "svg source..." ;
              cnt:charEncoding "utf-8" ;
              dc:format "image/svg+xml" .

_:fragSelector a <oa:FragmentSelector> ;
               dcterms:conformsTo "http://www.w3.org/TR/media-frags/" ;
               rdf:value "t=npt:0,5" .

Do you have a motivation (probably oa:commenting?) in the above example?

Also, if possible,  could you provide the missing details (from a real
example: SVG selector videoURL and pageURL) and maybe screenshots of the
real application displaying the annotation?


On Wed, May 8, 2013 at 7:58 PM, Stian Soiland-Reyes <
soiland-reyes@cs.manchester.ac.uk> wrote:

> On 8 May 2013 18:22, James Smith <jgsmith@gmail.com> wrote:
> >> cnt:charEncoding  should be cnt:characterEncoding  - it is useful to
> > This was a typo on my part in transcribing to email. The code has
> cnt:characterEncoding for the RDF/JSON production. I've dropped it from the
> JSON-LD version since JSON-LD strings are Unicode, the Unicode encoding
> (UTF-8, -16, ...) presumably holds for the entire JSON-LD document, and I
> didn't see it in the suggested context while I did see other properties
> from the cnt: namespace.
> No, it is not really needed, as by its definition it is more of a
> provenance thing, like "I read this string from a file and assumed
> this encoding"; which probably is not true as you are generating the
> SVG.
> > I'm targeting JSON-LD at this point. This is a JavaScript application
> living in the browser, so I figure JSON-LD is a natural fit for that aspect
> of a video annotation system. I'll leave RDF/XML as an exercise for a
> server component.
> (as JSON-LD supporter) Great! Then I guess you should stay far away
> from Content as XML ;)
> --
> Stian Soiland-Reyes, myGrid team
> School of Computer Science
> The University of Manchester
> http://soiland-reyes.com/stian/work/

Dr. Paolo Ciccarese
Biomedical Informatics Research & Development
Instructor of Neurology at Harvard Medical School
Assistant in Neuroscience at Mass General Hospital
Member of the MGH Biomedical Informatics Core
+1-857-366-1524 (mobile)   +1-617-768-8744 (office)

CONFIDENTIALITY NOTICE: This message is intended only for the addressee(s),
may contain information that is considered
to be sensitive or confidential and may not be forwarded or disclosed to
any other party without the permission of the sender.
If you have received this message in error, please notify the sender
Received on Wednesday, 15 May 2013 15:47:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:38:23 UTC