Re: multiple bodies and motivations

Hi Ray,

My question would be, are we conflating motivation with structural
implications? That a thing is a tag seems to me to say more about its
intrinsic nature, i.e., a tag is a sort snippet of text, a semantic tag is
a named entity, rather than the role it plays in the annotation. That being
said I do think that there is likely room in the model for a motivation (or
more properly a role) property on the body.

We may want to be cautious here because there will likely be cases where
the role a body plays in an annotation is sensitive to the environment the
annotation finds itself in. In some environments some text might be
explaining the target and in others it might be describing it. Since the
model is extensible it might be best to leave it to individual communities
to develop value added extensions particular to their annotation
repositories rather than try to develop an over-arching taxonomy of body
types that will likely be incomplete.

Regards,

Jacob

_____________________________________________________
Jacob Jett
Research Assistant
Center for Informatics Research in Science and Scholarship
The Graduate School of Library and Information Science
University of Illinois at Urbana-Champaign
501 E. Daniel Street, MC-493, Champaign, IL 61820-6211 USA
(217) 244-2164
jjett2@illinois.edu

_____________________________________________________
Jacob Jett
Research Assistant
Center for Informatics Research in Science and Scholarship
The Graduate School of Library and Information Science
University of Illinois at Urbana-Champaign
501 E. Daniel Street, MC-493, Champaign, IL 61820-6211 USA
(217) 244-2164
jjett2@illinois.edu

On Wed, Mar 18, 2015 at 12:55 PM, Denenberg, Ray <rden@loc.gov> wrote:

> We ran out of time while I was on-Q so I’ll carry my thoughts to email.
>
>
>
> The issue is multiple bodies with multiple motivations. In the model
> currently,   a  motivation, applies to the entire annotation. How do you
>  associate a motivation with a  body.
>
>
>
> It seems to me that a straightforward approach is for each body to have a
> class  (with implied motivation).   Someone mentioned, if it’s a tag, you
> know it’s a tag. If it’s a sematic tag, you know it’s a semantic tag.  How
> do you know? Because the body is classed as oa:Tag or oa:SemanticTag.   So
> it works for those two, why wouldn’t that work in general?
>
>
>
> Ray
>