There are (at least) four different things that Jorg addressed. Perhaps it would be better to look at them separately so as not to develop any confusion between them.

1) Language - coding by language is part of the RDF core standard. However, years ago a committee was looking into coding MARC data by language and essentially failed because the cataloging rules are not strictly language-dependent, and there are many strings in a bibliographic record for which the language isn't terribly relevent. For example, a book in German with the title "Marie Antoinette" the title string is not really either in German nor necessarily in French. The fields that could be tagged would be those that reflect the language of cataloging (250, 300, etc.), and perhaps subject headings. For proper names, language becomes quite complex, such as a name of Chinese origin where the person works in the West and prefers the Western name order.

2) Cataloging rules - this is covered in the FRAD standard: each access point should be coded by rule base. As I recall, this is "AACR2" not "AACR2 section 17.2.B3"

3) Transliteration - it would be nice to have the transliteration rules along with the transliteration, and to know that a string is a transliteration. I don't know if " en-US-x-aacr-transliteration" covers this, but know very little about transliteration. I do know that we moved from Wade-Giles to Pinyin in my lifetime, and I don't think those could be covered by "aacr-transliteration".

4) Supplied/transcribed/recorded - as suggested by Alan Danskin.

One would need to think of the interplay between these (e.g. could a transliteration be transcribed? or is it always supplied?).

kc


On 8/15/13 6:00 AM, Ford, Kevin wrote:
[log in to unmask]" type="cite">
Dear Francis,

Yes, specifying whether data in a given element is recorded or transcribed (or a one or two other designations) is necessary, is certainly within the scope of BIBFRAME, and will have to be accommodated.

In fact, one of the proposed solutions to this issue, posted on this listserv, made its way into the very recently published Use Cases and Requirements document.  See 5.3 under section 5 at 

http://bibframe.org/documentation/bibframe-usecases/#openissues

We still need to work up a few use cases to support the proposal as well as explore the full scope of what's needed, but do consider this a start.

Did the community have further thoughts about Jörg's proposal? [1]

Yours,
Kevin

[1] http://listserv.loc.gov/cgi-bin/wa?A2=ind1307&L=BIBFRAME&P=R4335&I=-3&X=2845C01B99123B796B


--
Kevin Ford
Network Development and MARC Standards Office
Library of Congress
Washington, DC


-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum
[mailto:[log in to unmask]] On Behalf Of Lapka, Francis
Sent: Wednesday, August 14, 2013 8:42 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] supplied information, in transcribed elements

In July, I posted to the present list to ask if there were any plans to
introduce a mechanism in BIBFRAME that would allow us to specify
whether the data in a given element is recorded or transcribed. While
the ensuing discussion was quite interesting, we never received a
response from anyone directly involved in BIBFRAME development.

May I ask the same question again, with the hopes that someone involved
with BIBFRAME may assert whether or not such a feature would be within
the scope of BIBFRAME development?

Thanks,
Francis






From: Bibliographic Framework Transition Initiative Forum
[mailto:[log in to unmask]] On Behalf Of Karen Coyle
Sent: Friday, July 05, 2013 11:41 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] supplied information, in transcribed elements

Alan,

Thanks. Then we'd need a use case for distinguishing between recorded
and transcribed, or between recorded and supplied, which we do not
separately code today. The only "coded" source is "supplied." I suspect
that in many current catalog records it is not possible to know if
certain elements are recorded or are transcribed, right? It seems to be
an assumption made based on the nature of the data element (e.g.
publisher).

I'd suggest that transliteration be noted similar to language, using a
code on the element. It would be ideal to know WHICH transliteration
was used, but I don't think our data can supply that.

kc
On 7/5/13 8:13 AM, Danskin, Alan wrote:
Karen,

Information in the resource may be recorded without being transcribed,
for example date of publication (2.8.6.3), copyright date, extent.
There are at least three categories:

transcribed
recorded
supplied

some information may also be transliterated, so that may be a fourth
category.

Alan
________________________________________
From: Bibliographic Framework Transition Initiative Forum
[mailto:[log in to unmask]] On Behalf Of Karen Coyle
Sent: 05 July 2013 15:44
To: [log in to unmask]
Subject: Re: [BIBFRAME] supplied information, in transcribed elements
Francis, et al,

I've been wondering if we shouldn't reverse the markup, and indicate
which elements are precisely transcribed. In effect, everything else is
supplied.

kc
On 7/3/13 9:36 AM, Lapka, Francis wrote:
RDA 2.2.4, Other Sources of Information, notes:
When instructions specify transcription, indicate that the information
is supplied from a source outside the resource itself:
1. <!--[if !supportLists]--><!--[endif]-->By means of a note (see 2.20)
2. <!--[if !supportLists]--><!--[endif]-->Or by some other means (e.g.,
through coding or the use of square brackets).
If encoding RDA in MARC, square brackets appear to be the only option
for “some other means.”  In the development of BIBFRAME, are there
plans to enable an encoding to indicate that information has been
supplied?
MODS has already developed this attribute. See, for example, the
titleInfo element, for which the “supplied” attribute is defined as
follows:
Definition
An indication that the title information did not come from the resource
itself.
Application
This attribute is used as supplied="yes" when the title information has
been supplied from an external source, not from the resource.
MODS also defines the “supplied” attribute for originInfo/place,
originInfo/publisher, originInfo/edition, and
physicalDescription/extent.
Something equivalent in BIBFRAME might be useful for encoding any RDA
transcribed element (as listed in RDA 2.2.4).
Francis
_________________________________
Francis Lapka, Catalog Librarian
Yale Center for British Art, Department of Rare Books and Manuscripts
1080 Chapel Street, PO Box 208280, New Haven, CT  06520
203.432.9672    [log in to unmask]
Please note:  the Study Room will be closed from June 4 through August
30, 2013, due to the Center’s refurbishment project.  After September 3,
access will be limited and by appointment only. Requests for materials
from Prints and Drawings and Rare Books and Manuscripts should be made
at least two weeks in advance by e-mailing [log in to unmask]. It is
expected that normal services in the Study Room will resume in early
January.

--
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet
***********************************************************************
***
Experience the British Library online at www.bl.uk

The British Library’s latest Annual Report and Accounts :
www.bl.uk/aboutus/annrep/index.html

Help the British Library conserve the world's knowledge. Adopt a Book.
www.bl.uk/adoptabook

The Library's St Pancras site is WiFi - enabled

***********************************************************************
**

The information contained in this e-mail is confidential and may be
legally privileged. It is intended for the addressee(s) only. If you
are not the intended recipient, please delete this e-mail and notify
the [log in to unmask] : The contents of this e-mail must not be
disclosed or copied without the sender's consent.

The statements and opinions expressed in this message are those of the
author and do not necessarily reflect those of the British Library. The
British Library does not take any responsibility for the views of the
author.

***********************************************************************
**
 Think before you print

--
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet