New LOD Cloud Cache -- 51 Billion+ Triples in Virtuoso 7.0

[Ted Thibodeau Jr]

All,

We are pleased to unveil the new Virtuoso 7.0 LOD Cloud Cache [1][2].

Naturally, this release takes full advantage of performance and
scalability enhancements for both SPARQL and SQL delivered by the
new Virtuoso DBMS engine.

To aid understanding of what's now possible, we've published a
Google Spreadsheet [3] including response times for a collection
of analytics-oriented queries and which anyone can perform against
the new public SPARQL endpoint.


Links:

1. LOD Cloud Cache home page
(for text searches, label, and/or URI lookups) --
http://lod.openlinksw.com/

2. LOD Cloud Cache SPARQL endpoint --
http://lod.openlinksw.com/sparql

3. Sample queries showing Virtuoso 7.0's effect on latest
LOD Cloud Cache (comprised of 51 Billion+ relations) --
http://bit.ly/YQMHo2

Related:

• Virtuoso 7.0 blog announcement -- http://bit.ly/18FXEL5

• Column Store Tutorial from Peter Boncz and +Daniel Abadi --
http://bit.ly/17oSWk9

• Prof. Michael Stonebraker talks about NoSQL and NewSQL
as they relate to Big Data --
http://slidesha.re/13RzSfq

• IEEE Data Engineering Technical Bulletin which includes
coverage of Column-Stores and Virtuoso --
http://bit.ly/166kEnC

• Commercial Edition download page -- http://bit.ly/18tkbKU

• Open Source Edition on Github -- http://bit.ly/18tkpBF

• Virtuoso 7.0 special offers -- http://bit.ly/11zHXB2


Feedback of all sorts is welcomed and encouraged!

Regards,

Ted


--
A: Yes. http://www.guckes.net/faq/attribution.html
| Q: Are you sure?
| | A: Because it reverses the logical flow of conversation.
| | | Q: Why is top posting frowned upon?

Ted Thibodeau, Jr. // voice +1-781-273-0900 x32
Senior Support & Evangelism // mailto:tthib...@openlinksw.com
// http://twitter.com/TallTed
OpenLink Software, Inc. // http://www.openlinksw.com/
10 Burlington Mall Road, Suite 265, Burlington MA 01803
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter -- http://twitter.com/OpenLink
Google+ -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers

[Michel Dumontier]

Hi Ted,

  Unfortunately, it looks like you didn't use Bio2RDF's latest data.

http://lod.openlinksw.com/describe/?url=http%3A%2F%2Fbio2rdf.org%2Fpharmgkb%3APA28903&sid=7719

http://pharmgkb.bio2rdf.org/describe/?url=http%3A%2F%2Fbio2rdf.org%2Fpharmgkb%3APA28903&sid=207&urilookup=1

how did you get your Bio2RDF data?

FYI: our download page: http://download.bio2rdf.org/current/

is it possible for you to remove the old data and add the new data?

m.

--

Michel Dumontier

Associate Professor of Bioinformatics, Carleton University

Chair, W3C Semantic Web for Health Care and the Life Sciences Interest Group

http://dumontierlab.com

[Kingsley Idehen]

On 5/13/13 5:02 PM, Michel Dumontier wrote:

Hi Ted,

  Unfortunately, it looks like you didn't use Bio2RDF's latest data.

http://lod.openlinksw.com/describe/?url=http%3A%2F%2Fbio2rdf.org%2Fpharmgkb%3APA28903&sid=7719

http://pharmgkb.bio2rdf.org/describe/?url=http%3A%2F%2Fbio2rdf.org%2Fpharmgkb%3APA28903&sid=207&urilookup=1

how did you get your Bio2RDF data?

FYI: our download page: http://download.bio2rdf.org/current/

is it possible for you to remove the old data and add the new data?

Yes.

Kingsley

--
You received this message because you are subscribed to the Google Groups "bio2rdf" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bio2rdf+u...@googlegroups.com.
To post to this group, send email to bio...@googlegroups.com.
Visit this group at http://groups.google.com/group/bio2rdf?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

-- 

Regards,

Kingsley Idehen	      
Founder & CEO 
OpenLink Software     
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

[Ted Thibodeau Jr]

Hi, Michel --

On May 13, 2013, at 05:02 PM, Michel Dumontier wrote:

> Hi Ted,
> Unfortunately, it looks like you didn't use Bio2RDF's latest data.
>
> http://lod.openlinksw.com/describe/?url=http%3A%2F%2Fbio2rdf.org%2Fpharmgkb%3APA28903&sid=7719
> http://pharmgkb.bio2rdf.org/describe/?url=http%3A%2F%2Fbio2rdf.org%2Fpharmgkb%3APA28903&sid=207&urilookup=1
>
> how did you get your Bio2RDF data?

I believe we reloaded the same Bio2RDF data set as we had in
the previous rendition of the LOD Cloud Cache, from not *too*
far in the past, but still...

We should have downloaded a fresh set from you for this load.

We'll rectify that as soon as possible.

Thanks for the heads up!

Be seeing you,

Ted

[Jeremy J Carroll]

This thread takes me to concern about version management.

My understanding is that the data Ted and Kingsley are putting together is interesting for my customers.

We are likely to provide annotation facilities to link from the customer data into the LOD cloud, quite possibly using this cache or some similar mechanism.

Now, as the LOD cloud updates, and the LOD cloud cache updates, some of these customer links will go bad: both syntactically in that they will 404, and worse, semantically, in that there may be some (possibly quite subtle) change in the reference data that makes the link from the customer data no longer appropriate (but not obviously broken)

Now one way to manage this is to use Ted and Kingsley's cache, with a fairly strict approach to versioning, so that
a) somewhere I have a copy of old versions of the cache
b) for each link between our customer data and the LOD we know which version of the cache was intended
…
and ….
?

any thoughts?

Micheal said:
>> Unfortunately, it looks like you didn't use Bio2RDF's latest data.

i.e. I differ somewhat from Michael's "Unfortunately" and suggest that it might be more like "Inevitably"


Jeremy J Carroll
Principal Architect
Syapse, Inc.

[Kingsley Idehen]

On 5/14/13 5:27 PM, Jeremy J Carroll wrote:
> This thread takes me to concern about version management.
>
> My understanding is that the data Ted and Kingsley are putting together is interesting for my customers.
>
> We are likely to provide annotation facilities to link from the customer data into the LOD cloud, quite possibly using this cache or some similar mechanism.
>
> Now, as the LOD cloud updates, and the LOD cloud cache updates, some of these customer links will go bad: both syntactically in that they will 404, and worse, semantically, in that there may be some (possibly quite subtle) change in the reference data that makes the link from the customer data no longer appropriate (but not obviously broken)
>
> Now one way to manage this is to use Ted and Kingsley's cache, with a fairly strict approach to versioning, so that
> a) somewhere I have a copy of old versions of the cache
> b) for each link between our customer data and the LOD we know which version of the cache was intended
> …
> and ….
> ?
>
> any thoughts?

It is possible for this to happen outside the cache via provenance
oriented datasets. Of course, said datasets could end up being loaded
via privileged access to SPARQL 1.1 utilization via WebID driven access
controls and data access policies. The great thing about Linked Data is
that you are able to attack this issue from a variety of perspectives,
in a totally loosely coupled manner.

We will also be releasing preloaded instances of the Virtuoso 7.0 DBMS
behind this cache, as we do with DBpedia and others. Thus, you can have
your own product and service specific instance instantiated via the
Amazon cloud or installed to your own setup etc..

Kingsley

[M. Scott Marshall]

Hi Jeremy,

Versioning is core to ongoing discussions about RDF dataset *descriptions* in the HCLS Linked Life Data task force (I invited you in March after your introduction to HCLS, but the words I chose to describe the discussion at the time were: "common metadata (about

an RDF dataset in a named graph)"). You can see some of what we've been discussing in this Google doc:

https://docs.google.com/spreadsheet/ccc?key=0Aoy0zfdRviKsdFJWTDFpblNXc3BtelhrdEpNYTdvbXc&usp=sharing

We've discussed ways to disclose information about provenance, versioning, format and availability, among other things. Such descriptions could serve many purposes, one of them as a way to discover and exchange information about catalog entries between database catalogs, or talk about LOD Cloud Cache releases.

You can find some minutes in the HCLS archives (if you don't, holler and I'll dig them up), from Alasdair Gray. I also pasted them into a few of the recent Google Calendar events (Mondays).

The next meeting will be next week Tuesday, 11AM ET using fuzebox (hosted by Michel). You can usually find the fuzebox URL / meeting number in the announcement to HCLS a day or two ahead of the meeting.

-Scott

-- 
M. Scott Marshall, PhD
MAASTRO clinic, http://www.maastro.nl/en/1/
http://eurecaproject.eu/
https://plus.google.com/u/0/114642613065018821852/posts
http://www.linkedin.com/pub/m-scott-marshall/5/464/a22