Karen I think  your last paragraph encapsulates it. Nate


From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Karen Coyle
Sent: Friday, December 12, 2014 7:29 PM
To: [log in to unmask]
Subject: Re: [BIBFRAME] bf:event


Nate, are you mainly looking at bf:Event and bf:event as ... I'm not sure what to call it, but let's say "creation events"? So they would be music performances, or a news program or perhaps an art exhibit? I presume a conference would also be an event, if it leads to conference papers, yes?

I ask because there is other metadata that uses a different definition of event. FRBRoo has publication itself as an event, as does <indecs>. has a broad definition of event that is just about anything taking place with a time and/or place. I could also imagine a subject scheme that considers WWII to be an "event" by some measure.

If BF is only considering creation events, then it would be good to specify that, or at least say what an event *isn't*. If bf:Event is a subclass of Work, then it seems that it must be a creation event, and cannot be an event like publication or distribution, or the date when an item was added to an archive.


On 12/10/14 7:35 AM, Trail, Nate wrote:

Steven, we have been looking at bf:Event a little , as a result of the AV paper. They suggested that Events could be thought of as Works, and I think we’re moving in that direction, ie., subclassing Work for an event, which gives you the ability to describe it much more thoroughly than just date, time, place.  There is some confusion with overlapping concepts like the provision event, where something is published or manufactured or whatever, where you really don’t want or need to go much beyond date/time/place.


You could then have bf:Event be the range of bf:subject.




Nate Trail


LA308, Mail Stop 4402

Library of Congress

Washington DC 20540




From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Steven Folsom
Sent: Monday, December 08, 2014 9:34 PM
To: [log in to unmask]
Subject: Re: [BIBFRAME] bf:event


The expected value of a bf:event is a bf:Event, Because bf:Event is a subclass of resource, it seems that there’s the ability to have AAP’s, labels, etc. 


The part I’m having trouble with is that the expected value of a bf:subject is a bf:Work or bf:Authority… which reads to me like a bf:Event cannot be the value of a bf:subject. Will we need two bf:resources for events, one as the event (bf:event), one for the event as subject (bf:Topic? or bf:Agent?)… ?





From: Simon Spero <[log in to unmask]>
Reply-To: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
Date: Monday, December 8, 2014 at 5:24 PM
To: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
Subject: Re: [BIBFRAME] bf:event


On Mon, Dec 8, 2014 at 4:33 PM, J. McRee Elrod <[log in to unmask]> wrote:

Steven said:

>In MARC terms it would be consistent with a 650 field where the work is about an "Event".

More often we find an event related subject heading is 610 (e.g. a corporate annual meeting, a symphony orchestra concert), 611 (e.g. a conference), or 600 ( exhibition or concert by a single artist), than a 650 topic.


Notice that those headings are primarily related to works created as an intended outcome of the event.  


Contrast that with the examples I used (*): 



<datafield tag="150" ind1=" " ind2=" ">

 <subfield code="a">Stonewall Riots, New York, N.Y., 1969</subfield>



* The bombing of Hiroshima does not have a non composite topical heading, so I will go the other way, to the bombing of Pearl Harbor. 


<datafield tag="150" ind1=" " ind2=" ">

<subfield code="a">Pearl Harbor (Hawaii), Attack on, 1941</subfield>


Karen Coyle
[log in to unmask]
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600