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  August 2014

BIBFRAME August 2014

Subject:

AV Modeling Study

From:

Philip Schreur <[log in to unmask]>

Reply-To:

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

Date:

Fri, 8 Aug 2014 09:35:51 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (56 lines)

Thanks for this excellent paper.  Our BIBFRAME group at Stanford 
discussed it yesterday.  We had quite a lengthy discussion and I'm 
hoping others will send in their comments as well, we all had different 
perspectives.

We all agreed that elevating the concept of Event in BIBFRAME is 
needed.  Up until now, the focus has been on the conversion of MARC to 
BIBFRAME for more traditional library resources.  As we move beyond them 
into more complex media and resources that we have never attempted to 
"catalog" before, the concept of event becomes more and more important.  
It also brings BIBFRAME in line with other models such as EDM that allow 
for an object-centric or event-centric approach.  My own comments are on 
broader issues.

bf:Content -  A fascinating concept but I have to admit I hate the name, 
lol.  Content is a very loaded term.  At first I wondered if bf:Content 
was meant merely to be a shell for joining bf:Work and bf:Event and 
linking to bf:Instance.   I see this isn't true, though.  On p. 42: By 
allowing these properties to be used with bf:Content, catalogers can 
describe the original intention/characteristics of the content, even if 
that is quite different from the characteristics of an instance in the 
collection." This thought certainly resonated with me.  I'm still 
frustrated by the inability of linking a bf:Work to an authority 
although I understand the reason.  If you consider the authority as 
representing the work itself, not just a controlled string for it, it is 
the natural home for "the original intention/characteristics of the 
content."  Maybe bf:Content could serve this purpose as well?

bf:Instance - This may be my misunderstanding, but I have undestood that 
each bf:Work in a resource does not have it's own bf:Instance, there is 
only one for the resource as a whole.  I still struggle with this a 
bit.  Although I'm not sure the paper recommends this, it does seem to 
articulate cases in which it would be valuable to record separate 
instance data for different parts of a collective resource.

BIBFRAME extensions - I think the paper highlights the need to extend 
BIBFRAME to cover various types of resources.  I disagree slightly with 
the technique, though.  I'd prefer seeing the BIBFRAME vocabulary remain 
as simple as possible and, when extensions are needed, to make use of 
other established vocabularies as opposed to incorporating them as part 
of the BIBFRAME vocabulary.  If they were absorbed, the resultant 
behemoth would soon become impossible to manage and keep in synch with 
whatever vocabulary it was derived from.

Sequences - Another critical concept difficult to express in BIBFRAME.  
I agree that this is an area that needs to be resolved in general.

Philip

-- 
Philip E. Schreur
Head, Metadata Department
Stanford University
650-723-2454
650-725-1120 (fax)

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