Experience using bio2rdf datasets on blazegraph

[Sean Davis]

Hello, all.

I am new to the Bio2RDF list but have been following the project from a distance. I hate to start communications with a new group with technology questions, but since the utility of RDF data relies heavily on the technology exposing it, I thought I would ask about experiences with blazegraph.  I have given it a try and found it to be somewhat easier to use than Virtuoso for basic use cases.  Has anyone used it (or other graph database engines) to host Bio2RDF datasets locally?  If so, can you share your experiences?

Thanks,

Sean

[Kingsley Idehen]

--
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 https://groups.google.com/group/bio2rdf.
For more options, visit https://groups.google.com/d/optout.

What is a Basic Usecase?

A basic Virtuoso usecase goes as follows:

1. Download installer

2. Run installer

3. Start your server

4. Load RDF into your Database.

I would be happy to learn a simpler approach to working with RDF data than what's outlined above.
Of course, if you are using the Open Source edition, you have the standard expectations re. source compilation prior to steps 3 & 4 above.

-- 
Regards,

Kingsley Idehen	      
Founder & CEO 
OpenLink Software   (Home Page: http://www.openlinksw.com)

Weblogs (Blogs):
Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
Blogspot Blog: http://kidehen.blogspot.com
Medium Blog: https://medium.com/@kidehen

Profile Pages:
Pinterest: https://www.pinterest.com/kidehen/
Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter: https://twitter.com/kidehen
Google+: https://plus.google.com/+KingsleyIdehen/about
LinkedIn: http://www.linkedin.com/in/kidehen

Web Identities (WebID):
Personal: http://kingsley.idehen.net/dataspace/person/kidehen#this
        : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this

[Egon Willighagen]

On Thu, Sep 29, 2016 at 2:37 PM, Kingsley Idehen <kid...@openlinksw.com> wrote:
> Of course, if you are using the Open Source edition, you have the standard expectations re. source compilation prior to steps 3 & 4 above.

Which is actually for me too a reason to like Blazegraph, even being a
long term VOS user!

Egon

--
E.L. Willighagen
Department of Bioinformatics - BiGCaT
Maastricht University (http://www.bigcat.unimaas.nl/)
Homepage: http://egonw.github.com/
LinkedIn: http://se.linkedin.com/in/egonw
Blog: http://chem-bla-ics.blogspot.com/
PubList: http://www.citeulike.org/user/egonw/tag/papers
ORCID: 0000-0001-7542-0286
ImpactStory: https://impactstory.org/u/egonwillighagen

[Hilmar Lapp]

Phenoscape uses Blazegraph for its Knowledgebase, and we've been quite happy with it: http://kb.phenoscape.org

If you have specific questions about our experience with it, contact Jim Balhoff (copied).

-hilmar

Sent from away

[Kingsley Idehen]

On 9/29/16 8:52 AM, Egon Willighagen wrote:

On Thu, Sep 29, 2016 at 2:37 PM, Kingsley Idehen <kid...@openlinksw.com> wrote:

> Of course, if you are using the Open Source edition, you have the standard expectations re. source compilation prior to steps 3 & 4 above.

Which is actually for me too a reason to like Blazegraph, even being a
long term VOS user!

What is the problem though?

1. Build instructions unclear?

2. Build process unpredictable?

[Kingsley Idehen]

On 9/29/16 9:12 AM, Hilmar Lapp wrote:

Phenoscape uses Blazegraph for its Knowledgebase, and we've been quite happy with it: http://kb.phenoscape.org

If you have specific questions about our experience with it, contact Jim Balhoff (copied).

-hilmar

Do you have a SPARQL endpoint URI that I could look at?

Kingsley

Sent from away

On Sep 28, 2016, at 2:33 PM, Sean Davis <sean...@gmail.com> wrote:

Hello, all.

I am new to the Bio2RDF list but have been following the project from a distance. I hate to start communications with a new group with technology questions, but since the utility of RDF data relies heavily on the technology exposing it, I thought I would ask about experiences with blazegraph.  I have given it a try and found it to be somewhat easier to use than Virtuoso for basic use cases.  Has anyone used it (or other graph database engines) to host Bio2RDF datasets locally?  If so, can you share your experiences?

Thanks,

Sean

--
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 https://groups.google.com/group/bio2rdf.
For more options, visit https://groups.google.com/d/optout.

--
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 https://groups.google.com/group/bio2rdf.
For more options, visit https://groups.google.com/d/optout.

[Hilmar Lapp]

Hi Kingsley,

The SPARQL endpoint at this point isn’t meant for public consumption. We have a publicly accessible API instead:

http://docs.phenoscapekb.apiary.io/#

  -hilmar

-- 

Hilmar Lapp -:- lappland.io

[Kingsley Idehen]

On 9/29/16 11:59 AM, Hilmar Lapp wrote:

Hi Kingsley,

The SPARQL endpoint at this point isn’t meant for public consumption. We have a publicly accessible API instead:

http://docs.phenoscapekb.apiary.io/#

  -hilmar

Hilmar,

Okay, but do bear in mind that Virtuoso is about making a Linked Data Space on an HTTP network, with ease. Net effect, you end up with the following:

1. SPARQL Query Service (a/k/a SPARQL Endpoint)
2. Linked Data Deployment -- using server hosted Faceted Browser
3. Ability to leverage SPARQL for item 2 using your own redirection oriented rewrite rules from a URI pattern to a SPARQL Query where output is a wide variety for document types.

Kingsley