1. 1 16-May-2005Andy Lawrence : IVOA workshop, Kyoto Roadmap and charge news roadmap issues goals

2. news

3. 3 16-May-2005Andy Lawrence : IVOA workshop, Kyoto IVOA news IAU proposal successful Aug 2006 Prague : put it in your diaries science results focus VO-Event WG underway workshop at Caltech April 13-15 Co-ordinated demos January

4. 4 16-May-2005Andy Lawrence : IVOA workshop, Kyoto project news AVO ended, Euro-VO started Indian VO ending but IVO-TNG expected US-VO operations high priority for NSF AstroGrid released V1.0 science system JVO implemented 3rd gen prototype release of software soon RVO issued formal report RVO-II underway

5. roadmap

6. 6 16-May-2005Andy Lawrence : IVOA workshop, Kyoto Technical Milestones maintained on wiki page late milstones IVOA-IDs UCD1.06 STC1.0 VOsupport interface 1.0 2005 milestones : realistic ?

7. IVOA Calendar since Pune Autumn 2004 - Astro-RG at GGF12, Brussels Oct 2004 - ADASS, Pasadena (no InterOp) Jan 2005 - NVO demo at the AAS, San Diego Jan 2005 - Euro-VO demo event - Madrid, Spain May 2005 - InterOp, Kyoto, Japan July 2005 - Euro-VO data centre workshop - Munich Autumn 2005 - ADASS + InterOp Madrid, Spain May 2006 - Interop (locn ?) Aug 2006 - IAU Prague : VO Symposium Sep 2006 - Interop (locn ?) + small projects meeting Aug 2006 - co-ordinated complex events May 2007 - Interop Sep 2007 - Interop 2008 - major VO meeting ?

8. issues

9. 9 16-May-2005Andy Lawrence : IVOA workshop, Kyoto IVOA issues is the standards process on track ? are we producing what the projects need ? process not always clear reviewed yesterday at Arch. meeting WG reporting WD to PR to R process producing and monitoring milestones

10. The eightfold path (1) create WD-doc (2) debate, revise, implement (3) create PR-doc (4) WG-chair issues RFC to interop@ivoa.net public comments page min 4 week deadline (5) if in doubt, loop to (2) (6) IVOA chair asks Exec to vote (7) Exec votes (8) create R-doc

11. 11 16-May-2005Andy Lawrence : IVOA workshop, Kyoto WG reporting each WG must have clear milestones must be consistent with Technical Milestones for each exec meet and interop : text report progress vs milestones

12. 12 16-May-2005Andy Lawrence : IVOA workshop, Kyoto IG reporting IGs require plan but not formal milestones written report for each interop failure to report for a year triggers query over continuing need

13. 13 16-May-2005Andy Lawrence : IVOA workshop, Kyoto Milestone Review interop reviews progress against TM and develops next milestones aim to issue new TM at end of interop comes bottom up from WGs but routed through IVOA Tech Lead IVOA Tech Lead oversees TM and reviews at each exec meet

14. goals

15. 15 16-May-2005Andy Lawrence : IVOA workshop, Kyoto meeting goals find / resolve WG issues check progress vs milestones refresh WG roadmaps refresh Technical Milestones

16. FIN