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

BIBFRAME September 2013

Subject:

Re: BIBFRAME Annotation Model Draft 2

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Thu, 19 Sep 2013 18:36:23 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (60 lines)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 19.09.2013 17:42, schrieb Ford, Kevin:
> Dear Juha,

> About your first paragraph:
>> If multiple instances of different works have been bound together into
>> a single book, they all share the same item record in our present
>> bibliographic database....

> -- Not only does this represent something for a test case but the paragraph
> represents a use case. The question I see is: Is it possible to take BIBFRAME
> holding/item data and parse it into your current system's framework. I'm not
> going to say this would be a requirement (I've not been keen to restrict
> ourselves to what is possible today versus what is possible in the future) but
> it is worth considering. It is worth noting that a Holding resource would have a
> relationship with an Instance, not a Work. You mentioned "work" repeatedly, so
> there may be a misunderstanding there.

The more general question appears to be one about the appropiate place
for this situation in the bibframe model (and I don't think that FRBR
will ever have an answer for this):

Several prints have been individually bound together at some distant
time in the past. Not only for "holdings" purposes of the /item/ but
also for recording provenance information or describing the physical
and artistic features of the binding this is to be considered as one
physical /object/ of high cultural interest (worth "catalogueing" in
its own right).

Thus the compound object itself should be represented by more than a mere
BF annotation, but considering it as a BF instance there is the
requirement to denote exactly one corresponding BF work. Such a
retrospectively construed "work" from singular aggregation of individual
instances is very counter-intuitive (and definitely not a "creative"
work) and furthermore provoces the question of the exact kind of relation
between this "compound work" and its individual constituent works
(those, whose instances had been bound together) and how to model it.

This might become easier to grasp, when general objects (collection items)
are dealt with by Bibframe: They often have physical components but
must not be decomposed, dissasembled, partially summoned in reality.
(Or cannot, if you consider a scratchbook with individual works on
recto and verso of a certain page).


viele Gruesse
Thomas Berger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iJwEAQECAAYFAlI7KAcACgkQYhMlmJ6W47NU/AP/WPYoAIXMWt8oSo3gUNwsMPLB
qyGhzhmAxkvkaQoHyP/6LinT9l8h4QpM/zizia03tvNB37qHfbWi/0QzkgamvrNp
2jwI17WrsBInswOkdqLja3XRPAl0AeRQVA7qLSAcA1EoLNaukwPd3AuGF2UDPZp/
VusUc8P6cyoCd+dMEv8=
=vZ6J
-----END PGP SIGNATURE-----

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

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