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  July 2013

BIBFRAME July 2013

Subject:

Proposal for Bibframe bibliographic strings (Re: supplied information, in transcribed elements)

From:

Jörg Prante <[log in to unmask]>

Reply-To:

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

Date:

Fri, 5 Jul 2013 19:13:55 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (217 lines)

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:

http://www.w3.org/International/articles/language-tags/#extension

(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).

Examples:

"¬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

where

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 
transliteration

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

etc.

Best regards,

Jörg

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 (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] <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]>  http://kcoyle.net
>>     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 www.bl.uk
>>     <http://www.bl.uk/>
>>     The British Library’s latest Annual Report and Accounts :
>>     www.bl.uk/aboutus/annrep/index.html
>>     <http://www.bl.uk/aboutus/annrep/index.html>
>>     Help the British Library conserve the world's knowledge. Adopt a
>>     Book. www.bl.uk/adoptabook <http://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] <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]>  http://kcoyle.net
>     ph:1-510-540-7596  <tel:1-510-540-7596>
>     m:1-510-435-8234  <tel:1-510-435-8234>
>     skype: kcoylenet
>
>

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

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