UDF catalogue Proposed Endorsed Note: Request for Comments | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | This PEN proposes a mechanism for listing ADQL extension functions that are requried to work the same way in different data centers. It is a supplement to the ADQL standard, and currently there's text in ADQL 2.1 referencing it. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Latest version of the UDF catalogue can be found at: http://ivoa.net/documents/udf-catalogue/ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | 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 UCF names (there's always a use case exactly for the most exotic feature you can think of), so you might have to go parse different services' capabilities to find them. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The RegTAP service at http://dc.g-vo.org/tap lets you locate UDFs, though. Use a query like | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The RegTAP service at http://dc.g-vo.org/tap parses the extra res_detail. Use a query like | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | select ivoid | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | select access_url | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
from rr.res_detail | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | where detail_xpath='/capability/language/languageFeature/feature/form' | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | natural join rr.interface | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | natural join rr.capability where detail_xpath='/capability/language/languageFeatures/feature/form' | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
and detail_value like 'ivo_healpix_index%' | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | and standard_id='ivo://ivoa.net/std/tap' | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementations Validators | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Not really applicable here. It might be nice to have a few standard queries per function, but since ADQL doesn't have queries without from clauses, they're really hard to write. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | 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-30The 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 documentComments from TCG member during the RFC/TCG Review Period: 2020-02-15 .. 2020-03-30WG 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 ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupOperationsStandards and Processes CommitteeTCG Vote : Vote_start_date - Vote_end_dateIf 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.
<--
|
UDF catalogue Proposed Endorsed Note: Request for CommentsThis PEN proposes a mechanism for listing ADQL extension functions that are requried to work the same way in different data centers. It is a supplement to the ADQL standard, and currently there's text in ADQL 2.1 referencing it. 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-catalogueReference Interoperable ImplementationsAs 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 UCF names (there's always a use case exactly for the most exotic feature you can think of), so you might have to go parse different services' capabilities to find them. The RegTAP service at http://dc.g-vo.org/tap lets you locate UDFs, though. Use a query likeselect ivoid from rr.res_detail where detail_xpath='/capability/language/languageFeature/feature/form' and detail_value like 'ivo_healpix_index%' Implementations ValidatorsNot really applicable here. It might be nice to have a few standard queries per function, but since ADQL doesn't have queries without from clauses, 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-30The 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 documentComments from TCG member during the RFC/TCG Review Period: 2020-02-15 .. 2020-03-30WG 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 ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupOperationsStandards and Processes CommitteeTCG Vote : Vote_start_date - Vote_end_dateIf 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.
<--
|