Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

News

2007 Dec 20

The Registry of Registries is now available for validating and registering your registry. You can also view the currently registered registries. See the Software Tools and Testers section below for more information.

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

--IVOA.RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries:
  • Documentation: IVOA Note
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr/oai.pl
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate and register your registry at http://rofr.ivoa.net:8080/vovalidation/regvalidate.html
  • view currently registered Registries

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

News

2007 Dec 20

The Registry of Registries is now available for validating and registering your registry. You can also view the currently registered registries. See the Software Tools and Testers section below for more information.

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

--IVOA.RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries:
  • Documentation: IVOA Note
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr/oai.pl
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate and register your registry at http://rofr.ivoa.net:8080/vovalidation/regvalidate.html
  • view currently registered Registries

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

--IVOA.RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• • Documentation: IVOA Note
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr/oai.pl
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries: Preliminary release
  • Documentation: IVOA Note
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr/oai.pl
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate your registry at http://nvo.ncsa.uiuc.edu/rofr/check.html
  • registration coming next.

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries: Preliminary release
  • Documentation: IVOA Note
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr/oai.pl
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate your registry at http://nvo.ncsa.uiuc.edu/rofr/check.html
  • registration coming next.

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries: Preliminary release

• • • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate your registry at http://nvo.ncsa.uiuc.edu/rofr/check.html
  • registration coming next.

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate your registry at http://nvo.ncsa.uiuc.edu/rofr/check.html
  • registration coming next.

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.

• • • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate your registry at http://nvo.ncsa.uiuc.edu/rofr/check.html
  • registration coming next.

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

Action	When	Comments <-- -->
updated versions schemas	done	see schema section below
conversion stylesheet available	done	see below
updated draft of RI spec	done	see attachments at RegistryInterface
complete implementations of RI v1.0	30-Apr-2007
general testing period begins	01-May-2007
discuss remaining interoperability issues at IVOA mtg.	14-May-2007
new registries "turned on"	01-Jun-2007
achieve stability	15-Jun-2007
Registry of Registries ready	06-Apr-2007	(Ray)

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry in a Box, v2.0: riabox-2.0rc2.tar.gz
  • Enhancements on the commonly used OAI libraries from Virginia Tech that understands the RI profile on OAI.
  • Allows configuration for compliant OAI responses:
    • returning the Registry VOResource record in Identify response
    • define, document, and configure sets
    • show support for ivo_vor metadata prefix
    • support required oai_dc format with stylesheet from VOResource format.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
    • implemented using Registry-in-a-box above.
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate your registry at http://nvo.ncsa.uiuc.edu/rofr/check.html
  • registration coming next.

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr

• • Fully v1.0 compliant
  • can be used to test Harvesting
  • validate your registry at http://nvo.ncsa.uiuc.edu/rofr/check.html
  • registration coming next.

• VOResource validating stylesheet: validateVOResource.xsl
  • this style sheet will run VOResource compliance checks that are not covered by the VOResource schemas
  • understands extension types defined in these extension schemas
    • VORegistry
    • VODataService
    • ConeSearch
    • SIA
    • SkyNode
  • By default it will only report on problems found with a text output.
  • Useful optional input parameters include (see in-line documentation for more detail):
    • requireRI: set to 1 if you want to ensure that the VOResource records is wrapped in the <ri:Resource> element as required by the RI standard.
    • rightnow: set to the current date and time (in ISO format) to ensure that all dates are in the past.
    • showStatus: set to "fail warn rec pass" to include reports on passed tests; the default is only to report failures, warnings and recommendations.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
  • Fully v1.0 compliant
  • can be used to test Harvesting

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: The samples above were created to be compliant only with the VOResource schema and the above extensions. These would have a different wrapping or "root" element (namely, the <ri:Resource> element) when used as part of a Registry service, the details depending on the type of message; see the RI spec for specifics. (I'll try to update these with Registry-specific versions to avoid confusion --rp)

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • registration and registry checking coming next.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • registration and registry checking coming next.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

See VoResourceConversionXSL for more info, including Caveats, available input parameters, and a list of recent changes.

-- RayPlante - 17 April 2007

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • registration and registry checking coming next.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap

Please update this schedule as necessary. The initial dates have been taken from the roadmap described in InterOpMay2006ResReg and are subject to change pending discussion by the WG.

We are strongly encouraging registry providers to maintain the old registry interfaces beyond the "change-over" date to support existing applications. Note, however, that after the switch, the old interfaces may not continue to be updated.

Meetings and Discussion

• Registry Provider Telecon, 14 June 2006: Minutes
• Moscow Interop Meeting: InterOpSep2006ResReg

Standard Schemas and WSDLs

VOResource Schemas and Example Instances (Release Candidate 11 2006-11-07)

The VOResource core schema is documented in the Working Draft, VOResource: an XML Encoding Schema for Resource Metadata. The current version under review is VOResource-20061107; the associated Schema files is available at both at http://www.ivoa.net/xml/ and below.

All of the schemas and examples can be downloaded together: VOResource-v1.0.tar.gz, VOResource-v1.0.zip.

Individual examples:

Several of the examples use STC which requires stc-v1.30.xsd and xlink.xsd.

Note: Prior to 26 June, several of the schemas had versions set to 0.9; they have now been elevated to v1.0.

-- RayPlante - 5 April 2007

Interface WSDLs

A version 1.0 of the RI spec has been submitted to the IVOA document repository. There is a small errata plus an internal WD waiting in the wings on the RegistryInterface twiki page. Consult this document for examples of how to include VOResource metadata within the interface messages.

The RI specification defines 2 WSDL files--one for the search interface and one for the harvest interface. Both import a common RegistryInterface schema. These are available here:

• RegistrySearch-v1.0.wsdl
• RegistryHarvest-v1.0.wsdl
• RegistryInterface-v1.0.xsd

More info about the RI spec, including getting Kevin's last bundle of WSDLs and Schemas, conult the RegistryInterface page.

Remember: The WSDL/SOAP-based Harvesting interface is optional; if your registry is harvestable, the standard GET-based version of OAI is required.

XSL conversion stylesheets

For v1.02 (Release Cand. 11):

VOResource-v0.10-v1.0.xsl2

XSL stylesheet for converting v0.10 to v1.0 records. (Updated 5 April 2007)

This stylesheet requires an XSLT 2.0 processor, such as the Saxon engine, available in saxon8.jar. To run, type:

java -jar saxon8.jar resource-v0.10.xml VOResource-v0.10-v1.0.xsl2 > resource-v1.0.xml

where resource-v0.10.xml is the v0.10 resource record to convert.

Software Tools and Testers

• ivoaregistry: a registry search Java library and tester.
  • Download as a zip file: ireg-linux.zip
    • "linux" means the command line wrapper script is for *nix OSes; the Windows version is not yet included.
    • It is pre-built, but can be re-built with ant
    • Requires at least Java 1.5
  • The net.ivoa.registry.search.RegistrySearchClient class provides a Java API to the standard IVOA Registry Search Interface.
  • The regsearch command line tool can be used to test the interface
    • to install, first run "bin/install_tools"
    • see top section of bin/regsearch for usage details
    • it's still a little clunky for using in scripts.

• Registry of Registries: Preliminary release
  • OAI interface at http://nvo.ncsa.uiuc.edu/cgi-bin/rofr
  • Fully v1.0 compliant
  • can be used to test Harvesting
  • registration and registry checking coming next.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Upgrade to Registry Interface v1.0 (Spring 2007)

This page will provide useful information for registry providers regarding the upgrade schedule, upgrade requirements, links to schemas and tools, etc.

Contents

Roadmap