[Sugar-devel] Call for testing and feedback: alternative Journal implementation
c.d.m.gueret at vu.nl
Fri May 11 09:41:03 EDT 2012
> For remote access you mean such feature in particular triple storage
> If it is about adding remote access to some of existing triple storage
> implementations, it might be useful to split the work into local part
> (implement reliable/fast/resources-consumption-humble local storage)
> and attaching this storage to the existing formation.
> For example, there is an ongoing work for Sugar Network. It is a
> system of servers (master one and decentralized nodes that can be
> synchronized with each other and with the master one) and clients that
> work with servers via RESTful API. The system should contain arbitrary
> content (indexed in Xapian), e.g, activities, activity objects, books,
> etc. For now, server (node/master) is being implemented as Xapain
> db with key/value storage (like Journal, but filesystem storage might be
> replaced by more regular key/value db in the future). Plus, there is an
> ongoing work for creating client. So, when local triple storage will be
> good enough for being handling on a XO (Sugar Network is being developed
> also for working out offline usecase in schools) and Sugar Network will
> be in more stable stage, RDF storage might replace Xapian.
Thanks for the pointer! I wasn't aware of that Sugar Network initiave. It
is actually the very same thing I am now implementing with some of my
students. We are building a system made of different nodes and using triple
stores. With it, it is (or will be) possible to store abitrary content and
do any kind of query. Our first activity making use of the network will be
a social network application allowing to asynchronously send messages
across schools and between XOs in a mesh. The system will take benefit from
Linked Data principles to uniquely identify every user in the system and
efficiently spread the messages.
Triple stores are close to key/value stores, with the main difference that
they associated two keys for one value. If you set the first key to a
particular value, for instance one that refers to a particular journal
entry, and then iterate over the other key/values you get something similar
to any other key/value store. Currently, that is how the triple-store based
journal is implemented: one new resource per journal entry and one triple
per key/value of the entry. Every entry is then wrapped into a named graph
which is the basic unit transfered across XOs.
I will read more about Sugar Network and see how to related SemanticXO with
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel