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

BIBFRAME September 2013

Subject:

Re: Local cache vs. connection

From:

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

Reply-To:

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

Date:

Tue, 3 Sep 2013 09:20:11 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (71 lines)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Those interested in these questions (caching, indexing, etc. in the LD context) and who are of a technical background might find instructive the work done on the Apache Stanbol (a descendent of the EU IKS effort) EntityHub project:

https://stanbol.apache.org/docs/trunk/components/entityhub/

This is a software component for a larger semantic framework that attacks some of these problems, providing (cached) retrieval, management and (text- or triplestore-based) indexing of LD entities. It's by no means a solution in itself to these problems, but it's useful to me to examine how other people have approached them in concrete ways, and what they did or didn't find difficult in practice.

- ---
A. Soroka
The University of Virginia Library

On Sep 3, 2013, at 5:47 AM, Wallis,Richard wrote:

> Caching is both easier and more challenging in the Linked Data environment.
> 
> For direct access to a URI, the web infrastructure takes care of most of it.  If implemented correctly at the server end, the caches will be made aware if the information behind a URI has changed (e.g. a death date added to an authority) and will update itself.  Even if a server is not operating that way, web caches will refresh in a time based mode ensuring a near real-time up to date view.
> 
> The challenge of local storage/indexing will require rethinking of some of the approaches we have to come to rely upon.   
> 
> Take the [overly] simple case of a Work with a title, an author and a subject.  The Work description will contain three bits of information - a string "The Title" and two URIs: a VIAF URI for the author; a LCSH URI for the subject.  To build a subject index or an author index we need to get the data from somewhere else other than where the Work data came from.  
> 
> Keeping things up to date in this environment is just plain different - you will get no indication from the source of the Work that VIAF has added a death date for the author.  These challenges could have many answers - download a copy and regularly update a copy of VIAF, LCSH, etc., etc. - use remote indexes - check in the background (using the web) each of theURIs you use to see if the indexing data has changed - and combinations thereof.
> 
> All of this is important "It is not the model but without it the model won't work in real life", but is separate from the data model and vocabulary. Which is why we should consider a parallel implementation(s) guide which would help draw some of the technology specific debate away from confusing the modelling and vocabulary discussion. Bibframe is still a good forum for both.
> 
> My 2 cents….
> 
> 
> 
> ~Richard
> 
> On 3 Sep 2013, at 06:03, Shlomo Sanders <[log in to unmask]> wrote:
> 
>> I agree with your sentiment.
>> 
>> There are 2 primary ways of using Linked Data
>> - Just In Time access baed on the URI. For example, AJAX based display in a user interface.
>>   This scenario has me less worried.
>> - Just In Case local caching. This is mandatory for data to be locally indexed for search purposes. This case is more problematic because of the challenges of keeping the local cache up to date. The more LD you use the more it becomes an issue.
>> 
>> If the community, as a community, would implement a push mechanism of updates that is appropriate to Linked Data this would be a big help. A good example could be community acceptance of ResourceSynch, Unfortunately this is another case of Chicken and the Egg. Most do not create a Client listener if there aren't enough Servers. Most do not create Servers if there aren't enough Clients. Around and around we go. 
>> 
>> One way out of this cycle is explicitly recommending a specific solution as part of the BF framework. It is not the model but without it the model won't work in real life (at least not if we want to gain enough advantages to warrant implementing BF). This may be arguable, but it is my opinion.
>> 
>> Thanks,
>> Shlomo
>> 
>> Sent from my iPad
>> 
>> On Sep 2, 2013, at 20:10, "J. McRee Elrod" <[log in to unmask]> wrote:
>> 
>>> Perhaps there could be notification if there is change in the authority,
>>> say a death date added?
>> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSJeINAAoJEATpPYSyaoIkh24IAJkZs0sQLRUkEcZGlQfEkcMq
B+9vGjv0/cBN3A9MRZpxLeWUyH4dvmEBjAYmS7XFKAryiVAHI/Wk/EQVse4x7/BN
Va5vE65Xm8dARrT5VK7EOzr1ErsFrEYBftcmuLXLm7/ktifhFmLybeL49r08OG6e
GnIXmB3nghgQQJJpS15h6OU3HGHM/xBgMHz1WWiURSENtyjwWtYX4iwv3lRivSxM
CDLe678ovG8lmCiTtwxkNC0Yu/NysL5JJRpEQgmbzrDWeC6hUzBvqizZcDF6Eblr
4a7AWsBb48s4nnSjPcFaRNpxGJY6HUSH4tTxjMRO0+ky0vC8ipPbLn0qBbBmkis=
=3oSd
-----END PGP SIGNATURE-----

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

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