Print

Print


Another quick comment.

Section 2.4 discusses the "RDA emphasis on Transcription" and makes the point that the information about the transcription vs any 'authority' could be recorded in the BIBFRAME Authority entity. In section 3 the document goes on to say

"As for including places of publication, publishers, and the like as types of BIBFRAME Authorities, it is easy to see the benefit of associating the entries with some form of controlled, traditional authority.  The lightweight Abstraction Layer provides an elegant way to associate controlled information (authorized labels and URIs) with such an entity and capture transcribed information.  

Alternate solutions are available.  For example, two properties could be created, both of which, in the current example of a publisher, would be associated with an instance: "publisher" and "transcribedPublisher."


I feel that conflating the BIBFRAME Authority and Transcription properties is a mistake - mainly because there are transcribed elements that do not currently fall into the concept of BIBFRAME Authority (and probably have no place there). e.g. Date of Publication.

It feels like a stronger case could be made for a separate class for transcribed values - which could contain the properties the documents mentions in relation to transcribed elements, and that this transcribed data class could then point (but only where appropriate) to a BIBFRAME Authority. So rather than:

<!--  BIBFRAME Instance -->
<HardCoverBook id = "http://bibframe/inst/frbr-1997-09-01:0">
      <date>1998</date>
      <isbn>359811382X</isbn>
      <publisher resource="http://bibframe/auth/org/k.g.saur" /> 
</HardCoverBook>
<!--  BIBFRAME Authority -->
<Organization id="http://bibframe/auth/org/k.g.saur">
      <label>K.G. Saur</label>
      <hasIDLink resource="http://id.loc.gov/authorities/names/nr91037301" />
      <hasVIAFLink resource="http://viaf.org/viaf/125770969" />
      <hasDNBLink resource="http://d-nb.info/gnd/4020140-5" />
</Organization>
We would have (really rough example - but hopefully you get the idea):

<!--  BIBFRAME Instance -->
      <date>1998</date>
      <isbn>359811382X</isbn>
      <publisher resource="http://bibframe/transcription/123" /> 
</HardCoverBook>
<!--  BIBFRAME Transcription -->
<Transcription id="http://bibfram/transcription/123">
<transcribedValue>K.G. Saur</transcribedValue>
<hasBIBFRAMEAuthorityLink resource="http://bibframe/auth/org/k.g.saur">
<!--  BIBFRAME Authority -->
<Organization id="http://bibframe/auth/org/k.g.saur">
<label>K.G. Saur</label>
<hasIDLink resource="http://id.loc.gov/authorities/names/nr91037301" />
<hasVIAFLink resource="http://viaf.org/viaf/125770969" />
<hasDNBLink resource="http://d-nb.info/gnd/4020140-5" />
</Organization>

I don't think this weakens the arguments around the need for a BIBFRAME Authority entity as laid out in the document, and would mean that transcribed elements (which to be honest are often problematic for those non-library world people consuming library data) were clearly modelled and dealt with consistently.

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com
Email: [log in to unmask]
Telephone: 0121 288 6936

On 10 May 2013, at 22:38, "McCallum, Sally" <[log in to unmask]> wrote:

Here is another part of the BIBFRAME pie to stimulate discussion and questions for the community to consider, On BIBFRAME Authority.  This issue paper concerns the Authorities concept in the BIBFRAME model paper.   This paper clarifies what the model document says about the Authority part of the model and invites discussion.
 
 
Again it is helpful if when discussing this paper, you name your listserv comment with the topic  plus  an extra title to bind threads, e.g., "authority--main point". 
 
Looking forward to your comments,  Sally
 
 
**************************
Sally H. McCallum
Chief, Network Development and Standards Office
Library of Congress,  101 Independence Ave., SE
Washington, DC 20540  USA
Tel. 1-202-707-5119 -- Fax 1-202-707-0115
**************************