-
Notifications
You must be signed in to change notification settings - Fork 5
Clean Registry extension specification #67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I wonder if some advisory text on how to discover SCS services would be in order ("where standard_id like 'ivo://ivoa.net/std/conesearch%'"). Also, we could be specific on what to do with capability/interface/version; right now, most services have this empty. whereas others put in 1.03, 1.1, or 1.0. This is not dramatically important, but it might be convenient if someone (e.g., a validator author) actually wants this. See:
select distinct std_version from rr.interface
natural join rr.capability
where standard_id like 'ivo://ivoa.net/std/conesearch%'
But all that can wait. Let's merge this and see.
Just to add some text to the section, maybe we can add the ADQL query on standardID as a showcase. Should I try it? The part on version might, on the other hand, become a new issue for v1.1 to be discussed. |
On Fri, Sep 19, 2025 at 06:15:40AM -0700, Marco Molinaro wrote:
molinaro-m left a comment (ivoa-std/ConeSearch#67)
Just to add some text to the section, maybe we can add the ADQL query on standardID as a showcase.
It would be a couple of text lines and the query itself, copying your comment here above.
Should I try it?
I'd say yes. I'm not sure how many implementors or users will make
*good use* of it, but at least it will help taking the first steps.
|
I added a few lines related to service discovery via RegTAP. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the discovery query, add a "AND intf_role='std'"; people shouldn't add other interfaces to cone search capabilities, but better safe than sorry (cf. https://ivoa.net/documents/RegTAP/20241002/REC-RegTAP-1.2.html#tth_sEc10.1).
I'll approve, and feel free to merge once you've put it in. Thanks!
Fixed, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This is a first, baseline, attempt at putting Cone Search registration prescription as a direct reference to SimpleDALRegExt.
The final goal is to close issue #62.
Please comment and discuss here what else should be part of this change in the ConeSearch text, taking into account that an Erratum will be required for SimpleDALRegExt to smooth out minor details.
For example, should we explicitly note here that there's an Endorsed Note (XML Schema Versioning) that saves us from changing standardID and namespace?
I suggest to keep this pull request in draft for some time to allow all interested people to be aware of this change.