Difference: VODataServiceNext (1 vs. 6)

Revision 62019-02-05 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"
Changed:
<
<		This page collects specification issues as well as proposals for extensions for VODataService 1.1. Version 1.2, addressing most of the points below, is currently in pre-WD state. See https://volute.g-vo.org/svn/trunk/projects/registry/VODataService for where the review stands.
>
>		This page collects specification issues as well as proposals for
Added:
>
>		extensions for VODataService 1.1. Version 1.2, addressing most of the points below, is currently a working draft (of 2018-10).
 
Added:
>
>		See also https://volute.g-vo.org/svn/trunk/projects/registry/VODataService for the bleeding edge
 

Specification Problems

  • In current VODataService tableset, table structure is implied to be schema.table; ADQL table references, on the other hand, have one to three elements. This should be reconciled; I propose allowing table-s as direct children of tableset and prescribing full ADQL table references in table/name. -- MarkusDemleitner - 2015-05-05
Added:
>
>
    • This is in current 1.2 drafts, except that we now use anonymous schema elements for instead of having direct children (because it's saving migration in RegTAP).
 
  • VODataService has no provisions for how SQL delimited identifiers are to be handled where that is relevant (e.g., in TAP tables endpoints). I propose to explicitly say {schema/table/column}/name "must be in forms ready for application" and mention ADQL and the respective symbols as examples. -- MarkusDemleitner - 2015-05-05
Added:
>
>
    • This is in current 1.2 drafts.
 
  • ParamHTTP (and perhaps others) resultType is 0..1. With DALI RESPONSEFORMAT, that should probably be made 0..n. Or perhaps we should just adapt TAPRegExt's outputFormat, which already models DALI? -- MarkusDemleitner - 2018-03-16
Added:
>
>
    • There do not seem to be terribly important use cases for resultTypes. So, we'll probably leave this alone in 1.2.
 
  • For many reasons, we DataCollections should be allowed to have capabilities. -- MarkusDemleitner - 2018-04-18
Added:
>
>
    • This has been solved by deprecating DataCollections and using CatalogResources instead.
 

Suggested Extensions

  • Have some markup to say what dataproduct types the service will return? This would be particularly useful with ObsTAP ("what services have time series?"). -- MarkusDemleitner - 2018-04-18
Added:
>
>
    • No satisfying solutions have been suggested so far.
 
Added:
>
>
    • This is in 1.2 drafts.
 
<--  
-->

Revision 52018-10-02 - MarkTaylor

 
META TOPICPARENT name="IvoaResReg"
This page collects specification issues as well as proposals for extensions for VODataService 1.1. Version 1.2, addressing most of the points below, is currently in pre-WD state. See https://volute.g-vo.org/svn/trunk/projects/registry/VODataService for where the review stands.

Specification Problems

  • In current VODataService tableset, table structure is implied to be schema.table; ADQL table references, on the other hand, have one to three elements. This should be reconciled; I propose allowing table-s as direct children of tableset and prescribing full ADQL table references in table/name. -- MarkusDemleitner - 2015-05-05
  • VODataService has no provisions for how SQL delimited identifiers are to be handled where that is relevant (e.g., in TAP tables endpoints). I propose to explicitly say {schema/table/column}/name "must be in forms ready for application" and mention ADQL and the respective symbols as examples. -- MarkusDemleitner - 2015-05-05
  • ParamHTTP (and perhaps others) resultType is 0..1. With DALI RESPONSEFORMAT, that should probably be made 0..n. Or perhaps we should just adapt TAPRegExt's outputFormat, which already models DALI? -- MarkusDemleitner - 2018-03-16
  • For many reasons, we DataCollections should be allowed to have capabilities. -- MarkusDemleitner - 2018-04-18

Suggested Extensions

  • Have some markup to say what dataproduct types the service will return? This would be particularly useful with ObsTAP ("what services have time series?"). -- MarkusDemleitner - 2018-04-18
Changed:
<
<
>
>
 
<--  
-->

Revision 42018-10-01 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"
Changed:
<
<		This page collects specification issues as well as proposals for extensions for VODataService 1.1. No new version of the document is scheduled right now.
>
>		This page collects specification issues as well as proposals for extensions for VODataService 1.1. Version 1.2, addressing most of the points below, is currently in pre-WD state. See https://volute.g-vo.org/svn/trunk/projects/registry/VODataService for where the review stands.
 

Specification Problems

  • In current VODataService tableset, table structure is implied to be schema.table; ADQL table references, on the other hand, have one to three elements. This should be reconciled; I propose allowing table-s as direct children of tableset and prescribing full ADQL table references in table/name. -- MarkusDemleitner - 2015-05-05
Changed:
<
<
  • VODataService has no provisions for how SQL delimited identifiers are to be handled where that is relevant (e.g., in TAP tables endpoints). I propose to explitely say {schema/table/column}/name "must be in forms ready for application" and mention ADQL and the respective symbols as examples. -- MarkusDemleitner - 2015-05-05
>
>
  • VODataService has no provisions for how SQL delimited identifiers are to be handled where that is relevant (e.g., in TAP tables endpoints). I propose to explicitly say {schema/table/column}/name "must be in forms ready for application" and mention ADQL and the respective symbols as examples. -- MarkusDemleitner - 2015-05-05
 
  • ParamHTTP (and perhaps others) resultType is 0..1. With DALI RESPONSEFORMAT, that should probably be made 0..n. Or perhaps we should just adapt TAPRegExt's outputFormat, which already models DALI? -- MarkusDemleitner - 2018-03-16
Changed:
<
<
  • For many reasons, we DataCollections should be allowed to have capabilities. -- MarkusDemleitner - 2018-04-18
>
>
  • For many reasons, we DataCollections should be allowed to have capabilities. -- MarkusDemleitner - 2018-04-18
 

Suggested Extensions

  • Have some markup to say what dataproduct types the service will return? This would be particularly useful with ObsTAP ("what services have time series?"). -- MarkusDemleitner - 2018-04-18
  • Add numerical/MOC coverage (see note) -- MarkusDemleitner - 2018-04-18
Changed:
<
<

Revision 32018-04-18 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"
This page collects specification issues as well as proposals for extensions for VODataService 1.1. No new version of the document is scheduled right now.

Specification Problems

  • In current VODataService tableset, table structure is implied to be schema.table; ADQL table references, on the other hand, have one to three elements. This should be reconciled; I propose allowing table-s as direct children of tableset and prescribing full ADQL table references in table/name. -- MarkusDemleitner - 2015-05-05
  • VODataService has no provisions for how SQL delimited identifiers are to be handled where that is relevant (e.g., in TAP tables endpoints). I propose to explitely say {schema/table/column}/name "must be in forms ready for application" and mention ADQL and the respective symbols as examples. -- MarkusDemleitner - 2015-05-05
Changed:
<
<
  • ParamHTTP (and perhaps others) resultType is 0..1. With DALI RESPONSEFORMAT, that should probably be made 0..n. Or perhaps we should just adapt TAPRegExt's outputFormat, which already models DALI? -- MarkusDemleitner - 2018-03-16
>
>
  • ParamHTTP (and perhaps others) resultType is 0..1. With DALI RESPONSEFORMAT, that should probably be made 0..n. Or perhaps we should just adapt TAPRegExt's outputFormat, which already models DALI? -- MarkusDemleitner - 2018-03-16
Added:
>
>
  • For many reasons, we DataCollections should be allowed to have capabilities. -- MarkusDemleitner - 2018-04-18
 

Suggested Extensions

Added:
>
>
  • Have some markup to say what dataproduct types the service will return? This would be particularly useful with ObsTAP ("what services have time series?"). -- MarkusDemleitner - 2018-04-18
  • Add numerical/MOC coverage (see note) -- MarkusDemleitner - 2018-04-18
 
<--  
-->

Revision 22018-03-16 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"
This page collects specification issues as well as proposals for extensions for VODataService 1.1. No new version of the document is scheduled right now.

Specification Problems

  • In current VODataService tableset, table structure is implied to be schema.table; ADQL table references, on the other hand, have one to three elements. This should be reconciled; I propose allowing table-s as direct children of tableset and prescribing full ADQL table references in table/name. -- MarkusDemleitner - 2015-05-05
  • VODataService has no provisions for how SQL delimited identifiers are to be handled where that is relevant (e.g., in TAP tables endpoints). I propose to explitely say {schema/table/column}/name "must be in forms ready for application" and mention ADQL and the respective symbols as examples. -- MarkusDemleitner - 2015-05-05
Added:
>
>
  • ParamHTTP (and perhaps others) resultType is 0..1. With DALI RESPONSEFORMAT, that should probably be made 0..n. Or perhaps we should just adapt TAPRegExt's outputFormat, which already models DALI? -- MarkusDemleitner - 2018-03-16
 

Suggested Extensions 


<--  
-->

Revision 12015-05-05 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"
This page collects specification issues as well as proposals for extensions for VODataService 1.1. No new version of the document is scheduled right now.

Specification Problems

  • In current VODataService tableset, table structure is implied to be schema.table; ADQL table references, on the other hand, have one to three elements. This should be reconciled; I propose allowing table-s as direct children of tableset and prescribing full ADQL table references in table/name. -- MarkusDemleitner - 2015-05-05
  • VODataService has no provisions for how SQL delimited identifiers are to be handled where that is relevant (e.g., in TAP tables endpoints). I propose to explitely say {schema/table/column}/name "must be in forms ready for application" and mention ADQL and the respective symbols as examples. -- MarkusDemleitner - 2015-05-05

Suggested Extensions 


<--  
-->
View topic | History: r6 < r5 < r4 < r3 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback