Open GoogleCodeExporter opened 9 years ago
For a proposed version control system see
http://www.ics.mq.edu.au/~cassidy/2007/09/03/version-control-for-rdf-triple-stor
es/
Original comment by rgardler...@gmail.com
on 12 Sep 2008 at 8:13
I have proposed a simal:collected attribute to the schema so that we can track
when a
fact has been collected. This allows us to take a different approach to version
control.
Basically we keep all facts and the date they were collected (along with their
source) we can assume the most recently collected data is the most accurate.
See [Schema] for more details
Original comment by rgardler...@gmail.com
on 26 Sep 2008 at 4:18
Original comment by rgardler...@gmail.com
on 27 Sep 2008 at 11:29
The work on ISSUE 201 has changed the way data is stored. We now maintain a
reference
to the original source of the information. This reduces the necessity for the
data to
be versioned. I'm therefore marking this issue as won't fix until a more
complete use
case emerges.
Original comment by rgardler...@gmail.com
on 21 Nov 2008 at 12:44
This issue is recently discussed on the list [1] and there it is agreed that
it's
usefoul to have the simal:collected timestamp.
I'm reopening this issue, because it hasn't been implemented yet.
[1] http://groups.google.com/group/simal-
contributors/browse_thread/thread/89e00171352243d6/e85a382fbe05cc6a?
lnk=gst&q=195#e85a382fbe05cc6a
Original comment by sander.v...@oucs.ox.ac.uk
on 21 Dec 2009 at 5:02
Original comment by ross.gardler
on 10 Mar 2011 at 12:11
Original issue reported on code.google.com by
rgardler...@gmail.com
on 12 Sep 2008 at 8:07