VizieR example (use Param in interface)

[gilleslandais]

This is an example of vizier record which contains several tables.
Param applyed to interface allows to link the Conesearch service with the table definition

[msdemlei]

On Thu, Jul 02, 2026 at 09:19:55AM -0700, gilleslandais wrote: This is an example of vizier record which contains several tables. Param applyed to interface allows to link the Conesearch service with the table definition

Thanks for that; I think that's a valuable addition, both in terms of features and in terms of complexity (including mirrorURLs). One point, though: I've long been pained by the lack of quotes in VizieR table names. This is a pain that TOPCAT works around emitting warnings and that will to this day break query generation when using pyVO (without doing funny guesswork); see also my Malta talk <https://wiki.ivoa.net/internal/IVOA/InterOpNov2024Apps/volimits.pdf>. VODataService itself says: When the table set describes a set of TAP-accessible tables, the value of a table’s name child must be in a form immediately usable for use in ADQL or SQL queries. This corresponds to the analogous requirement for TAP_SCHEMA. This means that all qualifications (schema, catalogue) must be present, but also that when delimited identifiers are used as table names on the relational side, the quotes must be part of name’s value, and the capitalisation used in the DDL must be preserved. This means that in the tableset, you have to say <name>"J/AJ/151/120/table2"</name> and in consequence in stats: <option>"J/AJ/151/120/table2"</option> I can understand that you probably don't want to switch TAPVizieR immediately (presumably some folks have workarounds for the missing quotes that will break when they are there). But at least in an example file for the very standard that mandates the quotes they need to be there. Also, if you introduce the example with a brief comment on why it's there, that'd be great, perhaps something like: <!-- Noteworthy in this example is the use of stats on the SCS2 TABLE parameter that links the particular service with the table it queries. While this is a use particular to SCS2, is illustrates one use of stats with input parameters. --> or something like this.

[gilleslandais]

As you can imagine, I am also annoyed with quotes in names (especially for columns).

Currently the VizieRTAP service add quotes in both xml output (/tap/tables) and in database tap_schema.
But quotes are not in place in the registry vs:table (historical choice) . That's not consistent !

Update registry - why not - but carrefully : I'm not sure that adding quotes won't have any issues with clients?
astroquery? pyVO? topcat? ... and others codes may be using those...

The best, would be that VizieR adopts new (and modern) conventions.
But this revolution could harms users (astronomers.. and CDS staaf...)

...I can't give any response yet! ... but that's a good point!