IVOA Executive Committee Meeting (FM36)

Sunday May 16 @ 16.00-18.00 - Merino meeting room

Supplementary: May 19 @ 12.30-14.00, possible extension @ 17.00 - Harbour meeting room

---

Logistics

Full Meeting at InterOpMay2010.

Draft Agenda FM36

1. Roll Call and Agenda
2. Minutes of TM35
3. Status of Actions - brief, no discussion
4. Report of the TCG meeting and TCG status - CA
5. Reports by WGs - WG Chairs
6. Approval of new IVOA Recommendation(s) [Standing Item]
7. Discussion on IVOA and Exec (what is IVOA? what is Exec?) - all
8. Discussion on the IVOA structure (Exec, committees, WGs/IGs/LGs, ...) - all
9. IVOA Web pages - AL
10. Interop POC - SG
11. Expiring Chairs - FP
12. Next Interops and Workshops
13. Date of next meeting (TM37)
14. AOB
15. Discussion on Action Items
16. Summary of Actions

Reports from the Projects

ArVO

---

AstroGrid

---

Australia-VO

---

BRAVO

---

China-VO

---

CVO

---

Euro-VO

---

France VO

---

GAVO

---

HVO

---

Japan-VO

---

Korean VO

---

NVO

---

RVO

---

SVO

---

VObs.it

---

VO-India

---

---

Reports from WGs & IGs(follows order as at http://www.ivoa.net/forum/)

---

---

Applications WG

---

Data Access Layer WG

---

Data Models WG

---

Grid and Web Services Working Group

A fortuitous mixture of snatched moments and whimsy has meant that we are broadly on track with our specification schedule:

• The TCG review period for Universal Worker Service (UWS) has ended but we are still awaiting (5/10) approval from a number of chairs, despite repeated coaxing, cajoling and badgering on the TCG list. This seems to be an increasingly common occurrence in the specification process and needs addressing.
• The RFC period for Web Service Basic Profile has ended (4/28) with comments from just one individual which are being addressed. It is difficult to believe that this represents the tacit approval of the rest of the IVOA for this specification. Again we need to engage more comment and review from within IVOA on our specifications and within the specified timescales. A number of specifications have also garnered extensive comment outside of and after the review process - how should this be treated? It seems churlish to ignore it but the process is there for a purpose.
• The RFC period for Support Interfaces (VOSI) has ended (5/14) with comments from two individuals which are being addressed. Again given that this is an integral part of the TAP specification, it is surprising that it has not garnered greater comment or review.
• A new working draft of VOSpace 2.0 has been released (3/23) and reference implementations are being created at CADC, CDS and Caltech.
• There has been some internal discussion about VOPipe.

---

Registry WG

---

Semantics/UCD WG

---

VOEvent

---

VOQL WG

---

VOTable WG

---

Data Curation and Preservation IG

---

Theory IG

---