We need something to define object types and content repository content types to allow for dynamic forms. The CMS package added its own table to manage the widget definition and datatypes for dynamic forms.
This is not generic (obviosuly) and we already have acs_attributes which mostly does this job. Acs_attributes is also used to define the covenience views for content repository content types.
Steps to fix acs_attributes:
Synchronize acs_attributes datatypes with acs-templating/form builder datatypes
This is the main issue I think.
Extend acs_attributes to define a default widget? Or should we create a new table, that includes the attribute_id, widget_name and a context field, so we can define different widgets based on how the attribute is being used.
Should we also examine the skinny storage spec http://www.collaboraid.biz/developer/skinny-spec in relation to acs_attributes role as generic storage?
