From: amirouche <amirouche@hypermove.net>
To: Guile User <guile-user@gnu.org>
Subject: Re: neon: git for structured data [Was: Functional database]
Date: Mon, 05 Mar 2018 23:32:27 +0100 [thread overview]
Message-ID: <1520289147.15975.0@mail.gandi.net> (raw)
In-Reply-To: <3bf20807996ce0bdc4e5ca6ea1d3776f@hypermove.net>
Here is a small update on the neon project.
I implemented what could prolly be called naive
query engine that somewhat follows SPARQL specification.
Remember neon is quad store, that stores a *set* of 4-tuples
that looks like the following:
(graph, subject, predicate, object)
Or in more casual terms:
(namespace, uid, key, value)
It's a *set*. It means you can have that:
("hyperdev.fr" "metadata" "description" "a blog about programming")
And another tuple with another description:
("hyperdev.fr" "metadata" "description" "space muse")
That is (namespace, uid, key) is not unique.
Given that schema, SPARQL is basically pattern matching
scheme over the tuples. The only thing that I plan to add
to this part of the program is filtering because it allows
to speed up the pattern matching in some cases.
I am not sure how to implement OPTIONAL [0] so I leave it
for later.
[0] https://www.w3.org/TR/rdf-sparql-query/#optionals
There is a lot more to do and I am a bit lost about
the goals of the project. neon seems pretty overkill
for a blog engine. I don't have a particular need for
it actually. The idea of building a community that builds
knowledge bases but I am not sure how to proceed.
BTW, forget about the task that I said would be useful
in the previous mail.
I made a small video:
wget http://hyperdev.fr/static/gnu-guile-hacking-15.mp4
The project is still hosted at the following address:
https://github.com/amirouche/neon
Happy hacking!
prev parent reply other threads:[~2018-03-05 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 14:49 neon: git for structured data [Was: Functional database] Amirouche Boubekki
2018-02-21 16:02 ` Roel Janssen
2018-02-21 18:41 ` amirouche
2018-03-05 22:32 ` amirouche [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1520289147.15975.0@mail.gandi.net \
--to=amirouche@hypermove.net \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).