coodbms 0.7.1, reworing the Journal

Lots of refactoring today. CNode (which is the base class for all Rolonic Elements) now supports the dynamic creation of both persistent and transient attributes.

The RoleML script and the Document Rolon Model now both support the creation and assignment of values to Entries, as well as the methods for arranging an ordered map app.

Sample 2 has now been converted to using JTransaction and the RoleML script.

Things are looking up, but I am not at all satisfied with the Journal. You can't look at a Rolon's JUnit and get much of a clue as to what changes have been made. Here's the new plan:

• Each JRolon will have a CSec with symbolic links to all the Rolons which it updated.
• When a Rolon is updated, a JSec is created.
• For each Action (DEnt) which is evaluated, a JEnt is added to the JSec. This JEnt reflects the change that was made by that action.

The JSec will have the same headline as the JRolon and will give you some idea of the intent of the transaction, while the JEnts under the JSec will give the particulars of the actions applied to that Rolon when the JRolon was executed.

The hope here is that this will not require any extra effort when writing a RoleML script, and yet it should fully document the effect that script had on each of the Rolons which are updated by that script.