History for DataModelingRedux

??changed:
-
DataModelingRedux

  Integrating with the openacs, bring alot of questions to how best to model the system. Specifically integration with the Content Repository (cr) for versioning, Permissions integration and workflow. i've tenatively decided against using the cr and just subclassing from acs_object to provide services on a one by one basis.

  Entities

    - Package - represent a python package with associated metadata (description), etc.
  
    - Package Versions
  
    - Package Files
   
    - Authors

    - Vendors
  
    - Maintainers

    - Licenses

    - Dependencies

    - Categories

    - Keywords
  

  an example data model can be found in the snapshot linked from DataModel

  remaining questions (ignored for the moment), is it useful to have a package
  serve as a container (distribution) for other packages like 4suite. this
  still constitutes an extremely small percentage of packages. Also this could 
  solved by having package aliases.