Hi Chris, OpenLink has been working on this, as Kingsley noted. However, in the meantime, here's an idea. I used it for a small scale project that needed a similar feature over one year ago.
Add triggers to the RDF_QUAD table ( I'm talking SQL here ). Use these triggers to append each transaction to a log table ( g, s, p, o, add/remove flag, timestamp ) You can quickly move the RDF_QUAD table back and forth to a certain point in time by replaying this log table or by executing a "select + insert". You can always keep more than one RDF_QUAD tables and just rename them as needed. SPARQL will always execute against the one named RDF_QUAD. In fact, in theory ( I have not tried this one ), the RDF_QUAD table could be a view atop the RDF_QUAD_LOG table that filters on an additional flag: is_valid. Of course this is not cheap neither built-in, it is rather a hack thanks to the fact that Virtuoso is a very transparent "environment" rather than a one off tool. Working with RDF_QUAD can take you to strange, but useful, places ;) Besides time travel, having a built-in way to audit graph changes ( with timestamp, user and an optional message ) would be really useful. I think lots of different configurations of the quad store should be possible depending on a user's needs and performance requirements. Regards, A On Sat, Jun 26, 2010 at 3:33 PM, Chris Wj <[email protected]> wrote: > Would I be able to sparql query the graph as it was at a particular point in > the past? > > On Sat, Jun 26, 2010 at 10:50 AM, Kingsley Idehen <[email protected]> > wrote: >> >> Chris Wj wrote: >>> >>> Is there a way to specify versioning (tracking changes) for a particular >>> rdf graph uri? I don't need it for all RDF, but for certain named graphs, I >>> want to be able to evaluate the change over time. >>> >>> -Chris >>> ------------------------------------------------------------------------ >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Sprint >>> What will you do first with EVO, the first 4G phone? >>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Virtuoso-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users >>> >> >> Chris, >> >> Yes, this is what our delta-engine + replication is all about. >> >> Changes get replicated between Virtuoso instances, automatically. In >> addition, you have access to the deltas. >> >> Live example here (note the deltas link): >> http://dbpedia-live.openlinksw.com/live >> >> >> >> -- >> >> Regards, >> >> Kingsley Idehen President & CEO OpenLink Software Web: >> http://www.openlinksw.com >> Weblog: http://www.openlinksw.com/blog/~kidehen >> Twitter/Identi.ca: kidehen >> >> >> >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Virtuoso-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtuoso-users > > -- Aldo Bucchi @aldonline skype:aldo.bucchi http://aldobucchi.com/ PRIVILEGED AND CONFIDENTIAL INFORMATION This message is only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If you are not the intended recipient, please do not distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail.
