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

BIBFRAME April 2015

Subject:

Re: How is Bibframe data stored?

From:

"LeVan,Ralph" <[log in to unmask]>

Reply-To:

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

Date:

Fri, 10 Apr 2015 14:32:58 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Millions of triples?  Puhleeze.

At OCLC we've got >300M bib records, around a billion article records and billions of holdings records.  That's going to be a *lot* of triples.

Ralph

-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Martynas Jusevicius
Sent: Friday, April 10, 2015 4:25 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] How is Bibframe data stored?

Usage patterns do matter, I agree. But if we're only talking about an order of millions of triples, there is no reason to believe that a triplestore could not perform adequately in real-world usage scenarios. This has been done already many times.

To my knowledge, BIBFRAME was designed as an RDF vocabulary and intended for Linked Data use. So it's not me prescribing RDF. RDF is the natural data model of choice here, while RDBMS a source of data from legacy systems. Putting RDF data into an RDBMS makes no sense.

On Fri, Apr 10, 2015 at 11:09 AM, Ross Singer <[log in to unmask]> wrote:
> Martynas, the number of triples don't matter.  It's the usage pattern 
> that does.
>
> To answer your question about "Because when you decide a DESCRIBE is 
> not enough and you want a custom CONSTRUCT instead, you simply do that 
> with the triplestore and you're stuck in the RDBMS setup that you suggest."
>
> In that scenario, export to a triplestore and do what you need.  The 
> vast majority of operations (and libraries) will never need or want to 
> do this, though.
>
> And I disagree about using a triplestore for everything and I think it 
> will be a very long time (if ever) that you'll see it embraced by the enterprise.
>
> Regardless, it's counter-productive to prescribe a specific technology 
> if the goal is to increase adoption.  Especially if you don't know 
> what the needs and constraints are.
>
> -Ross.
>
> On Fri, Apr 10, 2015 at 8:58 AM Martynas Jusevičius 
> <[log in to unmask]>
> wrote:
>>
>> I question I've already asked here, but received no answer to: what's 
>> the ballpark number of triples we're talking about?
>>
>> Here's a list of large triplestore setups to compare with:
>> https://www.w3.org/wiki/LargeTripleStores
>>
>> On Fri, Apr 10, 2015 at 10:47 AM, Bernhard Eversberg 
>> <[log in to unmask]>
>> wrote:
>> > 10.04.2015 09:18, Ross Singer:
>> >>
>> >> But if you're just using DESCRIBEs, why bother with a triplestore?  
>> >> Why bother storing it natively as RDF at all?
>> >>
>> >> BIBFRAME only touches part of a library's data, and it doesn't 
>> >> make much sense to model the rest as RDF.  ...  Even more 
>> >> unnecessary if it's sole purpose is to enable queries that are not 
>> >> even particularly useful.
>> >>
>> > It is unfortunate that not much can be said up to now about the use 
>> > cases to be expected. Though it was very likely deliberate by LC to 
>> > not specify anything about use scenarios when they commissioned the 
>> > development of BIBFRAME - so as not to anticipate anything that 
>> > might be too library specific or backward.
>> > But one thing is clear: storage methods will have to scale well. 
>> > Very well indeed. Both in terms of data volume and access traffic volume.
>> > What's the attitude of OCLC in that regard, and the vendors'? I 
>> > mean, they should have some views, based on their experience.
>> >
>> > B.Eversberg

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

July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
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