Thanks for your helpful response, Ray!
What happens if two authority sources offer different labels for a
person? For example, in the following example, LCNAF refers to a
person as "Allen, Paula Gunn", while wikidata refers to her as "Paula
Gunn Allen, Native American writer". However, it's impossible to tell
which name authority provided which label.
Is there a cool way to do this? Or have BIBFRAME designers decided
that this it is not important to preserve these data? Granted, I
can't necessarily think of a specific use case for recording the
providers of specific authorized labels, but it just seems like
something that'd be nice to have (and something that MARC includes in
the second indicator or $2 of many fields, such as the 600 field).
@prefix bf: <http://bibframe.org/vocab/>
@prefix lcnaf: <http://id.loc.gov/authorities/names/>
@prefix rel: <http://id.loc.gov/vocabulary/relators/>
@prefix wd: <https://www.wikidata.org/wiki/>
_:article a bf:Work;
bf:contributor _:author .
_:author a bf:Contribution;
bf:role rel:aut ;
rdfs:label "Allen, Paula Gunn" ;
rdfs:label "Paula Gunn Allen, Native American writer" ;
bf:agent lcnaf:n81139185 ;
bf:agent wd:Q435902 .
On Mon, Jul 11, 2016 at 4:21 PM, Ray Denenberg <[log in to unmask]> wrote:
> Hi Jane -
> bf:authorityAssigner from 1.0 is generalized in 2.0. to bf:assigner.
> referenceAuthority. Yes, in 1.0 the idea was to be able to designate a principal authority and to distinguish it from one or more secondary authorities. In 2.0 the concept of a principal is discarded. Instead, you can supply multiple agents within a single contribution. (The obvious question is, if you supply two agents for, let’s say author, how do you know whether there are two authors or if they are just different authorities for the same author. The answer is, if there are two authors, supply separate contributions.)
>> On Jul 11, 2016, at 5:49 PM, Jane Sandberg <[log in to unmask]> wrote:
>> Hi everyone,
>> BF1.0 included two properties that don't exist in 2.0 that I am
>> curious about. bf:authorityAssigner was a rdf:Property that connected
>> a bf:Authority to the bf:Agent who had done the work of assigning that
>> authority. bf:referenceAuthority was a rdf:Property that connected a
>> bf:Authority to some other information about the authority -- my
>> understanding was that this refers to some secondary authority.
>> So as I wrap my mind around BF 2.0, I am trying to put together an
>> example that expresses the following:
>> 1) That an author of an article is represented in both LCNAF and ISNI.
>> 2) That I used an author's homepage as a reference to verify the match.
>> 3) That the authority matching work was done by Linn-Benton Community College.
>> How would I do this in BF 2.0? I took a bit of a stab at this below.
>> @prefix bf: <http://bibframe.org/vocab/>
>> @prefix isni: <http://isni.org/isni/>
>> @prefix lcnaf: <http://id.loc.gov/authorities/names/>
>> @prefix rel: <http://id.loc.gov/vocabulary/relators/>
>> _:article a bf:Work;
>> bf:contributor _:author .
>> _:author a bf:Contribution;
>> bf:role rel:aut ;
>> bf:agent lcnaf:no2013089082 .
>> lcnaf:no2013089082 rdfs:label "Lilley, Spencer, 1963-" ;
>> owl:sameAs isni:0000000418419694 ;
>> <http://www.massey.ac.nz/massey/expertise/profile.cfm?stref=334330> .
>> Jane Sandberg
>> Electronic Resources Librarian
>> Linn-Benton Community College
>> [log in to unmask] / 541-917-4655
Electronic Resources Librarian
Linn-Benton Community College
[log in to unmask] / 541-917-4655