LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  July 2013

BIBFRAME July 2013

Subject:

Re: BF annotation and OA annotation

From:

Thomas Baker <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Wed, 31 Jul 2013 08:07:29 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (103 lines)

On Tue, Jul 30, 2013 at 02:17:31PM -0700, Karen Coyle wrote:
> On 7/30/13 12:15 PM, Ray Denenberg wrote:
> >points out that an OA Annotation may have multiple bodies.  So if
> >we were to declare for example that the two properties,
> >bf:hasCoverArt and bf:hasCoverartThumb,  were both subproperties
> >of oa:hasBody, then a cover art Annotation which  incudes both
> >(i.e. a link to cover art as well as to a thumbnail) could be
> >viewed from an OA perspective as an Annotation with two bodies.
> 
> Thanks, Ray, but I think this misses the point of Rob Sanderson's
> message[1], which I then tried to illustrate.[2] Rob says:
> 
> * The different semantics -- hasCoverArt conveys a very different
> relationship to hasBody.  The /annotation/ does not have the image as its
> cover art, the target of the annotation is the resource that it is the
> cover art for.
> 
> I illustrated it this way:
> 
> A has target B
> A has cover art C
> 
> If this means that B is the target of A, then it also means that C is
> the cover art of A.
> 
>  "hasCoverArt" could not be a sub-property of oa:hasBody, since "has
> body" is saying that the annotation is the subject of the statement,
> and the body is its object. Unless Rob and I are mistaken in our
> interpretation, 

I agree that in the absence of a fuller definition, the property name alone --
"hasCoverArt" -- invites this interpretation, but a name is just a name...

If hasCoverArt were a sub-property of oa:hasBody, I would take it to mean
something like "has-body-that-happens-to-be-cover-art".  If that is indeed the
intended meaning, then I do not see an obvious way to convey that notion in a
short property name, so if defined appropriately, the property could be called
"hasCoverArt" and formally mean something like: "the annotation is associated
with cover art of which we can infer, since the property is a sub-property of
oa:hasBody, that it is the body of an annotation".

So I agree that the name "hasCoverArt" is problematic because it implies a
model that is probably not intended.  However, a property with this name
_could_ be formally defined in a way that is compatible with what you and Rob
suggest.  

Tom

>                  ...this is a modeling error, unrelated to any conflicts
> between OA and BF. The body could have a type, but the type is not
> logically the relationship to the annotation.
> 
> If Body1 is an image of a cover, then you can see the difference between:
> 
> Anno1 -> hasBody -> Body1 -> is type of:cover art
> Anno1 -> hasCoverArt -> Body1
> 
> The body can BE an instance of cover art, but I don't think that the
> annotation can have cover art. The annotation is a relationship
> between a body and a target.
> 
> In that email [2] I proposed a way that BIBFRAME could type its
> annotation bodies, which I believe would give you the detailed body
> type information you desire. You then can still have multiple bodies
> and be compatible with OA, as Tom pointed out.
> 
> kc
> 
> 
> [1] http://listserv.loc.gov/cgi-bin/wa?A2=ind1307&L=bibframe&T=0&P=4206
> 
> [2] http://listserv.loc.gov/cgi-bin/wa?A2=ind1307&L=bibframe&T=0&P=4656
> 
> 
> 
> 
> [1] http://listserv.loc.gov/cgi-bin/wa?A2=ind1307&L=bibframe&D=0&T=0&P=4206
> >
> >I knew that an OA Annotation could have multiple bodies but I
> >hadn't thought through the implications of that quite in these
> >terms. Tom's argument is convincing enough for me. So we will
> >define all BIBFRAME Annotation-class-specific properties to be
> >subproperties of oa:hasBody.   And, we will define bf:annotates to
> >be a subproperty  of oa:hasTarget.
> >
> >I appreciate the comments on and discussion of BIBFRAME
> >Annotations and we hope to have draft 2 of the model ready to
> >review soon.
> >
> >Ray
> >
> 
> -- 
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet
> 

-- 
Tom Baker <[log in to unmask]>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager