On 19/12/14 23:08, florent andré wrote:
Hi Andy, *

Jumping from the "Commons RDF" discussion in Clerezza ml with this
statements :

===
 > I developed the first version of such an API in 2006 when working
 > with the Jena team at HP on a Graph Versioning System. The current
Clerezza
 > API is however substantially different from this with the
contributions of
 > many developers.

You will be pleased to know that HP granted IP rights of GVS, and
derived works, to ASF as part of the Jena software grant.  It had not
been done before.

===

To this question :
Can you say a little bit more on this or link to rtfm documents / code
on what you mean by "graph versioning" here ?

I'm really interesting in this subject and greedy to know what this 2
words means here !

Thanks a lot.

Cheers.

Hi there,

The imported code is hanging around in the imported area.

https://svn.apache.org/repos/asf/jena/Import/Jena-CVS/gvs/trunk/

and some text which seems to be the old web site gvs.hpl.hp.com.

http://svn.apache.org/repos/asf/jena/Import/Jena-SVN/gvs/trunk/src/META-INF/web/application/about-gvs.xhtml

I'm sure there was a HP Labs tech report as well but I can't find that ATM. Maybe it didn't get published.

I wasn't directly involved in the project but from memory ...

The GVS world is (was) a world of many small(ish) graphs. These evolve over time. GVS focuses on the handling of such things, including a lot of use of RDF molecules. This is where the particular take on the role of blank nodes comes from.

Reto did this work.  It has inspired/evolved into some of Clerezza.

New related work: The W3C Linked Data Platform people is very relevant here. Whole graphs are PUT and GETted.

And from the database world, version databases are in the mainstream (MVCC, and immutable persistent data structures (datomics); NoSQL consistency and vector clocks).

        Andy

Reply via email to