Registry Extension Schemas

1
Registry Extension Schemas
THE INTERNATIONAL VIRTUAL OBSERVATORY ALLIANCE

• VODataService
• VOStandard

19 May 2008 IVOA Interoperability Meeting --
Trieste
2
Standards Dependencies
RM
Identifiers
Astronomical Visualization Metadata (AVM)
VOResource
Registry Interfaces (RI) (incl.
VORegistry, RegisryInterface)
VODataService
VOApp
VOStandard
SCS
SIA
SkyNode
SSA
TAP
VOEvent
Recommendation Working Draft Working Draft (xml
only)
Note In Development
depends on
This that
19 May 2008
IVOA Interoperability Meeting -- Trieste
3
All About Extending VOResource

• New Twiki Page VOResource
• Resources for developers, spec editors
• Includes How-to on Extending VOResource,
  presented at past Interops.
• What makes an official IVOA extension?
• Schema posted to http//www.ivoa.net/xml by WG
  chair
• First posted as WD to enable coordinated app
  development across IVOA
• It is expected that every IVOA schema will go
  through the IVOA process via a prose document

19 May 2008
IVOA Interoperability Meeting -- Trieste
4
Evolving Resource Schemas

• We are proposing changes to VODataService
• Will go into v1.1
• Will necessitate changes/up-rev to SIA,
  ConeSearch, SSA, etc.
• Not all registries will upgrade simultaneously
• We will have v1.0 and v1.1 version of resource
  records in system simultaneously
• Are we ready for this?
• If changes are largely backward-compatible (wrt
  tag names, structure), should not cause problems
  for most registries, apps.
• Full registries that have not upgraded to
  recognize new version may treat records just like
  any other unrecognized extension
• Note changes to core VOResource schema are
  trickier
• RI spec refers to VOResource v1.0
• Would require change to wrapper schema
  (RegistryInterface)

19 May 2008
IVOA Interoperability Meeting -- Trieste
5
VODataService changes

• Discussed at previous Interops
• Add ltrightsgt to DataService Resource type
• Add ltsampleQuerygt to ParamHTTP
• Replaces lttestQuerygt in SIA, SCS extensions
• Contains simple query string
• Proposed by D. Tody for TAP
• Replace lttablegts role attribute with type
• Controlled values
• table represents a real, persistent table
  in resource
• view represents a database view
• out table returned in service response
  (e.g. SIA)
• Add ltutypegt as optional column metadatum

19 May 2008
IVOA Interoperability Meeting -- Trieste