Presentation is loading. Please wait.

Presentation is loading. Please wait.

19 May 2008 IVOA Interoperability Meeting -- Trieste T HE I NTERNATIONAL V IRTUAL O BSERVATORY ALLIANCE Registry Extension Schemas VODataService VOStandard.

Similar presentations


Presentation on theme: "19 May 2008 IVOA Interoperability Meeting -- Trieste T HE I NTERNATIONAL V IRTUAL O BSERVATORY ALLIANCE Registry Extension Schemas VODataService VOStandard."— Presentation transcript:

1 19 May 2008 IVOA Interoperability Meeting -- Trieste T HE I NTERNATIONAL V IRTUAL O BSERVATORY ALLIANCE Registry Extension Schemas VODataService VOStandard

2 19 May 2008IVOA Interoperability Meeting -- Trieste Standards Dependencies RMIdentifiers VOResource Astronomical Visualization Metadata (AVM) VODataServiceVOAppVOStandard Registry Interfaces (RI) (incl. VORegistry, RegisryInterface) SCSSIASkyNodeSSA VOEvent TAP Recommendation Working Draft Working Draft (xml only) Note In Development This that depends on

3 19 May 2008IVOA Interoperability Meeting -- Trieste 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 by WG chairhttp://www.ivoa.net/xml –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

4 19 May 2008IVOA Interoperability Meeting -- Trieste 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)

5 19 May 2008IVOA Interoperability Meeting -- Trieste VODataService changes Discussed at previous Interops: –Add to DataService Resource type –Add to ParamHTTP Replaces in SIA, SCS extensions Contains simple query string Proposed by D. Tody for TAP –Replace s 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 as optional column metadatum


Download ppt "19 May 2008 IVOA Interoperability Meeting -- Trieste T HE I NTERNATIONAL V IRTUAL O BSERVATORY ALLIANCE Registry Extension Schemas VODataService VOStandard."

Similar presentations


Ads by Google