1. 27 October 2008 IVOA Interoperability Meeting -- Baltimore T HE I NTERNATIONAL V IRTUAL O BSERVATORY ALLIANCE Resource Registries Opening Plenary Registry Search Issues Extension Schemas Publishing Interfaces

2. 27 October 2008IVOA Interoperability Meeting -- Baltimore Registry Sessions Reg 1: Tuesday 8.30 – 10.00 –Search Interfaces Registry Interfaces v1.0 Issues TAP/VOTable-based advanced searching Search techniques from the user perspective Reg 2: Tuesday 15.30 – 17.00 –Extension Schemas VODataService VOEventStream –Publishing Interfaces Common publishing toolkit? Apps/DM/Reg Joint Session: Thursday 8.30 – 10.00 –General Cross-cutting Issues –Astronomical Visualization Metadata (AVM) GWS/Reg/DAL Joint Session: Thursday 13.30 – 15.00 –VOSI

3. 27 October 2008IVOA Interoperability Meeting -- Baltimore Standards Dependencies RMIdentifiers VOResource Astronomical Visualization Metadata (AVM) VODataServiceVOAppVOStandard Registry Interfaces (RI) (incl. VORegistry, RegistryInterface) SCSSIASkyNodeSSA VOEventStream TAP Recommendation Proposed Rec Working Draft Working Draft (xml only) Note In Development This that depends on

4. 27 October 2008IVOA Interoperability Meeting -- Baltimore Standards Dependencies RMIdentifiers VOResource Astronomical Visualization Metadata (AVM) VODataServiceVOAppVOStandard Registry Interfaces (RI) (incl. VORegistry, RegistryInterface) SCSSIASkyNodeSSA VOEventStream TAP Recommendation Proposed Rec Working Draft Working Draft (xml only) Note In Development This that depends on

5. 27 October 2008IVOA Interoperability Meeting -- Baltimore Search Interfaces Registry Interfaces v1.0 RFC status –On-going: scheduled to end Nov 9 –Will probably be extended slightly –Issue for discussion: Required advanced search interface depends on ADQL/x v1.0 Is this wise? How should we address this? –Make optional? adopt ADQL v1.0? Other approaches to searching –Norman Gray: approaches to searching in AstroGrid –Gretchen Greene: TAP/VOTable-based interface

6. 27 October 2008IVOA Interoperability Meeting -- Baltimore Extension Schemas VODataService –For describing data collections and services that access them Particularly std. DAL services: SIA, SCS, SSA, TAP –Key to the VO Support Interfaces (VOSI) VODataService: defines metadata for describing tables VOSI can provide ability to pull table metadata directly from the service –Interdependencies: TAP – VODataService – VOSI VOEventStream –Developed by VOEvent WG

7. 27 October 2008IVOA Interoperability Meeting -- Baltimore Publishing Interfaces Would a shared, open toolkit be useful? –Biggest Challenge: getting metadata out of publishers brains and into XML NVO Universal Publishing Interface –A publishing interface that can be attached to any registry –Theresa Dower: demonstration Benefits of an open toolkit –Plugin helpers for generating metadata –Sebastien Derriere: ideas for semantics-based assists

8. 27 October 2008IVOA Interoperability Meeting -- Baltimore Astronomical Visualization Metadata (AVM) For tagging graphical images for outreach purposes. –Developed by VAMP project Discussed extensively via the observatory outreach community –RWG charge: submit to IVOA process Status since Trieste: –application development to exercise –IVOA document version submitted to RWG Will review in Apps/DM/Reg joint session

9. 27 October 2008IVOA Interoperability Meeting -- Baltimore Registry Standards Roadmap In RFC: –Registry Interfaces v1.0 Ready after Baltimore: –VODataService –AVM Next in Queue –DAL service support: SCS, SIA, SSA –VOApp –VOStandard Active collaborations –VOEventStream –TAP

10. 27 October 2008IVOA Interoperability Meeting -- Baltimore VOSI: Joint Session with DAL, GWS VO Standard Interface (VOSI) –Provides ability to get metadata directly from services –Capability metadata: interface and how it behaves –Table metadata: table & column descriptions –Looking to move to PR after Interop Registries harvest metadata from services –Reduces what publisher provide by hand –Registries choose which metadata to index –VOSI is key to addressing coarse vs. fine grained registry issue