[osis-core] annotateWork and annotateType

[Todd Tillinghast]

> From: owner-osis-core@bibletechnologieswg.org [mailto:owner-osis-
> core@bibletechnologieswg.org] On Behalf Of Steve DeRose
> Sent: Wednesday, August 21, 2002 1:08 PM
> To: osis-core@bibletechnologieswg.org
> Subject: RE: [osis-core] annotateWork and annotateType
> 
> At 02:48 PM -0600 08/20/02, Todd Tillinghast wrote:
> >This indicates to me that the description is out of date and needs to
be
> >updated to reflect the current understanding.  As recently as 8/18
(see
> >the post from Troy) osisRef was removed as an attribute from
> >globalAttributes for various reasons (see earlier posts) based on the
> >fact that the same behavior could be achieved using <reference> as I
> >outlined in the earlier post.
> >
> >(There are also earlier posts related to this use of <reference>.)
> >
> >The question is not whether this is a proper use of <reference> but
if
> >annotations have a different structure requires a special structure.
I
> >thought that an annotation was reference to an whole work and not to
a
> >point within the work and that is why we needed a special structure.
> >(This may bring up the issue of how we create a reference to an
entire
> >work or reference system.)
> 
> Why would annotation be a reference to a whole work? I don't get why
> that would be useful except in rare cases.

Agreed, better understanding what the purpose of annotation, I see how a
reference to a whole work does not make sense (I think I may have been
thrown off by the "Work" in annotation work").  To me this further
suggests that eliminating annotationWork and annotationType in favor of
using a child <reference> element.

Todd
> 
> 
> --
> 
> Steve DeRose -- http://www.stg.brown.edu/~sjd
> Chair, Bible Technologies Group -- http://www.bibletechnologies.net
> Email: sderose@speakeasy.net
> Backup email: sjd@stg.brown.edu