1. Registry Interop Summary IVOA Interoperability meeting Cambridge, Boston, MA 24-28 May 2004

2. 2 28-May-2004Registry Interop Summary Sessions Session 1 Bob Hanisch: RM update Ray Plante: Resource Schema update Paul Harrison: Questions on Schema structure Session 2 Ray Plante: OAI-based harvesting Kevin Benson: Registry Interface spec Gretchen Green/Wil OMullane: Searchable Registry in NVO Kevin Benson: XQuery-based searching in AstroGrid Matthew Graham: The Caltech NVO Registry Martin Hill: Resource Names vs Locators Session 3 Paul Harrison: Application resource schema in AstroGrid Ray Plante: IVOA Identifiers update Bob Hanisch: Registry Data Curation See InterOpMay2004ResReg wiki page for presentations Thanks to all presenters

3. 3 28-May-2004Registry Interop Summary Session Decisions: General Types are defined in RM Documents are defined in RI Will promote v1.1 of Identifier spec to PR status & thence to REC Implement owned/managed authorityID to cater for Publishing/Full registries

4. 4 28-May-2004Registry Interop Summary Session Decisions: Schema Level of hierarchy will be as in RM v1.01 Switch to type-based schemas (vs subs group) Logical-id will be defined via a second relationship (rather than via direct attribute) Service types as a sub-class of Resource (rather than extending Capability) Organisation type definition will be moved into the base VOResource definitions Referred resources will be via ivo-id attribute The metadata describing a registry will include a flag indicating whether it is a full or publishing registry.

5. 5 28-May-2004Registry Interop Summary Session Decisions: Interface An IVOA Registry must support OAI-PMH protocol for harvesting via HTTP GET, returning at least oai_dc and ivo_vor metadata formats using standard data criteria The IVOA Registry Harvesting protocol will be web service-based and will conform to the full OAI-PMH specification: details will be worked out on the mailing list An IVOA Registry must support the Keyword Search as specified in the RI document An IVOA Registry must support a Full Query facility (interface tbd) using the WHERE clause of the ADQL schema with field names specified using non- namespaced XPath directives (simple, ie no [...] options), and returning full resource entries

6. 6 28-May-2004Registry Interop Summary Roadmap for 2004 Revised RMS v0.10Raydone Revised RI spec v0.11Kevin15 Jun Implement Keyword query interfaceNVO/AGend July Implement Full query interfaceNVO/AGend July Run inter-project harvesting trialsallfrom 01 Aug Trial inter-project query (app reg)NVO/AGfrom 01 Aug Basis for Jan 2005 demos

7. 7 28-May-2004Registry Interop Summary Sept04 Interop meeting Discuss implementations Harvesting Query Determine fix schedule Decide on shape of Jan05 demos wrt Registry Look at: Science Resource / Service split Application resource description SELECT clause in full query from Data Model group: Data Resource description based on (Catalog) DM