Re: [web-annotation] Intended Audience for Annotation

Hi Ray,

An example annotation, taking Benjamin's as a base:

{
  "@id": "http://example.org/annotations/1.json",
  "@type": "oa:Annotation",
  "annotatedBy": "http://highschool.edu/staff/SmithJ",
  "audience" : {
    "@id"   : "http://some.edu/audiences/teacher",
    "@type" : "schema:EducationalAudience",
    "schema:educationalRole" : "teacher"
   },
  "hasTarget": "http://publisher.com/epubs/textbook",
  "hasBody": {
    "@type": "oa:EmbeddedContent",    "value": "This textbook is good
for teaching the cell cycle, probably for 12-14 year olds.",
    "language": "en"   }}

The annotator (Smith, J) comments on a publisher's text book that it is
good for teaching the cell cycle.  The intended audience of the annotation
is other teachers, rather than the students who read the text book.  Thus a
reading system could determine who the user is, and whether they would fall
into that intended audience.

Hope that helps!

Rob



On Tue, Apr 14, 2015 at 7:08 AM, Denenberg, Ray <rden@loc.gov> wrote:

> I'd like to see a concrete example.  One that includes target and body.
>
> The closest to an example I see is "BigBlueHat commented 5 days ago" with
> two audiences (1)EducationalAudience/teacher, (2)ParentAudience/child age
> 12-14;  but no target or body is given in the example, only a  comment
> "For...middle school PTA meetings...or something",  and I'm having a hard
> time understanding the example.  Maybe if a target and body were supplied
> ....
>
> Mainly I want to be convinced that an annotation pertains to a particular
> audience, which might not be the same audience as that for the target.  I'm
> sure there are good examples, I'd just like to see one.
>
> Ray
>
> > -----Original Message-----
> > From: Ivan Herman via GitHub [mailto:sysbot+gh@w3.org]
> > Sent: Sunday, April 12, 2015 10:40 AM
> > To: public-annotation@w3.org
> > Subject: Re: [web-annotation] Intended Audience for Annotation
> >
> > I guess, from the model and spec point of view, what is needed to include
> > the "audience" property in the model. I think that is the only  change
> that is
> > required; I do not think our document should define anything as for the
> > content of the "audience", except than, possibly, relate in a
> non-normative
> > way to, e.g., the schema properties.
> >
> > However, Rob also referred to accessibility, etc, which may mean that,
> > instead of "audience" we would need a more general "hook" for that type
> of
> > additional metadata. But it should really be only a single such hook,
> and we
> > should not get bogged down (in my opinion) to an enumeration of all
> > possible such features...
> >
> > --
> > GitHub Notif of comment by iherman
> > See
> > https://github.com/w3c/web-annotation/issues/8#issuecomment-92072398
> >
>
>


-- 
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305