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  February 2017

BIBFRAME February 2017

Subject:

Re: Failure

From:

"James L. Weinheimer" <[log in to unmask]>

Reply-To:

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

Date:

Mon, 6 Feb 2017 20:35:54 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (65 lines)

On 06/02/2017 16:32, Jeff Edmunds wrote:
> Your final paragraph is what intrigues me most. How, in fact, would
> widespread adoption by libraries of BIBFRAME (or whatever it evolves
> into) affect user experience? Would they find more resources? Would they
> find them more quickly? Would resources discovered be better
> contextualized, such that information literacy would be in some sense
> built into search results? I doubt it.

Again, when someone makes their data available in RDF and linked data,
that doesn't mean that the *owners* of that data will be able to do
something they couldn't already have done with their own data. Sure,
some things may get easier and others may get harder, but when you are
dealing with your own data, you can already do whatever you want to with
it. The purpose of RDF/Linked data is to allow *others* to use your data
in better, easier, and more standardized ways than putting your data up
in Excel files or something similar. If a library wants to use linked
data from some other sites in their catalog, e.g. from
Wikipedia/Wikidata, they can do it right now without having to turn
their own data into RDF.

So, putting our data in Bibframe/RDF will allow *non-library agencies*
to create tools such as an "Uber" but they will be able to include
Bibframe library data, e.g. something that brings together Bibframe
data, Wikidata, and the Google Art Project might be useful--if it
doesn't exist already. Still, just because you put your data into RDF
and make it openly available, doesn't guarantee that anyone will use
your data, and a glance at the Linked Open Data cloud
(http://lod-cloud.net/) will show lots of linked data sites that perhaps
no one has ever used.

One app I have considered making would bring together images and
information for visitors to some of the museums in Rome. For instance,
there is a fabulous museum of musical instruments and when I visited it,
I kept thinking it would be great to be able to hear how those
instruments sound. Additional information about the instruments would be
OK too. There would be a lot of ways to make it, but one way of creating
a tool such as this would be to include, e.g. the LOD information from
Wikipedia/Wikidata. Would I use Bibframe information if it were
available? Maybe. I don't know if letting someone in a museum know what
is available from a library would be all that useful for them or
not--but I must say that if there is no option to use library data, it
certainly cannot be used.

Additionally, RDF/Linked data is not the only way to use information
from other sites. The fabulously popular Google Maps uses a different
technology (API) which is simpler for everyone to implement and there
are tons of all kinds of APIs
(https://www.programmableweb.com/apis/directory). Worldcat has APIs but
I'm not sure they are open or not.

That said, we should make library data available in formats other than
Z39.50 and it should have been done at leasts 20 years ago. I am for the
Bibframe project, but we shouldn't expect libraries to do anything new
with their own data than what they have been doing all along.

--
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/

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

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