Consider the following sentences:

1) Mark Twain is Samuel Langhorne Clemens.
2) Mark Twain wrote The Adventures of Huckleberry Finn.
3) Samuel Langhorne Clemens wrote the Adventures of Huckleberry Finn.

4) "Mark Twain" is shorter than "Samuel Langhorne Clemens".
#5) Mark Twain is shorter than Samuel Langhorne Clemens.

6) "Mark Twain" contains 9 letters.
#7) Something containing 9 letters wrote The Adventures of Huckleberry

8) "Mark Twain" is a name used by Samuel Langhorne Clemens.
9) Samuel Langhorne Clemens is a Person.


Is it possible for there to be some thing which is both a name and a
 On Jul 9, 2014 8:14 AM, "Ford, Kevin" <[log in to unmask]> wrote:

> However the definition of a Bibframe Person as it stands is a
> “Controlled personal name”, not a person as such; foaf:Person is defined
> “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.


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
> Authority actually is. I confess, for example, that I find the formulation
> “Resource reflecting key authority concepts that have defined
> 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
> “A person” which does implicitly suggest that "bf:Person != foaf:Person".
> 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
> BIBFRAME approaches discussed. We offer the following observations.
> String Authorities rather than Identifiers BIBFRAME has explicitly stated
> bf:Authority is not designed to compete with existing library authority
> or replicate traditional library authorities.  Furthermore, nowhere is it
> 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
> existing MARC records (if we broke them up, we'd have a problem re-
> creating them should we need to), they represent current cataloging
> (for better or worse), and they provide us with ready-made labels (and
> 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
> outweighs our need for -  and stakeholders' expectations of - those
> 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
> The paper finds fault:
> • In method (a), with  the perceived restriction of role URIs to LC
> • 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
> 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
> 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
> make sense of it.
> That said, it is important to note that the primary and expected way to
> 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
> As such, we feel that Rob’s section on identifiers may be trying to
> with several different issues, all of which are about identifiers but
each of
> which should be treated separately.  These issues are likely legitimate,
> we need to sort them out. We do want to note, bf:identifierValue  expects
> string literal, and Rob’s examples appear to treat it as a resource
> identifier.  This is a fairly fundamental misinterpretation that needs to
> 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
> 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
> mistake in the Bibframe vocabulary.  All of the properties mentioned in
> 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
> reason why bf:Event and  bf:Provider  are not of class bf:Authority is
> 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:
> 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