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 2014

BIBFRAME July 2014

Subject:

Re: Bibframe and Linked Data (Authorities)

From:

"Ford, Kevin" <[log in to unmask]>

Reply-To:

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

Date:

Wed, 9 Jul 2014 08:12:27 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

> However the definition of a Bibframe Person as it stands is a
> “Controlled personal name”, not a person as such; foaf:Person is defined as
> “A person” which does implicitly suggest that "bf:Person != foaf:Person". 
-- Agreed.  Two things here.  One, I can envision the definition of bf:Person changing (to what, I could not tell you, but the current definition seems narrow to how I think of bf:Person).  Two: while the second point is an intentionally technical point, we want it clear that we've made no such assertion explicit and that to suggest otherwise is to interpret beyond what has been stated at the vocabulary level.  I'm not saying that your assessment of the definitions is unreasonable, but that there is a way to assert (or not) this type of statement at the vocabulary level and we've not done that.

Yours,
Kevin

--
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 Meehan, Thomas
> Sent: Wednesday, July 09, 2014 5:17 AM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] Bibframe and Linked Data (Authorities)
> 
> Hello. I have been reading this and Rob’s initial paper while trying to get to
> grips with what Bibframe authorities are doing, particularly what a Bibframe
> Authority actually is. I confess, for example, that I find the formulation
> “Resource reflecting key authority concepts that have defined relationships
> reflected in the Work and Instance” rather confusing. The response below
> says that ‘Furthermore, nowhere is it ever asserted that "bf:Person !=
> foaf:Person"’. However the definition of a Bibframe Person as it stands is a
> “Controlled personal name”, not a person as such; foaf:Person is defined as
> “A person” which does implicitly suggest that "bf:Person != foaf:Person". I
> recall I think that the original specification of FRAD for instance treated a
> name as a separate entity to a person, although perhaps not quite in this
> sense. Do I have this wrong?
> 
> Thanks,
> 
> Tom
> 
> ---
> 
> Thomas Meehan
> Head of Current Cataloguing
> Library Services
> University College London
> Gower Street
> London WC1E 6BT
> 
> [log in to unmask]
> 
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Denenberg, Ray
> Sent: 08 July 2014 20:23
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] Bibframe and Linked Data
> 
> Following are thoughts from Kevin Ford and me on the Sanderson paper
> cited below, “Differences between BibFrame and other Linked Open Data
> Approaches.”
> 
> We appreciate these issues being raised and the constructive criticism of the
> BIBFRAME approaches discussed. We offer the following observations.
> 
> String Authorities rather than Identifiers BIBFRAME has explicitly stated that
> bf:Authority is not designed to compete with existing library authority efforts
> or replicate traditional library authorities.  Furthermore, nowhere is it ever
> asserted that "bf:Person != foaf:Person" and nowhere is it said that
> "bf:Authority == madsrdf:Authority".  Nothing, either way, is actually
> declared presently.   Rather, bf:Authority  is an abstraction allowing the
> implementer to reference a traditional authority. It is these traditional
> authorities that include the strings in question.  The explicit inclusion of the
> string within a bf:Authority (via property  bf:label or
> bf:authorizedAccessPoint) is not mandated;  it may be optionally included
> when a link to a traditional authority cannot be found, or for the benefit of a
> recipient who may be unable to follow the link.
> These carefully constructed strings allow us to create matches to strings in
> existing MARC records (if we broke them up, we'd have a problem re-
> creating them should we need to), they represent current cataloging practice
> (for better or worse), and they provide us with ready-made labels (and ones
> that the community expects to see in bibliographic data). Reliance on
> fabricated strings will diminish in time, some day they may go away and
> become a relic of 20th century cataloging but it is simply too early for that; for
> now they are imperative.  It will not happen until our reliance on identifiers
> outweighs our need for -  and stakeholders' expectations of - those strings.
> 
> Relationships
> The role of a BIBFRAME Agent with respect to a Work/Instance is expressed
> either by (a) a URI; or (b) a string, when there is no known URI for that role.
> The paper finds fault:
> • In method (a), with  the perceived restriction of role URIs to LC relators.
> • With method (b), in general.
> The first is simply a misperception. There is no such restriction; the URI can
> come from any appropriate role vocabulary. As for “method (b)” it is simply
> impractical to insist that every role have a URI, particularly since during early
> BIBFRAME implementation much of the BIBFRAME data will be converted
> from MARC records.  If a MARC record represents a person’s role as
> “ed.”,  whoever does the conversion might not be able to find an appropriate
> URI for that role. The string should not simply be discarded; it should be
> retained if for no other reason than that a human  end-user might be able to
> make sense of it.
> That said, it is important to note that the primary and expected way to relate
> Works/Instances to Agents in BIBFRAME is method (a) above.   Rob’s paper
> identifies method (a) as the "second way" (and presumably method “b” is
> interpreted to be the primary method).  This may be due to BIBFRAME not
> effectively communicating that method (a) is primary, and that method (b)
> should be used only in extraordinary circumstances.
> 
> 
> Identifiers
> We do believe that identifiers in BIBFRAME could benefit from more thinking.
> As such, we feel that Rob’s section on identifiers may be trying to grapple
> with several different issues, all of which are about identifiers but each of
> which should be treated separately.  These issues are likely legitimate, but
> we need to sort them out. We do want to note, bf:identifierValue  expects a
> string literal, and Rob’s examples appear to treat it as a resource
> identifier.  This is a fairly fundamental misinterpretation that needs to be
> cleared up before we can begin to sort out the other issues.
> 
> Predicate Proliferation
> This section points out that there are perhaps many more properties in
> BIBFRAME than necessary, and many could be eliminated.  This is a legitimate
> concern, and BIBFRAME is and will be undergoing vocabulary refinement,
> informed by the current BIBFRAME testbed activity.
> 
> Record vs.  Graph
> Based on the examples, we believe  this section  draws almost entirely on a
> mistake in the Bibframe vocabulary.  All of the properties mentioned in this
> section are currently associated directly with Work and Instance
> resources.  They should instead have a domain of
> bf:DescriptionAdminInfo   We regret this mistake.
> 
> Model Inconsistency
> The issues raised here do deserve closer inspection. Rob speculates that the
> reason why bf:Event and  bf:Provider  are not of class bf:Authority is because
> there are not library authority lists for events and providers.  That isn’t the
> reason; one has nothing to do with the other.
> Anyway, bf:Event and  bf:Provider are currently undergoing re-thinking.
> 
> 
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Jody L. DeRidder
> Sent: Friday, June 27, 2014 9:26 AM
> To: [log in to unmask]
> Subject: [BIBFRAME] Bibframe and Linked Data
> 
> I just saw this posted on Twitter.
> Rob Sanderson is concerned about the ways in which Bibframe does NOT
> worked in the linked data environment, and is trying to effectively
> communicate the issues.  He's asking for feedback:
> https://docs.google.com/document/d/1yyVKeYQkBucZqSoQ2qY17vrER46-
> S6Tw6lY8uqA5xxQ/edit#heading=h.sp1548qks85h
> 
> ---
> Jody L. DeRidder
> Head, Digital Services
> University of Alabama Libraries
> Tuscaloosa, AL 35487
> Phone: 205.348.0511
> 
> 
> "Hope lies in dreams, in imagination, and in the courage of those who dare to
> make dreams into reality." --Jonas Salk
> 

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

October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
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