- From: Leif Warner <abimelech@gmail.com>
- Date: Wed, 1 Nov 2017 09:53:22 -0700
- To: Anthony Durity <a.durity@umail.ucc.ie>
- Cc: W3C Ruby RDF mailing list <public-rdf-ruby@w3.org>
- Message-ID: <CAG2mRG5fd1CO7zBNiZwkYpfkUnVm5rqyPoJfTCnGa5EgCcaWtQ@mail.gmail.com>
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 >
Received on Wednesday, 1 November 2017 16:53:46 UTC