1. VOTable 2005 Discussion Summary and Roadmap

2. Agenda http://ivoa.net/twiki/bin/view/IVOA/InterOpMay2005VOTable Description of some applications dealing with VOTable interpretation/transformation Description of some applications dealing with VOTable interpretation/transformation Nilesh UrunkarAbout C++ Parser and CONVOT Nilesh UrunkarAbout C++ Parser and CONVOT Mark TaylorAbout STIL/STILTS/TOPCAT Mark TaylorAbout STIL/STILTS/TOPCAT Improvement of the VOTable schema Improvement of the VOTable schema Gerard LemsonAbout VOTable Schema Gerard LemsonAbout VOTable Schema

3. Agenda (continued) UCD1, UCD1+ and utype in VOTable UCD1, UCD1+ and utype in VOTable Sebastien DerriereAbout UCDs and utype Sebastien DerriereAbout UCDs and utype Jonathan McDowellComment on utype Jonathan McDowellComment on utype Coordinate system in VOTable Coordinate system in VOTable Arnold RotsAbout simple STC, LinearSTC? Arnold RotsAbout simple STC, LinearSTC? Discussion on implementations Discussion on implementations Open Questions Open Questions Other datatypes (dateTime, string,...) Other datatypes (dateTime, string,...) Future of the VOTable group ? Future of the VOTable group ?

4. VOTable interpretation/transformation Interpret all serializations Interpret all serializations streaming / non-streaming modes streaming / non-streaming modes full validator (not schema only) full validator (not schema only) graphical interfaces available graphical interfaces available VOTable mature & widely used VOTable mature & widely used

5. Changes in VOTable schema Construct closer to Java binding, no global element Construct closer to Java binding, no global element Single inheritance mapping, only extension, no substitutionGroup Single inheritance mapping, only extension, no substitutionGroup Change in VOTable schema, with PARAM inherited from FIELD (v1.11) (need for a Proposed Recommendation / Recommendation path ?) Change in VOTable schema, with PARAM inherited from FIELD (v1.11) (need for a Proposed Recommendation / Recommendation path ?)

6. UCD1 / UCD1+ / utype Some applications still use (old) UCD1 syntax. Some applications still use (old) UCD1 syntax. make clear from next version (1.12 or 1.2?) that UCD1+ syntax only is valid make clear from next version (1.12 or 1.2?) that UCD1+ syntax only is valid utype represents a pointer to some parameter of a data model utype represents a pointer to some parameter of a data model use XPath-like syntax (write a short formal document with DM?) use XPath-like syntax (write a short formal document with DM?)

7. Various questions Mime type for VOTable application/x-votable+xml (experimental) Mime type for VOTable application/x-votable+xml (experimental) Concepts of primary/foreign keys in VOTable (or in extension schemas?) Concepts of primary/foreign keys in VOTable (or in extension schemas?) other datatypes (date/time, string) not yet (FITS compatibility) other datatypes (date/time, string) not yet (FITS compatibility)

8. STC in VOTable In VOTable coordinate system currently defined by a dedicated In VOTable coordinate system currently defined by a dedicated to be replaced by STC definitions in order to keep common model across VO components to be replaced by STC definitions in order to keep common model across VO components Some problems in STC import in VOTable context Some problems in STC import in VOTable context

9. The STC problems fine but fine but necessity of defining unused systems (TimeFrame, SpectralFrame, RedshiftFrame) necessity of defining unused systems (TimeFrame, SpectralFrame, RedshiftFrame) could be referenced via a utype ? could be referenced via a utype ? problems: problems: Epoch need frequently to be defined Epoch need frequently to be defined Possible conflicting units with (interpret as default unit?) Possible conflicting units with (interpret as default unit?) Actual values are deferred via which has to reference a vector of 2 numbers (in VOTable it's necessary to reference the other way around) Actual values are deferred via which has to reference a vector of 2 numbers (in VOTable it's necessary to reference the other way around)

10. Possible solutions (private discussion A. Rots) Define the position as a VOTable referencing the part Define the position as a VOTable referencing the part what happens if one component of position is missing (e.g. Dec in meridian observations) what happens if one component of position is missing (e.g. Dec in meridian observations) Refine the utype syntax to reference individual components of the STC model Refine the utype syntax to reference individual components of the STC model Other solutions (include STC within a VOTable ?) Other solutions (include STC within a VOTable ?)

11. STC in VOTable: Roadmap Proposal need to be discussed between VOTable and DM (toward a VOTable V1.2) Proposal need to be discussed between VOTable and DM (toward a VOTable V1.2) possible solutions written down in June possible solutions written down in June discussions in summer/september discussions in summer/september report in Madrid report in Madrid