Jumps: IvoaResReg :: registry mail archive :: ResourceMetadata :: VOResource :: VODataService :: RegistryInterface
Meetings: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg

Registry Sessions at the May 2008 Interoperability Meeting

Moderator: Aurelien Stebe

Plenary 1 (Monday, 11.00)

Topic Presenter Materials
Status & Goals Aurelien Stebe ppt

Reg 1: Integration and Interoperability (Monday, 14.30)

In this session we will discuss any remaining issues related to our transition to the v1.0 Registry Interfaces standard. If you would like to formally present a report or raise issues, please add your name to the agenda below.

Topic Presenter Materials
Astrogrid status Kevin Benson pdf


Reports by the various Registry Providers :

  • Kevin Benson (Astrogrid) : over a year working, VODesktop using it, support for VOSI, XQuery interface (see presentation for more details).
  • Gretchen Greene (NVO/STScI) : RofR is a big success, watch closely how clients will handle the new multiple capabilities services resources.
  • Matthew Graham (NVO/Caltech) : issue with UTF-8 not correctly encoded on some resources; ask Ray if this can be added to the Validator.
  • Sebastien Derriere (CDS) : Validator is very useful, less resources than before (nearly half, using service-centric, rather than table-centric).
All Registry Providers reported minor glitches with specific resources; (nearly)-all were fixed; was to be expected, nothing too serious.

Talks on the "xsi:type" issue and general namespace short-names :

  • Proposition from Kevin Benson to mandate the namespace short-names (scs:, sia:, ssa:) for easier querying and XPath resolving.
  • Proposition from Aurelien Stebe to use VOStandard to register those in the RofR just like the "standardID".
  • General agreement that it would ease things for many people, and to investigate/test this until next InterOp and report there.

Proposition to have the Validator run periodically instead of single run on registration. Comment by Thomas McGlynn that this is in the work at NVO using Ray's Validator. Comments to have it fill a report page on the RofR webpage or even fill the "validationLevel" element.

Report by Evanthia Hatziminaoglou of the ESO SSAP resource not being transfered correctly to other Registries because of space characters in the identifier. Problem will be resolved after the session.

Thomas McGlynn asking if there is a date planned to encourage client applications implementations to transfer to the new Registries. Consult with Ray Plante.

Confirmation of agreements talked about on the mailing list concerning "deleted" records :

  • "deleted" records are allowed to be actually dropped completely after 6 months
  • GetResource and XQuerySearch are the only two Search methods returning "deleted" resources
  • calls to OAI harvesting methods should return "current" resources (not "deleted") if no date filter is used
Kevin Benson to add those to the RI document before it goes to RFC.

Talks about the "multiple schema versions" issue :

  • Clients must check the namespaces for versions they support.
  • Proposition from Aurelien Stebe to send a mail from the Registry WG to the Applications WG informing application implementors of the issue.
  • Proposition from Gretchen Greene to have the Registry list all the namespaces it might return on a search query inside its resource record.
  • Proposition from Aurelien Stebe to use a test Registry (isolated from the rest) with multiple schema versions for client application tests.
  • List of known client applications using the Registry : VODesktop, Aladin, VOSpec, a VOTech tool (to check).

Reg 2: Registry Extensions (Tuesday, 11.00)

In this session we will primarily discuss the standardization of various registry extension schemas, primarily VODataService and VOStandard. Revisions to VODataService will require an uprev of the schema to version 1.1, so we will also discuss if there are any issues supporting v1.0 and v1.1 simultaneously.

Topic Presenter Materials
Intro, versioning schemas Aurelien Stebe ppt
VODataService Guy Rixon see end of TWiki page
for proposed schema


A question on keeping or not "SkyNode" in the schema roadmap started a review of the schema responsibilities :

  • SimpleConeSearch and SimpleImageAccess will be completed and pushed to REC status by the Registry WG.
  • SkyNode is also under the Registry WG, but the effort to make it a REC will be reviewed when we get to it.
  • SimpleSpectralAccess will be completed and pushed to REC status conjointly by the Registry and DAL WG.
  • All other schema extensions are the responsibility of each Spec authors and should be attached to the Spec.

Presentation (see above PowerPoint file) on the schema roadmap, VOResource TWiki page with extension How-To, "what makes an extension schema IVOA official" and the risks involved in multiple schema versions (see Session 1 Notes above for more infos on this).

Discussions on proposed modifications to the VODataService schema :

  • All proposed modifications on the last slide of above PowerPoint presentation are accepted, except following point.
  • Doug Tody's proposition to change "table" 's "role" attribute is postponed, depends on the result of the TAP discussions. (questions on the utility of the table/view separation)
  • Matthew Graham proposed to add an optional "responseURL" to the "sampleQuery" pointing to the expected result -- accepted.
  • Guy Rixon presented more substantial modifications for the TAP/QL protocol (see schema posted on above VODataService TWiki page). (confusion on astro- / database- usage of "Catalogue")
TAP required modifications will be reviewed further and follow the protocol evolutions and discussions over the summer.

First half of discussion on Gretchen Greene's proposition to add an optional ADQL/VOTable search query method to the Registry interface. The idea is to have something similar to TAP query using the SELECT part of ADQL with XPaths/UTypes in String form, getting the result in flat VOTable for easier client access to simple Resources common values. The RM values returned would be queried for, not determined by the Registry. Agreement it is an interesting idea, with quite a few technical difficulties. Further talks in Session 3.

Joint Session: VOSI (Thursday, 16.30)

See the Grid and WebServices page

Reg 3: Future Directions (Friday, 9.00)

Topic Presenter Materials
Controlled Vocabularies with Registries Norman Gray pdf
Astronomical Visualization Metadata (AVM) Aurelien Stebe ppt
Future of ADQL for Registries Aurelien Stebe ppt


Plenary 2 (Friday, 14.30)

Topic Presenter Materials
Status & Report Aurelien Stebe ppt

Edit | Attach | Watch | Print version | History: r15 < r14 < r13 < r12 < r11 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r12 - 2008-06-10 - AurelienStebe
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback