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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  November 2011

BIBFRAME November 2011

Subject:

Re: Introduction (@W3C)

From:

"Riley, Charles" <[log in to unmask]>

Reply-To:

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

Date:

Sun, 13 Nov 2011 02:56:10 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (49 lines)

Thanks Rebecca! Very helpful, I was not aware that we could already use that coding directly in records.

Charles


________________________________________
From: Bibliographic Framework Transition Initiative Forum [[log in to unmask]] on behalf of Rebecca Guenther [[log in to unmask]]
Sent: Saturday, November 12, 2011 11:49 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] Introduction (@W3C)

The discussion about ISO 639-2 vs ISO 639-3 is a side topic of this thread-- but I wanted to respond to this comment about having 639-3 as an option for the cataloger. It is already available and can be used in MARC in field 041, specifying in subfield $2 the source of the language code as iso639-3.

Rebecca Guenther
(formerly chair of ISO 639 Joint Advisory Committee and Library of Congress)

On Wed, Nov 9, 2011 at 9:56 PM, Riley, Charles <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Thanks, Tom; sorry to have been less than fully precise on referring to MARC-8. I just meant that in the sense that it covers a range of characters that is far less than what is found in Unicode. Agreed on 15924.

I would definitely like to see 639-3 come through at least as an option for the cataloger. Some of the codes in 639-2/B are essentially nothing more than catchall categories, allowing for no granularity in distinguishing between a few hundred languages that share the same fixed field code.


________________________________________
From: Bibliographic Framework Transition Initiative Forum [[log in to unmask]<mailto:[log in to unmask]>] on behalf of Tom Emerson [[log in to unmask]<mailto:[log in to unmask]>]
Sent: Wednesday, November 09, 2011 4:31 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [BIBFRAME] Introduction (@W3C)

On Nov 9, 2011, at 3:39 PM, Riley, Charles wrote:
> Bibliographic data is largely built on the MARC-8 character set, in essence a subset of UTF-8; thus a loss of data for the preponderance of materials in non-Latin scripts has already occurred by the time data becomes bibliographic.

I don't think MARC-8 is properly a "subset" of UTF-8: I'm not sure what that means. MARC-8, as I understand, is more similar to ISO-2022 where you can switch between multiple character sets within a single text stream. UTF-8 is an encoding form of Unicode: a different beast entirely.

I would hope that Unicode would be used for any future bibliographic representation: the choice of encoding then depends on the particular serialization format used. There is little we can do if the original data has been lost, but having the foundation to represent the world's current and historical scripts is a vital requirement, and Unicode fits the bill here.

In addition to specifying language (whether ISO 639-2/B or 639-3 I don't have a preference) we should also consider specifying script details. ISO 15924 works well for this, e.g., to distinguish a title in Simplified Chinese vs. one in Traditional.

   -tree

P.S. All opinions are my own and do not necessarily represent my employer.

Tom Emerson
Principal Software Engineer --- Search
EBSCO Publishing
10 Estes Street
Ipswich, MA 01938, USA
Phone: +1-978-356-6500 x2185<tel:%2B1-978-356-6500%20x2185>
[log in to unmask]<mailto:[log in to unmask]>

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

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