- From: Stephane Corlosquet <stephane.corlosquet@deri.org>
- Date: Sun, 26 Apr 2009 19:06:43 +0100
- To: Peter Krantz <peter.krantz@gmail.com>
- CC: Dan Brickley <danbri@danbri.org>, foaf-dev Friend of a <foaf-dev@lists.foaf-project.org>, foaf-protocols@lists.foaf-project.org, Semantic Web <semantic-web@w3.org>, Thomas Roessler <tlr@w3.org>
In the case where the data is file based, using a Version Control System [1] should help a great deal in both of these areas, since a history is available and it makes it possible to track back or restore data. However, typical centralized revision control can be vulnerable if the server hosting the repository is compromized. To solve this, decentralized revision control [2] can increase the robustness due to its peer-to-peer approach. regards, Stéphane. [1] http://en.wikipedia.org/wiki/Revision_control [2] http://en.wikipedia.org/wiki/Revision_control#Distributed_revision_control Peter Krantz wrote: > Hijacking this thread back to the original topic: > > How can we help? Two important areas to start working with: > > 1. How to get your servers back online in a clean uninfected state and, > > 2. how do we provide security recommendations for people who publish > semweb data online? > > Anyone who is willing to help out? > > Regards, > > Peter Krantz > >
Received on Sunday, 26 April 2009 18:07:43 UTC