[Zope-CVS] SVN: zversioning/trunk/notes.txt added names an put notes at the end

[Grégoire Weber]

Log message for revision 28157:
  added names an put notes at the end

Changed:
  U   zversioning/trunk/notes.txt

-=-
Modified: zversioning/trunk/notes.txt
===================================================================
--- zversioning/trunk/notes.txt	2004-10-14 10:53:11 UTC (rev 28156)
+++ zversioning/trunk/notes.txt	2004-10-14 11:00:44 UTC (rev 28157)
@@ -1,32 +1,12 @@
-
-20041010_1100/gregweb
----------------------
-
-Our default policy what is considered part of versioned object is:
-
-  - all attributes that are defined in the schema declarations 
-    at the time of writing to the repository (including the 
-    directly provided ones) are considered to be part of the object
-    by default.
-    
-    The existing mechanism to specify exception of this rule can be
-    found in INonVersionedData
-    
-    XXX How to handle annotations? The current implementation only
-    handles attributes.
-    
-  - Attributes that are not part of a schema declaration are not
-    considered being part of the object all by default
-    
-    There will be an mechanism to specify what attributes shall be
-    included.
-    
-    
-    
-    
 What we did at the IsarSprint
 -----------------------------
 
+Volker Bachs
+Tobias Ahlers
+Markus Reinsch
+Uwe Oestermeier
+Gregoire Weber
+
 Versioning means different things to different people and there is no common optimal 
 solution for all the problems that are related to the history of evolving data.
 Therefore we wanted to provide a flexible framework that is pluggable in its
@@ -37,11 +17,11 @@
 we started by defining the use cases we wanted to address:
 
     Versioning in a groupware with web-based clients and standalone clients
-	CMS Uses Cases: Compound Document
-	Simple Content Versioning
-	Versioning of Proposals
-	
-	see also: http://zope.org/Members/vbachs/UseCases
+        CMS Uses Cases: Compound Document
+        Simple Content Versioning
+        Versioning of Proposals
+        
+        see also: http://zope.org/Members/vbachs/UseCases
 
 We spend a long time to discuss the things we wanted to be pluggable and which
 components were essential. The result of this discussion can be found
@@ -113,4 +93,27 @@
     use cases is more flexibel. So the work from "ui department" shifted to new
     VC
     
-    
\ No newline at end of file
+-----------------------------------------------------------------------
+
+Arbitrary Notes
+---------------
+
+Our default policy what is considered part of versioned object is:
+
+  - all attributes that are defined in the schema declarations 
+    at the time of writing to the repository (including the 
+    directly provided ones) are considered to be part of the object
+    by default.
+    
+    The existing mechanism to specify exception of this rule can be
+    found in INonVersionedData
+    
+    XXX How to handle annotations? The current implementation only
+    handles attributes.
+    
+  - Attributes that are not part of a schema declaration are not
+    considered being part of the object all by default
+    
+    There will be an mechanism to specify what attributes shall be
+    included.
+