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  November 2012

BIBFRAME November 2012

Subject:

Re: Annotation issues

From:

Lukas Koster <[log in to unmask]>

Reply-To:

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

Date:

Fri, 30 Nov 2012 18:36:29 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (133 lines)

Kevin,

Thanks. So in this example NYPL for instance publishes a news item on 
their website (which constitutes the Annotation) linking to the Bibframe 
Work (possibly in an LoC datastore) and the NYTimes article (either 
directly or indirectly). The Annotation Agent constitutes a type of 
provenance data (who said this?), but the Annotation is completely 
outside the framework more or less controlled by the library world. 
Which is perfectly OK with me. Is this what BIBFRAME makes possible? Do 
I interpret this correctly?

About the "target": I would say: in a library framework that is "on the 
web" and "of the web", we should link to the existing entities on the 
web directly. A BIBFRAME Work or Instance could of course be an existing 
online entity with a URI, right? Or do you see the BIBFRAME framework as 
a self contained implementation? In that case we will make a mistake.

About the Annotation links to Work or Instance: yes, in the case of a 
book cover it obviously has to be to an instance. But Annotation links 
to similar entities, like newspaper articles, should be the same, either 
to a Work or an Instance.

Hmm, writing this reply triggers me to think about the concepts and 
implications even more, as you may have noticed.

Lukas Koster
Library Systems Coordinator
Library and Information Systems Department
Library of the University of Amsterdam

On 30-11-2012 17:33, Ford, Kevin wrote:
> Hi Lukas,
>
>>   From the examples given I can't exactly figure out what the meaning of
>> Annotation Agent is.
> -- In short, it is the entity responsible for *creating* the Annotation.  Based on your email, I can see how the heading confounds; I'll be sure to modify it if I use it again.
>
>> the NYPL
>> asserts that the NYTimes article is in fact a review about the bibframe
>> work. Or it identifies that the NYPL publishes information that there
>> is a review about the work in the NYTimes that might be of interest to
>> the NYPL patrons.
> -- It's the second sentence:  NYPL (a source, and a trusted one we presume) says "here is the NYTimes review of this Work."
>
>> Then, the nature of the "target" relation. Does the target point to a
>> BIBFRAME metadata representation of the NYTimes article (containing a
>> URI to the actual article), or directly to the NYTimes article, or can
>> it be both?
> -- We're staring to think it might be best to provide both options: link to metadata resource and/or the review itself.  The metadata resource provides additional information that might aid in the display/comprehension of the "target" but being able to link directly to the target bypasses the need to parse an intemediary metadata resource.  Ultimately, I think community practice will inform actual practice: link to one or the other or both.  Other thoughts?
>
>> Then: there are two reviews, one annotation points to a bibframe:work
>> (NYTimes article), the other to a bibframe:instance (WashingtonPost
>> article). What is the difference? Shouldn't it both be just Work or
>> Instance? Not sure if a newspaper article should be a Work or an
>> Instance.
> -- Every time I saw this variation in my own slides I knew this would raise a question, and understandbly so.  I think both examples present perfectly viable possibilities, which is why I did it.  Community practice or rules may eventually guide whether the targets of Annotation resources should be to Work resources or Instance resources, or whether the linked-to target is dependent on the type of Annotation.  For example, the target of Review annotations might point to a Work while the target of a CoverArt annotation points to an Instance.
>
> Does this help?
>
> Thanks for bringing these questions to the listserv.  Much easier to provide fuller answers without a 140 character restriction (though that can be a good thing too). :)
>
> Warmly,
>
> Kevin
>
>
>
>
>> -----Original Message-----
>> From: Bibliographic Framework Transition Initiative Forum
>> [mailto:[log in to unmask]] On Behalf Of Lukas Koster
>> Sent: Friday, November 30, 2012 10:34 AM
>> To: [log in to unmask]
>> Subject: [BIBFRAME] Annotation issues
>>
>> I attended Kevin Ford's presentation at SWIB12. Unfortunately the sound
>> of the skype session was too bad to understand everything Kevin said.
>> The recording http://3windmills.com/kefo-swib12-bfi/ is much better.
>>
>> After watching the recording I have a couple of questions about the
>> Annotation core class. I already asked Kevin a couple of questions on
>> twitter about this after the SWIB12 Skype session. Fro completeness I
>> reproduce them here, as well as Kevin's answers.
>>
>> - Q: Annotation: isn't it just "relationships"? Why need extra entity?
>> (http://twitter.com/lukask/status/273749651759439873)
>> - A: Annotation can associate two Works (or Instances) not controlled
>> by the agent creating the Annotation. Provides buffer area.
>> Still, you raise a good question. We've debated this a number of times.
>>
>> - Q: can Annotations be used a) to flexibly extend the model? b) for
>> adding provenance data? Etc.
>> (http://twitter.com/lukask/status/273749990894092288)
>> - A: We're wondering about "b," but we've not done any work on it. I
>> think "a" is quite possible, and I've wondered the same.
>>
>> Now, in the presentation Annotations are called "assertions about the
>> other core class elements", holding all kinds of possible additional
>> information (reviews, holdings, book cover images, administrative data,
>> etc.). It is also said: "annotations are additional assertions".
>> There are a couple of examples from which you can see that an
>> Annotation has at least three possible relations: "annotates" (one of
>> the core classes), "target", which points at some external(?) entity
>> (like the book cover, or an article), and an unnamed relation that
>> identifies the "Annotation Agent". Besides that each Annotation
>> probably has a Title or Name property, and hopefully a Timestamp
>> property (to be able to define provenance).
>>   From the examples given I can't exactly figure out what the meaning of
>> Annotation Agent is. It could be provenance information: the NYPL
>> asserts that the NYTimes article is in fact a review about the bibframe
>> work. Or it identifies that the NYPL publishes information that there
>> is a review about the work in the NYTimes that might be of interest to
>> the NYPL patrons.
>> Then, the nature of the "target" relation. Does the target point to a
>> BIBFRAME metadata representation of the NYTimes article (containing a
>> URI to the actual article), or directly to the NYTimes article, or can
>> it be both?
>> Then: there are two reviews, one annotation points to a bibframe:work
>> (NYTimes article), the other to a bibframe:instance (WashingtonPost
>> article). What is the difference? Shouldn't it both be just Work or
>> Instance? Not sure if a newspaper article should be a Work or an
>> Instance.
>>
>>
>>
>> Lukas Koster
>> Library Systems Coordinator
>> Library and Information Systems Department Library of the University of
>> Amsterdam
>> Web: http://uba.uva.nl
>> Mobile site: http://m.uba.uva.nl
>> Digital Library: http://lib.uva.nl

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

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