Registry Interface

Registry Interface Specification

This page is dedicated to defining a standard query and harvesting interface.
This will allow the communication between registries to be a standard, and allow external implementations that need access to a registry a standard for querying the Registry. Understand this document is still evolving.

Internal Working Draft: Registry Interface (.pdf, .doc)

WSDL & Schema: .zip - this download has all the Schemas and WSDLs necessary to generate stubbs locally if desired.

Specification Discussions

The RegistryInterfacePre10Discussion page presents several topics that we could use feedback on, including ...

1. Would it be useful for the harvesting interface to have a switch that allows harvesters to choose whether to get all records versus only thoses that originate from the harvestee?
2. Should make the harvest() function independent of the searchable interface?
3. Should we drop getRegistries() or redefine it?
4. Should we add a harvestFrom attribute to the VOResource schema?
5. How should we handle namespace prefixes in ADQL queries?

Click on the topic question to see a more detailed description and discussion.

Prototyping Issues

We are gathering issues and comments regarding harvesting on the HarvestingIssues page. -- RayPlante - 11 Mar 2005

ADQL to SQL Parsing

An XSLT stylesheet for converting ADQL v1.0 to SQL can be downloaded here : adql2sql_v10_registry.xsl.
This file should work just fine for v0.9 and v0.8, just by changing the namespace declaration.
Note that the xPath expressions still need to be converted to your database column names. -- AurelienStebe - 23 Aug 2005