W3C home > Mailing lists > Public > public-openannotation@w3.org > July 2012

Re: [Open Annotation] some questions

From: Christian Morbidoni <christian.morbidoni@gmail.com>
Date: Thu, 19 Jul 2012 10:26:48 +0200
Message-ID: <CAE_W9BhmyvVjYdohvRzs-9sAQJxKbWtmhOPQdxcPWSzf8-uhJg@mail.gmail.com>
To: Robert Sanderson <azaroth42@gmail.com>
Cc: Paolo Ciccarese <paolo.ciccarese@gmail.com>, public-openannotation@w3.org
Hi all,

On Thu, Jul 19, 2012 at 8:49 AM, Robert Sanderson <azaroth42@gmail.com>wrote:

> On Wed, Jul 18, 2012 at 8:39 PM, Paolo Ciccarese
> <paolo.ciccarese@gmail.com> wrote:
> >> Is it covered by the FragmentSelector and hasSource in place of
> >> hasPageContext, and the element id as the object of the rdf:value
> >> property?  Or if that's not appropriate, then a new selector with the
> >> named section and the html page linked to the specific resource.
> >> Perhaps I'm misunderstanding the exact nature of the named target?
> >
> > If I want to say that the image has been annotated while part of the Open
> > Annotation Community page:
> > http://www.w3.org/community/openannotation/
> > Could I add something in the oa:SpecificResource instance pointing to
> that
> > page?
> From reading the pund.it documentation (and discussion with Marco
> Grassi) I'm not sure that's the same requirement?
> To try and characterize my understanding:
> If there's a web page that is cooperating with an annotation client to
> assign URI identifiers to its internal sections, how should this be
> expressed in the Open Annotation model?
> If that's correct, then it's a Selector that selects based on the
> identifier.  It seems very similar to a FragmentSelector, but in the
> HTML given by Christian, would select based on the "about" attribute
> rather than "id".
> Something like:
> <_:Anno1> a oa:Annotation ;
>   oa:hasSource <_:Body1> ;
>   oa:hasTarget <_:SpecificResource1> .
> <_:SpecificResource1> a oa:SpecificResource ;
>   oa:hasSource <http://example.org/page/1.html> ;
>   oa:hasSelector <_:AASelector> .
> <_:AASelector> a oax:AboutAttributeSelector ;
>   oax:about <http://example.org/section/123> .
> This seems like it could be accomplished without a new class however.
> xpointer(//[@about="http://example.org/section/123"])
> would also select the same element?

This seems formally correct, but I need to think about it :-)
Two things that cames in mind:
- a named content can be embedded in more than one page. I think the
proposed model addresses this issue anyway.
- most of the times we are annotating "specific sections" of a named
content. E.g. a word in a paragraph (where the paragraph is marked up as a
named content). In this case we use Xpointers like the following:
To indicate a text in the second <p> inside the named content
This allows us to resolve the xpointer independently from the page where it
is embedded.
How would I model this with selectors? not sure



> Rob
Received on Thursday, 19 July 2012 08:27:19 UTC

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