...
- About the OpenMI: What is it ? (10 lines + hyperlinks to) check/update RVM due 31/12/07
- How did we emerge: History (web) check/update RVM due 31/12/07
- Who are we: The Association (web) check/update RVM due 31/12/07
- What it is: Scope (Layman's report, 5-10 p., web (and PDF), target: managers/anyone without technical expertise in this domain) due 31/01/08
- Where are we heading: Strategy (PDF, 10 p, target: managers+OA-members), action OAEC, sketch due 16/11/07, draft 31/01/08, final 28/02/08
- What is it (details): OpenMI: The basic concepts (web (and PDF), subset of B, max. 20 p, target: (managers)/consultants/developers) v2. due 01/07/08
- How can you use it : Examples using the Standard (fact sheets of 2-4 page per use case, web+PDF, target: managers/consultants)
- template due 30/11/07
- examples taken from subset of doc.B, OpenMI-Life, consultants, US-webservices, etc. first set due 31/01/08
- Leaflets (folded double sided A4, for dissemination at conferences)
- OpenMI Association (action RVM+SM, NTUA for styling and publishing) due 01/04/08
- OpenMI Standard (update Harmoni-ca leaflet, action RVM+SM, NTUA for styling and publishing) due 01/04/08
- Newsletters
- Use cases of the OpenMI
- Posters
- OpenMI Association (action NTUA+RVM) due 01/04/08
- OpenMI Standard (action NTUA+RVM+JBG) due 01/04/08
...
- Charter (content done, formatting needed, action CIT+SM)
- Standing Orders (content ongoing, action RVM to complete, RVM+SM to format)
- Strategy {content draft on wiki, all to review, OAEC to approve, RVM+SM to format) draft 31/01/08, final 28/02/08
- Implementation plan (content to be setup, depends on strategy outcome, action OAEC)
- Procedures
- produce template (1 page) action SM
- standard upgrade procedure (content OAEC ongoing)
- software release (content OATC ongoing)
- change requests (content OATC ongoing)
- test and component acceptance (content OATC ongoing)
- document and website management
- membership administration
...