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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  August 2015

BIBFRAME August 2015

Subject:

Re: BIBFRAME Identifier, Role, and Authority Proposals

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Thu, 27 Aug 2015 00:17:50 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (86 lines)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 26.08.2015 um 22:48 schrieb Karen Coyle:

> What I'm getting at is that the reason that we struggle with tradition
al
> authorities in RDF is that they do not have the qualities that an RDF
> graph about a person might have. We might use the existing name
> authorities record identifiers as URIs, but the thing that is today an
> authority record will not be adequate as a graph describing a person o
r
> corporate body. The other option is to leave name authorities alone an
d
> create an entire new set of identifiers (parallel, perhaps) that are
> representative of the entity, not just of the label.

I might humbly point out that RDA mandates the collection of /data/
for identification purposes and leaves the crafting of individualized
headings merely as an option. DACS (Describing Archives - A Content
Standard) has a chapter on "/describing/ creators" (emphasis mine).
The archivist's vision of "authority" is communicated by EAC - Encoded
Archival Context without "authority" even in its name, i.e. providing
rich biographical etc. descriptions tailored to the actual corpus
(admittedly, establishing identity and rudimentary normalization of
name forms is only a tiny albeit important portion of the functions
of these records)

So I am confident that currently most authority files are under way
of being transformed from collections of headings and variant
headings into something more easily recognizable as a databases of
core identifiying information. And of course there are authority
files besides LCAuth which - possibly for a bunch of different
reasons - adopted a more data-centric view on their contents some
decades earlier.

- From the beginning on VIAF has (among other things) been relying on
the ability to extract /data/ from authority records - comparison
of headings can bring you only so far and birth and death dates
as such (and increasingly with granularity to the day, not the
year) are essential to the process, especially if there is no
bibliographical information to back the process, e.g. when trying
to bridge the gap to ULAN or Wikipedia/Wikidata and other datasets
with only loose ties to library-land.

LC records may be lacking explicit (especially death) dates, but
they usually contain a wealth of textual references which more often
than not reveal exact birth dates and other important contextual
information (affiliations, notable works, places of birth, death
and activity). So as information resources to be consulted by
humans for identification purposes these records are absolutely up
to most needs, they are just lacking data-ness. As do biographic
encyclopedias by the way. Other information resources on the
web may be richer in data (and poorer in information at the same
time) and can be used as providers of complimentary data.

In a sense, the actual contents of an authority record don't even
matter that much, the more connections to other resources are
established, the more the identity is determined by these
relations and not by information recorded *in* the record. Any
single data element might be wrong or contrived and still the
identity holds true. Think of pseudepigraphic authors of the
Late Antiquity - not even their name is known and yet they
have a very distinct identity! Eventually not only a name
like "Pseudo Galenus" but also an identifier like no2011008661
by itself serves as a cipher and the act of spelling it out
already evoces (or at least encompasses) everything that
can possibly be known, thought or felt about that entity.
(Semantically. I'm not advocating to encode the complete
information of our universe into triples and pour a substantial
part of them out on the unfortunate soul chanting the magic
no2011008661)

viele Gruesse
Thomas Berger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iJwEAQECAAYFAlXeOw0ACgkQYhMlmJ6W47OTJwP/TQimrys1JKCtLEfoVvrfl7rE
jkFKLHO7WKSz3c5300/DoLHKvio5uaFzdXPdymdbs+H3aKgg59i1BfGYnpKIyJMk
gBtQowCSCpbh13bbmL03TwMEjU3u31r3j1pBeN2QdM+RXSOBX7vGFP9sxnvZx4SF
CRmTztRfQfw/+XZ8Odk=
=Dr+F
-----END PGP SIGNATURE-----

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

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