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

BIBFRAME June 2012

Subject:

Re: Latest brilliant idea (fwd)

From:

Ed Summers <[log in to unmask]>

Reply-To:

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

Date:

Mon, 4 Jun 2012 08:45:55 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (62 lines)

Hi Bernhard,

I think the scenario you described at the end of your email is an
example of an approach to using Linked Data with MARC. However,
instead of focusing on it I am going to respond to your excellent
questions about the "record".

On Mon, Jun 4, 2012 at 3:29 AM, Bernhard Eversberg <[log in to unmask]> wrote:
> Can a MARC record be replaced by a set of Linked Data triples? How could
> the data exchange then actually work? Exchange, up until now, is based
> on records. So what would replace them - or is the new idea and the
> intention now to make the very concept of the bibliographic record
> obsolete? What does that mean for ILSs that used to receive MARC records?

I don't think Linked Data precludes the notion of a record, or even
that the record will be made obsolete. Much to the contrary, I think
Linked Data brings the notion of the record into the spotlight on the
Web. The reason why I say this is that using Linked Data principles
means assigning URLs to the things we care to describe (books,
authors, subjects, etc); and when those URLs are resolved (by your
browser or what have you) you get back a representation [1] of that
resource--which in my mind amounts to what we have historically called
a "record".

For example, here is a URL that identifies "MARC Formats":

    http://id.loc.gov/authorities/subjects/sh85080966

When your browser resolves this URL it will receive a text/html
document that describes the subject MARC Formats. When a machine agent
that prefers application/rdf+xml resolves the URL it currently
receives a set of of 226 RDF triples that describe MARC Formats. If
the agent prefers application/json or application/marc+xml it will get
that instead. I apologize if this answer seems burdened with technical
jargon, but your question is a technical one, so unfortunately there
is no avoiding it. Your question also gets to the heart of what Linked
Data means.

> What will it mean for the processes of cataloging and the
> catalogers' user interface?

LC has experimented at id.loc.gov with the exchange of "records" using
Atom feeds. Atom and other syndication technologies (RSS, Sitemaps,
OAI-PMH, etc) allow you to list resources that have been changed along
with their URLs. This allows interested parties to periodically fetch
the feed to see what has changed, and appropriately update their local
databases. You can see this in action at:

    http://id.loc.gov/authorities/subjects/feed/

That being said, I think there is still plenty of work and
experimentation to do in this area, some of which might even overlap
with the ResourceSync effort at NISO [2]. I hope this helps somewhat,
and doesn't confuse things more. I should be clear that I'm not
speaking for LC in any of these comments, an am just making
observations as someone who has been working in the Linked Data space.

//Ed

[1] http://www.w3.org/TR/di-gloss/#def-http-representation
[2] http://www.niso.org/workrooms/resourcesync/

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

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
https://listserv.loc.gov/cgi-bin/wa?A2=ind1206&L=BIBFRAME&D=0&P=2130
listserv.loc.gov
crawl=CC-MAIN-2021-10
52283
application/http; msgtype=response
sha1:DQACV7GIVAPFHVWC734GMKD67CP77KJP
<urn:uuid:8682ebfe-3ad1-4dcc-ba22-8195f2d61e8f>
2021-02-27T04:57:35Z
140.147.239.86
text/html
sha1:LAZCDUJR4QVBJQNBPVRBELEIGL63A6QU
<urn:uuid:bd1087de-b548-404d-b4da-05b5d9b7e0a7>
https://listserv.loc.gov/cgi-bin/wa?A2=ind1206&L=BIBFRAME&D=0&P=2130
response
<urn:uuid:bf81dd9f-edce-4c2c-902a-728e831a2deb>
isPartOf: CC-MAIN-2021-10
publisher: Common Crawl
description: Wide crawl of the web for February/March 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-210.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/