UDF catalogue Proposed Endorsed Note: Request for Comments
This PEN proposes a mechanism for listing
ADQL extension functions that are requried to work the same way across different data centers. It is a supplement to the
ADQL standard, and currently there's text in
ADQL 2.1 referencing it.
The latest version of the UDF catalogue can be found at:
http://ivoa.net/documents/udf-catalogue/
Version control:
https://volute.g-vo.org/svn/trunk/projects/dal/udf-catalogue
Reference Interoperable Implementations
As to the endorsed content, there should always be at least two services carrying the functions. Regrettably, the required RegTAP res_detail table doesn't carry UDF names (there's always a use case exactly for the most exotic feature you can think of), so to find these services, you'll have to rely on volutary extra keys parsed by the services.
The RegTAP service at
http://dc.g-vo.org/tap parses the extra res_detail. Use a query like
select access_url
from rr.res_detail
natural join rr.interface
natural join rr.capability
where detail_xpath='/capability/language/languageFeatures/feature/form'
and detail_value like 'ivo_healpix_index%'
and standard_id='ivo://ivoa.net/std/tap'
Implementations Validators
Not really applicable here. It might be nice to have a few standard queries per function with the intended results, but since
ADQL doesn't have queries without from clauses and there is essentially no content in the underlying databases you can rely on, they're really hard to write.
Perhaps a case for an
ADQL extension: Facilitate writing tests?
Comments from the IVOA Community during RFC/TCG review period: 2020-02-15 .. 2020-03-30
The comments from the TCG members during the RFC/TCG review should be included in the next section.
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
Comments from TCG member during the RFC/TCG Review Period: 2020-02-15 .. 2020-03-30
WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.
IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.
TCG Chair & Vice Chair
TCG Vote : Vote_start_date - Vote_end_date
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
Group |
Yes |
No |
Abstain |
Comments |
TCG |
|
|
|
|
Apps |
|
|
|
|
DAL |
|
|
|
|
DM |
|
|
|
|
GWS |
|
|
|
|
Registry |
|
|
|
|
Semantics |
|
|
|
|
DCP |
|
|
|
|
KDIG |
|
|
|
|
SSIG |
|
|
|
|
Theory |
|
|
|
|
TD |
|
|
|
|
Ops |
|
|
|
|
StdProc |
|
|
|
|