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 2014

BIBFRAME June 2014

Subject:

Re: Problems in source data

From:

"[log in to unmask]" <[log in to unmask]>

Reply-To:

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

Date:

Sun, 29 Jun 2014 16:55:38 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (60 lines)

I think that perhaps the most important work in this area is coming out of W3C's LDP activity:

http://www.w3.org/2012/ldp/wiki/Main_Page
http://www.w3.org/TR/ldp/

now being implemented by Marmotta, Fedora Commons, and other software.

A question that seems to be arising for this community is how workflows within it will change with the advent of these new ways of sharing work? That's surely beyond the scope of the Bibframe project, but I think that anyone who wants to engage with Bibframe will find themselves facing that question.

---
A. Soroka
The University of Virginia Library

On Jun 29, 2014, at 4:08 PM, "[log in to unmask]" <[log in to unmask]> wrote:

> Note that Linked Data caches work quite differently from the way as it is known from plain HTTP retrieval. An example how to cache Linked Data resources is implemented in the open-source software Apache Marmotta
> http://marmotta.apache.org/ldcache/usage.html
> 
> There is no reason to license linked data access from commercial catalog providers. All the data should be free and open (another story is licensing software and paying for support). When using restrictive licensing on data, catalog linking will not work. This is the reason why many national libraries are providing authority files by using a CC0 waiver.
> 
> Transporting such files which are publicly available through the library community (and through the vendors' silos) will be easier than ever. First, with the internet, we have enormous network bandwidth capacities available for cultural data. Second, with Linked Data Fragments - see also
> 
> http://linkeddatafragments.org/
> 
> http://www.w3.org/community/hydra/2014/06/20/hydra-welcomes-linked-data-fragments/
> 
> you can shovel the data you need very fast into your local system and prepare it for display or editing. 
> 
> This is very different from traditional MARC data supply path. You are no longer tied to tedious file import/export or slow and unstable SPARQL endpoints. Linked Data fragments may be retrieved once per day, or once per hour - the target is the real time web, with the help of large aggregating linked data hubs, to distribute the authoritative information globally at the highest possible speed and reliability.
> 
> JŲrg
> 
> 
> On Sun, Jun 29, 2014 at 9:21 PM, Simon Spero <[log in to unmask]> wrote:
> On Jun 29, 2014, at 8:15 AM, [log in to unmask] <[log in to unmask]> wrote:
> 
>> It's hard for me to imagine that those using linked library data will be putting what is retrieved from the network directly in front of their patrons without intervention. That's not really technically feasible, whatever the desire may be.
> 
> Itís not even really desirable to present the raw data directly to most users in most cases, anymore than it would be to present them with a raw MARC record (looking the tags and offsets in the directory  is a real pain).  Assembling the entities from streams of RDF triples is almost as painful to do by eye. :) 
> 
>> We will need to be guided by the Web architecture and use a design with caching. If you cache remote linked data resources locally (and if you intend to give your patrons a reasonable experience, you will be caching) you can certainly make emendations into or out of the cache, processing data in whatever ways you see fit. 
> [Small but important point:  Web caches arenít supposed to monkey about with the contents of documents they are caching - see http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.1.1 ]   
> 
> Exactly! Adding assertions about some Entity is one of the things that Linked Data makes really easy.  If an IRI  denoting some fictional thing lacks the  appropriate characterization, you can make the appropriate assertion yourself; for example adding an assertion that the entity is a member of the class of FictionalThings.  This can be published for others to use.  
> 
> A well designed future bibliographic network for open data would allow for all assertions about a given entity to be retrieved cheaply;  indeed it is probably feasible to copies of all assertions locally using simple overlay techniques.  Data can be fused from multiple sources.  
> 
> Commercial cataloging providers might require a subscription to access their data, and strictly license its use and reuse. 
> 
> Simon      
> 
> On Jun 28, 2014, at 5:04 PM, J. McRee Elrod <[log in to unmask]> wrote:
> 
>> The ability to add information locally, to be displayed with the remote data?  The RDA relator terms (MARC $e), for example, would I assume not be in the authority data, but rather stored locally for display with the authority form.  Perhaps the same could be done for missing qualifiers (MARC $c)?
>> 
>> Of course a better solution would be for LC/PCC to restore those missing (Fictitious character) and species qualifiers.
> 
> 
> 

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