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  March 2015

BIBFRAME March 2015

Subject:

Re: Linked data

From:

"Murray, Ronald" <[log in to unmask]>

Reply-To:

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

Date:

Mon, 30 Mar 2015 13:54:03 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (110 lines)

Well:

First there was Henry Ford, and then there were the Dodge Brothers - and
how they manufactured automobiles has everything to do with this thread.A
quick skim of Simpn Headıs ³The New Ruthless Economy*² will point out that
the initial stages of mass production were characterized by assembly lines
designed to create specific products. Ford perfected this strategy,
thinking that variety of product lines was not required.

This is the mode of production that library luminaries admired and
adopted, because thatıs what was available - efficient generation of a
uniform product.

It was only when the Dodge Brothers (using money they got for suing Henry
Ford) started General Motors that the idea of *deliberately* varying model
output in an assembly line architecture took root. Their solution was to
design a common underlying production substrate into which manufacturing
elements designed to produce new models could be plugged. Mass product of
products that could be varied periodically.

Libraries did not adopt this method (whether they knew about the
distinction or not). They did not have a physical infrastructure that
could support that kind of resource description strategy. We are only
reaching that point (as a promissory note), with W3C techıs RDF playing
the underlying infrastructure role. But whereıs the
theory/experiment/design mechanism that would provide guidance for
evolutionary/revolutionary changes in IT system design?

I think that the 19th-century industrialization of the library squeezed
out most of what could have become a theory/experiment/design
 mechanism in the search for Ford-like mass production perfection.
Competitors mostly wanted to swap out the main classification scheme for
their preferred one, but rearchitecting the bibliographic description &
access substructure was out of reach.

But today is different.

Goodreads, BIBFRAME ­ you name it ­ are all part of an unrecognized,
W3C-implemented, General Motors-like strategy for building variant
resource description schemes on a common substrate. Lots of resource
description schemes out there now. The important question for me is
whether the W3C XML/RDF substrate has sufficient capability to enable
resource description structures that genuinely improve on existing ones.
Sperberg & McQueen warned about XML's limitations in representing
nonhierarchical structures. Its not clear to me that RDF addressed all of
S&Qıs concerns.


Ron Murray

* http://www.amazon.com/New-Ruthless-Economy-Power-Digital/dp/0195179838/

--------------

Ronald J, Murray
Digital Conversion Specialist
Preservation Reformatting Division
Library of Congress
Washington DC 20540

email: [log in to unmask]
phone: (202) 707-9610




On 3/29/15, 1:32 PM, "James Weinheimer" <[log in to unmask]> wrote:

>On 3/27/2015 5:46 PM, Kelley McGrath wrote:
> > I strongly disagree with the statement that someone who understands
>MARCXML can do whatever they want with the data. I think I have a pretty
>good grasp of MARC and I have spent countless frustrating hours trying
>to get information out of MARC records (and not always succeeding).
> > Granted, I'm not a developer, but I've worked with people who are
>good developers so I don't think that's the bottleneck.
> >
> > That said, I'm not sure that Bibframe is going to fix my problems.
>
>[sorry, my cat walked on my keyboard and sent the message too soon!]
>
>MARCXML is not particularly friendly to extracting some of the
>information, but it can be done nevertheless. Certainly it can be made
>easier but that doesn't mean that it can't be done. A lot of that
>information is buried in the fixed fields which are crazy, but much of
>that information is less important for the public. Besides, relatively
>few need the width of the tape is 1/4 in. (which equals value "m" in
>007/07 when 007/00 is "s"). Such information can still be extracted.
>There has been ample time (20 years or so?), plus there used to be
>money, but there is much less now.
>
>In conjunction with the basic statement that libraries could have
>created lots of things and they haven't. Look at the other sites on the
>web, for instance, Goodreads really should have been made by libraries.
>We aleady have all the information. That was a missed opportunity.
>
>The problems have not been format. Obviously, the problems are elsewhere.
>
>James Weinheimer [log in to unmask]
>First Thus http://blog.jweinheimer.net
>First Thus Facebook Page https://www.facebook.com/FirstThus
>Personal Facebook Page https://www.facebook.com/james.weinheimer.35
>Google+ https://plus.google.com/u/0/+JamesWeinheimer
>Cooperative Cataloging Rules
>http://sites.google.com/site/opencatalogingrules/
>Cataloging Matters Podcasts
>http://blog.jweinheimer.net/cataloging-matters-podcasts
>The Library Herald http://libnews.jweinheimer.net/
>
>[delay +30 days]

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

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