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

BIBFRAME December 2017

Subject:

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

From:

Osma Suominen <[log in to unmask]>

Reply-To:

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

Date:

Thu, 21 Dec 2017 17:51:42 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (37 lines)

Hi Joe!

Joseph Kiegel kirjoitti 19.12.2017 klo 19:54:
> I think, broadly, there are two separate cases: cataloging data created natively in BIBFRAME, and cataloging data converted from MARC records. I would argue that standards and practices for language tags should be developed based on the needs and possibilities of native BIBFRAME. Once these are established, they can be simplified to what is possible for converted MARC records, since MARC provides relatively little explicit information about the language content of records.

Excellent point. I agree completely that the native BIBFRAME cataloging
use case should drive the specification. With conversion there may be
limitations to what sort of language information can be inferred from
MARC records, but that shouldn't hold back BIBFRAME itself.

In my experience, problematic situations arise when a MARC record
describes a multilingual publication, with several main languages and
titles in different languages. Then it can be impossible to infer which
title is in which language.

> In native BIBFRAME, why wouldn't we want a language tag for every language string? If that seems too much, we certainly want language tags when the same string appears in multiple manifestations, e.g. original script and romanization. Tagging both clearly will be essential for accurate searching, display, etc.

Agreed. Best practice in the RDF world is to use language tags for all
strings that are in some respect natural language. So this includes
things like titles, descriptions, names of people (with some caveats),
organizations such as publishers etc. In contrast, language-agnostic
data such as plain numbers which represent just that number (not a title
like "1984") should not be tagged with language tags, but may be tagged
with a more specific data type such as xsd:integer or xsd:year.

-Osma

--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
[log in to unmask]
http://www.nationallibrary.fi

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 2022
June 2022
May 2022
April 2022
March 2022
February 2022
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