For promoting international library catalog rule usage in Bibframe 
strings, I'd like to propose using W3C language tag extensions.

More info about W3C language tag extensions and private-use subtags:

(I would like to remind that string handling of bibliographic strings is 
fundamental in order to apply the correct filing/sorting order, and it 
is useful for building collations, which has been discussed some time ago).

As a consequence, special characters like [, ], ¬ or others could be 
interpreted automatically by semantic processors, because RDF natively 
support W3C language tags in literals.

Because bibliographic rules are commonly applied only within a certain 
country/language area, the language in the tag could indicate the scope 
where the string is valid or targeted for (not necessarily the language 
of the string itself because more than one language can be involved, 
like in transliterations).


"¬Der¬ Process"@de-DE-x-rak
"<u088>The <u0089>Process"@en-US-x-aacr
"Aleksandr Pushkin"@en-US-x-aacr-transliteration
"Aleksandr Sergeevič Puškin"@x-iso-9
"Malcolm Pasley [Hrsg.]"@de-DE-x-rak


de-DE-x-rak --> this bibliographic string originates from german catalog 
rules (RAK)
en-US-x-aacr --> this bibliographic string originates from US catalog 
rules (AACR)
en-US-x-aacr-transliteration --> this bibliographic string originates 
from US catalog transliteration rules (AACR)
x-iso-9 --> this bibliographic string was created using ISO-9 rules for 

Similar codes could be applied to transcribed, recorded, or supplied 


Best regards,


Am 05.07.13 18:08, schrieb Diane Hillmann:
> Karen, et al.:
> I like where this is going.  To me it has a lot of traction in a world 
> where data comes in from multiple sources and decisions need to be 
> made about which are more 'golden'.  It might also be useful as be 
> start to improve data, to exclude transcribed data from certain kinds 
> of transactions, for instance.
> This is not to say that we could expect the outside world to use 
> something like this if they don't find it useful, but within 
> libraries, particularly as we integrate legacy and prospective data, 
> it could be quite helpful.
> Diane
> On Fri, Jul 5, 2013 at 11:40 AM, Karen Coyle <[log in to unmask] 
> <mailto:[log in to unmask]>> wrote:
>     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 (, 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] <mailto:[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:
>>>     <!--[if !supportLists]-->·<!--[endif]-->By means of a note (see
>>>     2.20)
>>>     <!--[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 <tel:203.432.9672> [log in to unmask]
>>>     <mailto:[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]
>>>     <mailto:[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]  <mailto:[log in to unmask]>
>>     ph:1-510-540-7596  <tel:1-510-540-7596>
>>     m:1-510-435-8234  <tel:1-510-435-8234>
>>     skype: kcoylenet
>>     **************************************************************************
>>     Experience the British Library online at
>>     <>
>>     The British Library’s latest Annual Report and Accounts :
>>     <>
>>     Help the British Library conserve the world's knowledge. Adopt a
>>     Book. <>
>>     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] <mailto:[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]  <mailto:[log in to unmask]>
>     ph:1-510-540-7596  <tel:1-510-540-7596>
>     m:1-510-435-8234  <tel:1-510-435-8234>
>     skype: kcoylenet