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: Work issues

From:

Karen Coyle <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Fri, 30 Nov 2012 10:37:10 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (81 lines)

On 11/30/12 9:18 AM, Lukas Koster wrote:
>
> Looking at the described conversion procedures and the RDF example
> somehow I get the feeling that BIBFRAME Works will be treated as local
> redundant entities. I hope I'm wrong. Of course the BIBFRAME model can
> be implemented in a number of ways, both as local silo and as globally
> shared data. But I had the impression that 'based on linked data'
> meant abolition of redundancy by linking instead of
> copying/duplicating, not just using RDF as storage format.

Lukas, I tend to see "one and only one Work description for the whole
web" as a kind of platonic ideal that we will never achieve. I think the
LoD community has come to the same conclusion about identifiers for
things: it would be nice if each thing had only one identifier, but
we've already built in (and over-used) owl:sameAs because that will
probably never be the case.

For me, the question of "on the web? or locally stored?" will be decided
depending on what you are doing with the data. If you have a local
database that people will search in, you probably need to store locally
some of the key data you expect those searches to go against. If there
is information that you will mainly use for display you can simply have
a link that pulls in the relevant data at the time of display (like the
BBC links to Wikipedia). Then there is the special case of cataloging
systems for libraries, which I think will be much like they are today:
closed systems used by trained specialists with a very high degree of
sharing and low degree of freedom. Where I think things will be
significantly different from today is that the reference and user
"views" will less like the cataloging view than they are today, because
linking will allow us to add user-relevant data that doesn't interfere
with the catalog/inventory data that library management (acquisitions,
collection development, circulation) depends on.

Even in the cataloger view, my suspicion is that the Work will end up
being a cluster not unlike VIAF. That's my guess.

kc

>
> Ideally, a Work would be described only once, and as such be similar
> to an authority record to which links are made from Instances and
> Annotations. Of course in the real world we will have a limited number
> of redundant Work data stores. For this we would use "sameAs"
> relationships.
>
> In Kevin's RDF example I see however four Instance URIs, which would
> only make sense if this is a local library 'record' containing links
> to all local holdings of the work (FRBR Manifestations, originating
> from local legacy MARC records).
> A globally shared Work entity would of course never be able to hold
> links to all Instances existing in the world. This would not make any
> sense at all. A Work would not contain any Instance links at all.
> Rather, all Instances of a specific Work would obviously have one link
> to that Work.
> The only use for links to Instances in a Work would be to indicate
> provenance, which already is taken care of by the 'derivedFrom' and
> 'consolidates' links in the example.
>
> Anyway, I would expect libraries only to be dealing with Annotations
> for their own local holdings, linking, in their own new linked data
> ready systems, to existing Instances (FRBR Manifestations) made
> available by authorities such as LoC, OCLC, publishers, etc.
> Of course, Works and Instances might be available for editing by other
> trusted parties in a wikipedia way.
>
>
> Lukas Koster
> Library Systems Coordinator
> Library and Information Systems Department
> Library of the University of Amsterdam
> Web: http://uba.uva.nl
> Mobile site: http://m.uba.uva.nl
> Digital Library: http://lib.uva.nl

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

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