Presentation on theme: "26 May 2004IVOA Interoperability Meeting - Boston1 IVOA Registry Working Group VOResource v1.0 Ray Plante."— Presentation transcript:
26 May 2004IVOA Interoperability Meeting - Boston1 IVOA Registry Working Group VOResource v1.0 Ray Plante
26 May 2004IVOA Interoperability Meeting - Boston2 VOResource v1.0 Specification “VOResource: an Encoding Schema for Resource Metadata”“VOResource: an Encoding Schema for Resource Metadata” Objectives –Describe the “core” VOResource Data Model Relationship to RM standard How RM semantics are communicated –Use of xsi:type to identify specific types of resources Describe definition conventions –Describe the VOResource extension mechanism Motivation: adding more specific metadata to describe specific types of resources How to extend –Define specific components of the schema
26 May 2004IVOA Interoperability Meeting - Boston3 Summary of changes All date stamps are UTC –UTCDateTime: Borrowed type definition from OAI –Allows a date or date and time Allow string values to be padded with spaces –To improve readability The Ultimate Resource ADIL Some minor changes in occurrences –Allowing multiple occurrences of certain items
26 May 2004IVOA Interoperability Meeting - Boston4 Issues Registry-modifiable data within a VOResource record –validationLevel Proposed addition to RM Proposed to be rendered as attribute to base Resource type Should this be included in VOResource? –Will we need other registry-modifiable metadata? Should these be separated out of VOResource? Versioning support for VOResource –If there is a v1.1, will registries/applications have to support both versions (v1.0 & v1.1) ?
26 May 2004IVOA Interoperability Meeting - Boston5 VODataService A separately standardized extension Currently describes: –Resource types: DataCollection SkyService, TabularSkyService –Interface types: ParamHTTPGet WebService –Coverage Need to integrate STC –Miscellaneous metadata specific to data & services Issues: –Types sufficiently described? –Add support for registering applications or handle with separate extension? –Need better “coverage” of data and service metadata in RM
26 May 2004IVOA Interoperability Meeting - Boston6 Roadmap VOResource –Settle curation related issues –Move to Recommendation VODataService –Standardize separately from VOResource core as an extension Registry Interface v1.0 (WD) Upgrade registries