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

BIBFRAME March 2015

Subject:

Linked data

From:

"J. McRee Elrod" <[log in to unmask]>

Reply-To:

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

Date:

Thu, 5 Mar 2015 09:22:58 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (101 lines)

Forwarded by permission of James Weinheimer:



  There are some points to keep in mind when considering linked
  data/semantic web. The new formats (schema.org, Bibframe) are *not*
  there for libraries to be able to do new and wonderful things with their
  own data. Why? Because libraries already understand and control all of
  that data. Right now, so long as we have XML formats (and we have that
  now with MARCXML) we can do *anything* we want with the data. MARCXML is
  not perfect, but it is still XML and that means: librarians can search
  that data however we want, manipulate it however we want, transform it
  however we want, sort it however we want and display it however we want.
  If we want to search by the fiction code in the fixed fields and sort by
  number of pages or by 100/700$q we can. We can print out reams of entire
  records, or any bits and pieces of them we could want, collate them in
  any number of ways (or not), and print them out on 3D printers in
  day-glow colors, display them with laser beams on the moon or work with
  them in the virtual reality "wearable technology". We can do all of that
  and more *right now* if we wanted. We've been able to do it for a long
  time. We don't need schema.org or Bibframe to enhance our own
  capabilities because we can do anything with our own data now.
 
  So, who is schema.org and Bibframe for? Non-librarians, i.e. for people
  who neither understand nor control our data. Libraries will allow others
  to work with our data in ways that they can understand a bit more than
  MARC. Non-librarians cannot be expected to understand 240$k or 700$q,
  but with schema.org or Bibframe, it is supposed to be easier for
  them--although it still won't be easy. Nevertheless, they will be able
  to take our data and do with it as they will as they cannot do now with
  our MARC/ISO2709 records. 
  
  With Bibframe and schema.org people will be able to merge it with other
  parts of the linked data universe (oops! Not Freebase or dbpedia.
  They'll have to go to Wikidata! Wonder how long that will last!) or with
  all kinds of web APIs (see http://en.wikipedia.org/wiki/Web_API) that
  can create mashups. (I still think this video gives the best description
  of a mashup: https://www.youtube.com/watch?v=ZRcP2CZ8DS8. Here too is a
  list of some of the web apis
  http://www.programmableweb.com/apis/directory) Web programmers can then
  put these things together to create something absolutely new, e.g. bring
  together library data with ebay so that people can see if something on
  ebay is available in the library or vice versa. But remember that those
  web programmers will also be able to manipulate our data as much as we
  can, so the final product they create may look and work completely
  differently than we would imagine, or that we would like. As a result,
  libraries and catalogers will lose the control of their data that they
  have always enjoyed. For better or worse, that is a necessary
  consequence of sharing your data.
 
  Then comes what are--I think--the two major questions of linked data for
  libraries. First is: OK. We add the links, but what do we link *to*?
  Will linking into id.loc.gov appeal to the public? I personally don't
  think so since there is so little there, other than the traditional
  syndetic structures found in our traditional catalogs (i.e. the UF, BT,
  NT, RT for subjects, the earlier/later names of corporate bodies and
  series, the other names of people). This is not what people think of
  when they think of the advantages of linked data. While those things may
  be nice for us, I don't know if that will be so appealing to the public.
  If it is to become appealing to the public, somebody somewhere will have
  to do a lot of work to make them appealing.
 
  Concerning VIAF, it's nice to know the authorized forms in Hebrew,
  French, Italian, and so on, but again, is that so appealing to the
  *public*? It may be, but that remains to be proven.
 
  Second, there is no guarantee at all that anyone will actually do
  anything with our data. While I certainly hope so, there are no
  guarantees that anybody will do anything with our data. It could just
  sit and go unused.

  It's interesting to note that the LC book
  catalog in this format has been in the Internet Archive for awhile now
  (https://archive.org/details/marc_records_scriblio_net) but I haven't
  heard that any developers have used it.
  
  I want again to emphasize that libraries should go into linked data, but
  when we do so, there will probably be more question marks than
  exclamation points. Just as when a couple is expecting a baby and they
  experience pregnancy: at least when I experienced it, I imagined that
  the birth of my son would be an end of the pregnancy. But suddenly, I
  had a crying baby on my hands! Linked data will be similar: it will be a
  beginning and not an end.
 
  James Weinheimer [log in to unmask] First Thus
  http://blog.jweinheimer.net First Thus Facebook Page
  https://www.facebook.com/FirstThus Cooperative Cataloging Rules
  http://sites.google.com/site/opencatalogingrules/ Cataloging Matters
  Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts [delay
  +30 days]
 
  --

-- 
James Weinheimer [log in to unmask] First Thus 
http://blog.jweinheimer.net First Thus Facebook Page 
https://www.facebook.com/FirstThus Cooperative Cataloging Rules 
http://sites.google.com/site/opencatalogingrules/ Cataloging Matters 
Podcasts http://blog.jweinheimer.net/cataloging-matters-podcasts [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

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=BIBFRAME;bf1274bb.1503
listserv.loc.gov
crawl=CC-MAIN-2019-35
54935
application/http; msgtype=response
sha1:EPAQWWURZ4XSCTOHM4SPCM7HXCNCLNQV
<urn:uuid:09b9576f-3191-4aed-8c5d-2521a411767a>
2019-08-20T23:50:12Z
140.147.55.47
text/html
sha1:3LLKDSDIJP57FJWMENAFUPPQNWL2UH46
<urn:uuid:f1e0d850-9538-4f95-8b44-cb62b5036a8e>
https://listserv.loc.gov/cgi-bin/wa?A2=BIBFRAME;bf1274bb.1503
response
<urn:uuid:d8a663a8-a600-4525-a7e7-babd42843bde>
isPartOf: CC-MAIN-2019-35
publisher: Common Crawl
description: Wide crawl of the web for August 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-238.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-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/