On Sun, Feb 3, 2008 at 6:56 AM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> Simon Laws wrote: > [snip] > > From what you are saying a short term shopping list of functions seems > to be > > emerging. > > > > Contribution uploader/manager(via browser) > > Contribution addition/management from command line (adding as Luciano > has > > started this and useful for testing) > > Workspace to register added contributions contributions > > Parser to turn workspace contributions into a model that can be > inspected > > (doesn't need the machinery of a runtime) > > Validator for validating contributions in a workspace > > Domain/Node model reader/writer (implementation.node) > > Function for assigning composites to nodes > > Function for processing assigned composites in the context of the domain > > (reference resolution, autowire) (again can be more lightweight than a > > runtime but does needs access to binding specific processing) > > Deployer for writing out contributions for nodes > > > > What else is there? > > > > Simon > > > > Looks good to me, building on your initial list I added a few more items > and tried to organize them in three categories: > > A) Contribution workspace (containing installed contributions): > - Contribution model representing a contribution > - Reader for the contribution model > - Workspace model representing a collection of contributions > - Reader/writer for the workspace model > - HTTP based service for accessing the workspace > - Web browser client for the workspace service > - Command line client for the workspace service > - Validator for contributions in a workspace > > Do you have you heart set on calling this a workspace or are you open to calling it something else like a repository? ...ant
