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  November 2012

BIBFRAME November 2012

Subject:

Re: BIBFRAME Topic Authorities and LCSH

From:

Karen Coyle <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 27 Nov 2012 08:46:42 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (75 lines)

On 11/27/12 8:12 AM, Owen Stephens wrote:
> I might be jumping the gun with some of these questions but just becuase I'm interested ...
>
> From the Bibliographic Framework as a Web of Data p.11
> "Authorities are not designed to compete or replace existing authority efforts but rather provide a common, light weight abstraction layer over various different Web based authority efforts to make them even more effective."
>
> From this it seems clear that it is intended that authorities can make use of existing linked data representations of LC authorities via http://id.loc.gov.

Wow, Owen. I'm impressed that you made sense of that sentence because it
was one of the ones that just said NOTHING AT ALL to me. What is a
"light weight abstraction layer" anyway? Now that you've put out a
concrete example I can see it as something like VIAF that can bring
together authority identifiers (including ones like DBPedia) from
various sources. Yes? No?

However, and partially in response to John Myers' post, there is a
difference between library authorities, which is a mechanism to control
name forms (as identifiers), and full-blown entities that represent all
information about the entity. I was hoping/assuming that our future
model would be, as John says, a set of interacting entities, and that
would mean greatly expanding beyond the minimalist authority data we
have to something much fuller. To give an example, compare this
authority record for T.C. Boyle:

http://tinyurl.com/c4gqtrb

with his Wikipedia entry:

http://en.wikipedia.org/wiki/T._C._Boyle

The latter is actually a small Wikipedia page compared to many others,
but it still provides much more information that may be useful to
readers than what the authority record provides. The authority record
was always intended to be a "back room" entity. I'm hoping that what
replaces it has more information that is helpful to information seekers.
"Lightweight abstraction layer" doesn't read like that to me.

kc
> The example Bibframe serialisation supports this:
>
> <!-- BIBFRAME Topic -->
> <Topic id="http://bibframe/auth/topic/bibliography">
>
> <label>Bibliography</label>
> <generalSubdivision>Methodology</generalSubdivision>
>
> <hasIDLink resource=http://id.loc.gov/authorities/subjects/sh85013838 />
>
> </Topic>
>
> I did some work previously on linking to LCSH - see page 7 onwards of this presentation http://www.slideshare.net/ostephens/linking-lcsh-and-other-stuff, and based on this experience this example prompts me to ask:
>
> Is it expected that the Topic will include textual strings representing the subject as here?
> The example here suggests that there is some structure (LCSH based) within the Topic - is that the case? How would ordering be dealt with?
> Since id.loc.gov only issues URIs for Authorised headings, how would valid but unauthorised headings be represented (this was the focus of my presentation)
>
> Representing the topic as madsrdf could solve these problems?
>
> Finally - just to pedantically note that http://id.loc.gov/authorities/subjects/sh85013838 is the URI for the LCSH Topical Term Bibiliography. The correct URI for Bibliography--Methodology is http://id.loc.gov/authorities/subjects/sh85013859
>
> Owen
>
> Owen Stephens
> Owen Stephens Consulting
> Web: http://www.ostephens.com
> Email: [log in to unmask]
> Telephone: 0121 288 6936

--
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

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

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