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 2016

BIBFRAME July 2016

Subject:

Re: Name authorities in BIBFRAME?

From:

"Denenberg, Ray" <[log in to unmask]>

Reply-To:

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

Date:

Wed, 20 Jul 2016 14:52:17 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Jane - yes, in your example ...

    rdfs:label "Allen, Paula Gunn" ;
    rdfs:label "Paula Gunn Allen, Native American writer" ;
    bf:agent lcnaf:n81139185 ;
    bf:agent wd:Q435902 .

... where there are two labels and two links supplied you cannot readily associated a label with the link that it corresponds to.  If you need to associate them, you would have to follow the links.  (Or just one link; if you associate one label with one of the links you can probably assume that the other label is associated with the other link.)

Ray



> -----Original Message-----
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Jane Sandberg
> Sent: Tuesday, July 19, 2016 2:41 PM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] Name authorities in BIBFRAME?
> 
> 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.)
> >
> > Ray
> >
> >> 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.
> >>
> >> Appreciatively,
> >>
> >>  -Jane
> >>
> >> @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 ;
> >>    foaf:homepage
> >> <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
> 
> 
> 
> --
> Jane Sandberg
> Electronic Resources Librarian
> Linn-Benton Community College
> [log in to unmask] / 541-917-4655

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

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