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

Re: F2F Decision: Multiple Resources

From: Jacob Jett <jgjett@gmail.com>
Date: Tue, 30 Oct 2012 11:19:52 -0500
Message-ID: <CABzPtB+cesSLr-Y54mKju+LYx5rOZAru0PEOnkxjg9Rt3Ayb4g@mail.gmail.com>
To: Robert Sanderson <azaroth42@gmail.com>
Cc: Leyla Jael García Castro <leylajael@gmail.com>, Paolo Ciccarese <paolo.ciccarese@gmail.com>, public-openannotation@w3.org
Hi Rob,

I think the way you have it written below is best. What we really want to
do is capture the context that the annotation _:y is being made in. I think
capturing the relationship with annotation _:x through oax:asIncludedIn
will be more meaningful than having <choice1> as the object of the
oax:asIncludedIn predicate. It may be overkill though...since you could
hypothetically link back to annotation _:x through its relationships to
<choice1> using some method for reasoning / inferencing.

Since I don't think there are any rules in RDF that would prevent <choice1>
from being the object of oax:asIncludedIn, it seems like this is an area
were some best practice guidelines will need to be developed.

Regards,

Jacob


On Tue, Oct 30, 2012 at 10:37 AM, Robert Sanderson <azaroth42@gmail.com>wrote:

> On Tue, Oct 30, 2012 at 4:35 AM, Leyla Jael García Castro
> <leylajael@gmail.com> wrote:
> > Hi all,
> >
> > On Mon, Oct 29, 2012 at 10:31 PM, Robert Sanderson <azaroth42@gmail.com>
> > wrote:
> >>
> >> I don't see a problem with it, but should definitely be
> >> oax:asIncludedIn, as it can be used for both Body and Target.
> >> asAnnotatedIn would imply it could only be used for the target.
> >
> > @Rob. So, oax:asIncludedIn could be used for Body, Target, and
> Annotation as
> > well? It is used on an Annotation in Paolo's example (oax:annotatedIn).
> > Also in Paolo's example, what would be the difference between using
> > oax:asIncludedIn on the _x Annotation or on the <choice1> Body? Because
> both
> > would be possible, would not them?
>
>
> You could have a resource acting as a body which, for the purposes of
> the annotation, should be considered to be asIncludedIn another
> resource.
>
> Also, regarding previous examples, the asIncludedIn predicate as a
> domain of SpecificResource, as otherwise it would not be specific to
> the annotation.
>
>
> So:
>
> _x: a oa:Annotation ;
>   oa:hasBody <SpecRes1> ;
>   oa:hasTarget <target> .
>
> <SpecRes1> a oa:SpecificResource ;
>   oax:asIncludedIn <container-resource> ;
>   oa:hasSource <body-resource> .
>
> Thus, Jacob's case becomes slightly more complex:
>
> _:x a oa:Annotation ;
>   oa:hasBody <choice1> ;
>   oa:hasTarget <ny-times-article> .
>
> <choice1> a oa:Choice ;
>   oa:default <comment-in-french> ;
>   oa:item <comment-in-english> ;
>   oa:item <comment-in-spanish> .
>
>
> _:y a oa:Annotation ;
>   oa:hasBody <body> ;
>   oa:hasTarget <specificresource> .
>
> <specificresource> a oa:SpecificResource ;
>   oa:hasSource <comment-in-french> ;
>   oax:asIncludedIn _:x .
>
> (or should that be asIncludedIn <choice1> ? )
>
>
> Hope that helps,
>
> Rob
>
Received on Tuesday, 30 October 2012 16:21:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 October 2012 16:21:09 GMT