COOL! That sounds great! Thanks for listening!
On Jun 17, 2009, at 7:10 PM, Jack Schwartz wrote: <snip> > The terminology isn't quite accurate, but after the meeting today, > it changed again anyway. It is simpler now. One manifest with > three sections: criteria, installation, configuration. Either or > both of the latter two sections can be populated with data, or a > pointer to a file containing the data. >> >> I think the proposal you have currently works very well in the >> 'scaling to a wide variety of systems'. > Thanks. We kept the option of having pointers to files to those > last two sections for scalability. >> >> One thing we have talked about is making it easier for users to use >> AI out of the box. To setup services and understand what the client >> behavior will be. Is simply making the manifest(s) easier to edit a >> possibility to ease the learning curve? Do we know of an XML editor >> that might be useful for this? > We thought that having many files and incomplete examples would make > it harder for users to learn. > > We will be proposing working examples for a single, self-contained > manifest; and a manifest with pointers to files containing the > installation and configuration sections. These will be fully > commented, and list all fields to serve as an example. They will > also work - out of the box. Users can start with these and tweek > them as needed. > > I'll be posting meeting minutes tomorrow and a revised functional > spec as soon as I can. > > <snip>
