Content API Introduction
A long time ago Bill and I started talking about the item system (which by the way Microsoft is doing something similar with WinFS), however that project never went anywhere due to time and all that. In any case, with the 2.0 restrucutre, i felt it a good oppertunity to get back to work on the super CMS API. (Content Portion of the API).
Basically the conent API would remove the need for most modules to define their own sql, or datastore, and in most cases even properties. Thus making the pocess of making a content item for rainbow much simper. Also, there are some other things, becuase anythign really can be an item it offers things like permissioning, hierachry, relationships, searching and more ( it doesnt offer it all yet, but that is the final goal ). For a smaple of an "item" as it is currently, not really functional, mostly just place holders have a lokg at the following diagram.
The goal would be a release of say a version 1 of the content api sometime around alpha 7 or 8 to see if its workable in replacing most of the content in the core.
The content api would use the datastore provdier weather that be db provider, nhibernate or ibatis. since the api would handle all persistnce mehtods, changing between this would be rudementary, and can even be made options.