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: BIBFRAME relationship indicators & coding

From:

"Mark K. Ehlert" <[log in to unmask]>

Reply-To:

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

Date:

Fri, 30 Nov 2012 02:16:02 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (103 lines)

J. McRee Elrod <[log in to unmask]> wrote:
> Mark said:
>
>>There is no such designator in RDA.  It's "composer (expression)," which I
>>believe you export to your clients as simply "composer".
>
> It is in the registry:
>
> http://metadataregistry.org/schemaprop/show/id/2209.html
 ...
> It is also in the version of RDA to which I have access at 18.5.1.3:
>
> "For Example:
>    film producer
>    film director
>    actor
>    composer of music for sound film"
>
 ...
> Perhaps you looked in the wrong list?

No, I looked in the correct list--the current version of RDA's
Appendix I.  The "composer of music for sound film" designation
appeared in the November 2008 draft of RDA, but it was wiped out with
a number of other terms to form the current Appendix I list first
pushed out with the initial June 2010 publication of RDA.  The
examples in Chapter 18 were revised too.

I see that term is still classed as "new-proposed" at the Metadata
Registry.  Don't know if that means anything in this context.

> One list in alphabetic order
> would be much easier, perhaps coded for use with one or more of WEMI?

I've already made a single alphabetical list with WEMI labels, to use
as a cheat-sheet.

>>If the intent is to use URIs to describe relationships currently depicted
>>by our current use of MARC relator codes ...
>
> The URIs lead to terms in English.  The $4 MARC codes can be exported
> in any language.

The RDA relationship designators and other controlled terms are also
"codes."  They're given as English words in the text, but can be
represented using URIs that can point to multiple language labels for
the same concept.  For instance, a number of the RDA terms at the
Metadata Registry are available in both English and German, e.g.,
<http://metadataregistry.org/schemaprop/show/id/374.html>.   Though
pointing at the same thing via a URI, an English catalog can be set up
to display the English label, and the German catalog set up to display
the German label.  Or perhaps even set up to prefer certain words over
others in a particular language.

To your point about id.loc.gov, maybe LC and/or another group can work
to develop sanctioned translation-synonyms for the MARC relator and
other codes.

> So much of RDA and Bibframe is Anglocentric.

Can't speak to the BIBFRAME since the coding part hasn't come up yet
aside from references to or examples in RDF/XML and Turtle.

But RDA?  Yes, it is Anglocentric, certainly with regard to its
vocabularies--it's directed at an English-speaking audience.  Will
those vocabularies still be Anglocentric when RDA gets translated into
Spanish?  And German?  And French?

Furthermore, will the RDA term "maps" *mean* the same thing with each
language?  Likely.  Will that term be *represented* in the same way in
each translation and in their respective bib records and catalogs?
Likely no.  English "maps" = German "Karten" = French "cartes".  Using
potentially the same URI.  But we're still a long way from making this
happen in a typical library catalog.

> I wonder if our Quebec,
> European, and Asian clients would accept Bibframe XML markup in
> English?

Are they reading the mark-up?  Or is the computer reading the mark-up
and presenting it in a familiar form on the screen?  Compare reading
"raw" MARC to reading formatted MARC.  Or reading HTML code versus
viewing the content of a web page.

If it's an issue, XML isn't limited to tags containing roman
characters.  Not sure about Turtle or other methods of markup.

> They would certainaly not accept English inclusions in
> records for non English resources.

Understandable.  It interferes with the parts of the record that
should be read by the public--the spelled out bits.  But do they balk
at the quasi-English MARC codes "lat" and "ger" and "fre" and "eng",
for instance?

-- 
Mark K. Ehlert                 Minitex
Coordinator                    University of Minnesota
Digitization, Cataloging &     15 Andersen Library
  Metadata Education (DCME)    222 21st Avenue South
Phone: 612-624-0805            Minneapolis, MN 55455-0439
<http://www.minitex.umn.edu/>

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

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