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

BIBFRAME December 2017

Subject:

Re: CC:AAM Statement in Support of the Internationalization of BIBFRAME

From:

Jennifer Martin <[log in to unmask]>

Reply-To:

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

Date:

Tue, 19 Dec 2017 16:15:40 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Regarding "the language of the catalog" (or "language of cataloging"), under MARC, it is encoded in 040 $b (field 040 subfield b). So it is currently coded in most libraries' metadata. The language of cataloging matters when dealing with strings supplied by the cataloger (as opposed to transcribed from the resource); for example, "172 pages" makes sense to an English speaker, but "172面" or "172 stran", not so much.

-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Karen Coyle
Sent: Tuesday, December 19, 2017 9:32 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] CC:AAM Statement in Support of the Internationalization of BIBFRAME

On 12/17/17 3:56 PM, Andrew Cunningham wrote:
> Karen,
> 
> language taging is complex. In the first instance there is the 
> language of the object/resource being describe.

Yes, which is why I suggested that the language tagged is limited to the language of the resource.

> 
> Then there is the language used in the BIBFRAME doc, which may not be 
> the same as the language of the object being described.

We generally refer to this as "the language of the catalog." That isn't coded in our metadata, AFAIK, although I wonder if CanMARC covered that, since they often produce both an English-catalog and a French-catalog version. Anyone?

> 
> Some strings may also be in language of the object, in script and in 
> romanisation.
> 
> Depending on the userver of the BIBFRAME document all the above need 
> to be included.
> 
> For instance an institution that is displaying daat in a Web interface 
> and need to meet accessibility requirements will need to mark up all 
> changes in language.
> 
> Identifying lanGuage of strings may affect browers choice of language 
> or what localised features are applied during rendering.
> 
> For instance in most library catalogue language markup is non existent.
> So Traditional Chinese text will be displayed by either a Japanese 
> font or a simplified Chinese font. Browsers will never use a 
> traditional Chinese font if language markup is not present.

Do browsers have markup within the page for this? I'm aware of the head language encoding, but not of individual elements in the page. I guess that CSS may add something - I'm not up with everything you can do today. However, there is a big problem with trying to attribute
*language* to fields in bibliographic data. It only takes a few examples to understand why:

Title:
1984 (book in German)
1984 (book in Hebrew)
1984 (book in English)

Title:
Marie Antoinette (book in English)
Marie Antoinette (book in Swedish)

Author:
Wong, Mario (a real name, altho not an author)

If special exceptions are need for the unified ideograms, then I see that as an exception that affects display, not a general declaration of the language of strings.

kc


> 
> Most if not all library catalogues fail to meet what I would consider 
> minimum Web internationalization standards.
> 
> This is partly due to limitations in MARC itself and how it is used.
> BIBFRAME needs a robust internationalization model other wise its 
> usefullness will be limited in the wider context of the Internet.
> 
> Andrew
> 
> On 15 Dec 2017 02:12, "Karen Coyle" <[log in to unmask] 
> <mailto:[log in to unmask]>> wrote:
> 
>     It is very important to consider internationalization early on the life
>     of a standard, so this is an important effort.
> 
>     I noticed what appears to be a confusion (which it may be only in the
>     wording) in the section on language tags. BCP47 is defined as "(Internet
>     Best Current Practice for the use of language tags in cases where it is
>     desirable to indicate the language used in an information object)." The
>     next paragraph refers to "romanized fields". I interpret BCP47's
>     "information object" to be the object that is described by the metadata,
>     not the metadata itself, although it could presumably be used for
>     either. However, defining the language of individual metadata fields is
>     fraught, and I don't think you are suggesting that. It would be good to
>     be clear (if this is what you mean) that language codes are defined for
>     described resources, and that only transliteration is coded for metadata
>     fields.
> 
>     kc
> 
>     On 12/13/17 12:30 PM, Robert J. Rendall wrote:
>     > Colleagues -
>     >
>     > The ALA/ALCTS Committee on Cataloging: Asian and African Materials
>     > (CC:AAM) has voted to approve a Statement in Support of the
>     > Internationalization of BIBFRAME, containing recommendations on
>     > character encoding, the representation of original script and
>     > romanization, normalization, and language tags:
>     >
>     > http://connect.ala.org/node/271553
>     <http://connect.ala.org/node/271553>
>     >
>     > Robert Rendall
>     > Chair, CC:AAM 2017-2018
>     > http://www.ala.org/alcts/mgrps/camms/cmtes/ats-ccscataa
>     <http://www.ala.org/alcts/mgrps/camms/cmtes/ats-ccscataa>
>     >
>     > Robert Rendall
>     > Principal Serials Cataloger
>     > Original and Special Materials Cataloging, Columbia University
>     Libraries
>     > 102 Butler Library, 535 West 114th Street, New York, NY 10027
>     > tel.: 212 851 2449 <tel:212%20851%202449>  fax: 212 854 5167
>     <tel:212%20854%205167>
> 
>     --
>     Karen Coyle
>     [log in to unmask] <mailto:[log in to unmask]> http://kcoyle.net
>     m: +1-510-435-8234 <tel:%2B1-510-435-8234>
>     skype: kcoylenet/+1-510-984-3600 <tel:%2B1-510-984-3600>
> 
> 
> 
> --
> Andrew Cunningham
> [log in to unmask] <mailto:[log in to unmask]>
> 

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600

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 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
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