Re: Easy and simple Linux triple-store

Hi Nick.

Explain said apathy :/

I get compile errors for Redstore in Ubuntu 17.10 otherwise I'd love to use
it because it seems so lightweight.

--8<--

Making all in src
make[1]: Entering directory '/home/groobiest/†/src/redstore-0.5.4/src'
make  all-recursive
make[2]: Entering directory '/home/groobiest/†/src/redstore-0.5.4/src'
Making all in redhttp
make[3]: Entering directory
'/home/groobiest/†/src/redstore-0.5.4/src/redhttp'
/bin/bash ../../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../src     -g -O2 -MT server.lo -MD -MP -MF .deps/server.Tpo -c -o
server.lo server.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -g -O2 -MT server.lo
-MD -MP -MF .deps/server.Tpo -c server.c  -fPIC -DPIC -o .libs/server.o
server.c: In function ‘redhttp_server_listen’:
server.c:62:19: error: storage size of ‘hints’ isn’t known
   struct addrinfo hints;
                   ^~~~~
server.c:69:20: error: ‘AI_PASSIVE’ undeclared (first use in this
function); did you mean ‘AF_WANPIPE’?
   hints.ai_flags = AI_PASSIVE;
                    ^~~~~~~~~~
                    AF_WANPIPE

--8<--

Raptor2 is at version 2.0.14-1build1
Rasqal is at version 0.9.32-1build1
Redland is at version 1.0.17-1.1

So everything appears to be at a version higher than is required.

Best,
    Anthony

On 1 November 2017 at 17:09, Nicholas Humfrey <nicholas.humfrey@bbc.co.uk>
wrote:

> I wrote 'RedStore' precisely for the purpose of being a 'Easy and simple
> Linux triple-store' that you can get up and running quickly:
> https://github.com/njh/redstore
>
> It uses Redland as a backend and can either use a SQLite or BerkeleyDB
> backed storage (in-memory or on-disk). However it isn't very performant. It
> was supposed to be able to load a RDF file at launch and export it at
> shutdown.
>
> And I have lost energy in continuing to develop it, due to my increasing
> apathy about SemanticWeb / RDF technology.
>
>
> nick.
>
>
>
> From: Leif Warner <abimelech@gmail.com>
> Date: Wednesday, 1 November 2017 at 16:53
> To: Anthony Durity <a.durity@umail.ucc.ie>
> Cc: W3C Ruby RDF mailing list <public-rdf-ruby@w3.org>
> Subject: Re: Easy and simple Linux triple-store
> Resent-From: <public-rdf-ruby@w3.org>
> Resent-Date: Wednesday, 1 November 2017 at 16:53
>
> I think Redland would be the equivalent of SQLite. I think it's backed by
> BerkeleyDB or something. The whole suite comes with lots of useful
> command-line tools.
>
> You could also just maintain an in-memory graph, and re-write it to disk
> on program exit. Can write modifications to disk as they happen for more
> durability, as a write-ahead log.
>
> On Nov 1, 2017 4:32 AM, "Anthony Durity" <a.durity@umail.ucc.ie> wrote:
>
>> Hullo all,
>>
>> Apologies if this is a stupid question.
>>
>> I would like to know if there is any tech that would be the triple-store
>> equivalent to Sqlite? What I want is to create my only local graph based on
>> nodes in Wikidata and data I generate myself.
>>
>> What technology do people use? Is there a recommended stack? I don't
>> necessarily mean something like Ruby on Rails which is convention over
>> configuration and "batteries included" by I don't mean Opengraph Virtuoso
>> either, that's way too heavyweight.
>>
>> I'm running Ubuntu 17.10, a fairly popular distro. I can't seem to
>> compile Redstone and anyway it appears unmaintained. Cayley looks cool but
>> doesn't have its own on-disk back-end? (I don't understand that). Franz
>> Allegrograph seems too commercial and lispy (maybe I'm wrong about this.).
>> I don't want to use Jena because, um, Java.
>>
>> I can't find a single simple tutorial about using ruby-rdf to write to,
>> modify, and query my own local triple-store.
>>
>> Most of the time I think it would be easier to define a relational model
>> and map to triples on the fly and then I'd use tech that I'm familiar.
>>
>> For small projects what do people use? I don't want to spend a week
>> setting up a local triple-store. I want something that is robust, I can set
>> up nearly as easily as Rails, is actively maintained, and supports most of
>> the current Semantic Web tech.
>>
>> Is there something obvious I'm not getting or that I'm overlooking?
>>
>> Thanks!
>>     Anthony
>>
>