TAP-1.0 Erratum 5: VOTable usage in TAPAuthor: Markus Demleitner | ||||||||
Changed: | ||||||||
< < | Date last changed: 2017-02-14 | |||||||
> > | Date last changed: 2017-02-23 | |||||||
Added: | ||||||||
> > | Date accepted: 2018-02-22 | |||||||
RationaleThe wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. It is clear that §2.9 is discussing both successful and error outputs, and in the case of an error noTABLE element will normally be present, only one or more INFO elements. However, while the intention is clear from the fourth example in §2.9.1, it is not clear from the wording.
Erratum ContentThis erratum removes the inconsistency by changing:
The VOTable must contain a RESOURCE element identified with the attribute type="results", containing a single TABLE element with the results of the query.to The VOTable must contain a RESOURCE element identified with the attribute type="results". In case of successful job execution, this must contain exactly one TABLE element with the results of the query. In case of job failure, the TABLE element may be absent.and
The RESOURCE element must contain, before the TABLE element, an INFO element with attribute name="QUERY_STATUS". The value attribute must contain one of the following values:to The RESOURCE element must contain an INFO element with attribute name="QUERY_STATUS" indicating the success of the operation. For RESOURCE elements that contain a TABLE element, this INFO element must appear lexically before the TABLE. The following values are defined for this INFO element's value attribute: Impact AssessmentSince the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services or consuming applications are foreseen.Note | ||||||||
Changed: | ||||||||
< < | This Erratum was previously part of the TAP1Err1 Note still available on volute. The content presented here started from §6 of that Note at svn revision 2800. | |||||||
> > | This Erratum was previously part of the TAP1Err1 Errata Note (PDF former version). The content presented here started from §6 of that Note. | |||||||
Added: | ||||||||
> > | Erratum approved on 2018-02-22 by TCG, but last changes made as action deriving from that TCG tconf: removing unstable SVN reference and added formal author. -- MarcoMolinaro - 2018-02-23 | |||||||
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
TAP-1.0 Erratum 5: VOTable usage in TAP | ||||||||
Changed: | ||||||||
< < | Author: DAL WG | |||||||
> > | Author: Markus Demleitner | |||||||
Date last changed: 2017-02-14
RationaleThe wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. It is clear that §2.9 is discussing both successful and error outputs, and in the case of an error noTABLE element will normally be present, only one or more INFO elements. However, while the intention is clear from the fourth example in §2.9.1, it is not clear from the wording.
Erratum ContentThis erratum removes the inconsistency by changing:
The VOTable must contain a RESOURCE element identified with the attribute type="results", containing a single TABLE element with the results of the query.to The VOTable must contain a RESOURCE element identified with the attribute type="results". In case of successful job execution, this must contain exactly one | ||||||||
Changed: | ||||||||
< < | TABLE element with the results of the query. [In case of job failure, the TABLE element may be absent.] | |||||||
> > | TABLE element with the results of the query. In case of job failure, the TABLE element may be absent. | |||||||
and
The RESOURCE element must contain, before the TABLE element, an INFO element with attribute name="QUERY_STATUS". The value attribute must contain one of the following values:to The RESOURCE element must contain an INFO element with attribute name="QUERY_STATUS" indicating the success of the operation. For RESOURCE elements that contain a TABLE element, this INFO element must appear lexically before the TABLE. The following values are defined for this INFO element's value attribute: Impact AssessmentSince the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services or consuming applications are foreseen.NoteThis Erratum was previously part of the TAP1Err1 Note still available on volute. The content presented here started from §6 of that Note at svn revision 2800.<--
|
TAP-1.0 Erratum 5: VOTable usage in TAPAuthor: DAL WG | ||||||||
Changed: | ||||||||
< < | Date last changed: 2017-09-28 | |||||||
> > | Date last changed: 2017-02-14 | |||||||
RationaleThe wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. It is clear that §2.9 is discussing both successful and error outputs, and in the case of an error noTABLE element will normally be present, only one or more INFO elements. However, while the intention is clear from the fourth example in §2.9.1, it is not clear from the wording.
Erratum Content | ||||||||
Changed: | ||||||||
< < | The wording of §2.9 and §2.9.1 of TAP-1.0 is inconsistent with the rules for VOTable error documents. §2.9 says | |||||||
> > | This erratum removes the inconsistency by changing: | |||||||
Deleted: | ||||||||
< < |
TABLE element will normally be present, only one or more INFO elements. | |||||||
Changed: | ||||||||
< < | This Erratum removes the inconsistency by changing:
| |||||||
> > |
The VOTable must contain a RESOURCE element identified with the attribute type="results", containing a single TABLE element with the results of the query. | |||||||
Added: | ||||||||
> > | ||||||||
to | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
The VOTable must contain a RESOURCE element identified with the attribute type="results". In case of successful job execution, this must contain exactly one TABLE element with the results of the query. [In case of job failure, the TABLE element may be absent.]and | |||||||
Added: | ||||||||
> > |
The RESOURCE element must contain, before the TABLE element, an INFO element with attribute name="QUERY_STATUS". The value attribute must contain one of the following values: | |||||||
to | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | The RESOURCE element must contain an INFO element with attribute name="QUERY_STATUS" indicating the success of the operation. For RESOURCE | |||||||
Added: | ||||||||
> > | elements that contain a TABLE element, this INFO element must appear lexically before the TABLE. The following values are defined for this INFO element's value attribute: | |||||||
Impact AssessmentSince the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services or consuming applications are foreseen.NoteThis Erratum was previously part of the TAP1Err1 Note still available on volute. The content presented here started from §6 of that Note at svn revision 2800.<--
|
TAP-1.0 Erratum 5: VOTable usage in TAPAuthor: DAL WG Date last changed: 2017-09-28RationaleThe wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. It is clear that §2.9 is discussing both successful and error outputs, and in the case of an error noTABLE element will normally be present, only one or more INFO elements. However, while the intention is clear from the fourth example in §2.9.1, it is not clear from the wording.
Erratum ContentThe wording of §2.9 and §2.9.1 of TAP-1.0 is inconsistent with the rules for VOTable error documents. §2.9 says
TABLE element will normally be present, only one or more INFO elements.
This Erratum removes the inconsistency by changing:
| ||||||||
Changed: | ||||||||
< < | RESOURCE element identified with the attribute =type='results'=type='results'. In case of successful job execution, | |||||||
> > | RESOURCE element identified with the attribute type='results' . In case of successful job execution, | |||||||
this must contain exactly one TABLE element with the results of
the query. [In case of job failure, the TABLE element may be absent.]
Impact Assessment | ||||||||
Changed: | ||||||||
< < | Since the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services and consuming application is foreseen. | |||||||
> > | Since the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services or consuming applications are foreseen. | |||||||
NoteThis Erratum was previously part of the TAP1Err1 Note still available on volute. The content presented here started from §6 of that Note at svn revision 2800.<--
|
TAP-1.0 Erratum 5: VOTable usage in TAPAuthor: DAL WG | ||||||||
Changed: | ||||||||
< < | Date last changed: 2014-12-22 | |||||||
> > | Date last changed: 2017-09-28 | |||||||
RationaleThe wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. It is clear that §2.9 is discussing both successful and error outputs, and in the case of an error noTABLE element will normally be present, only one or more INFO elements. However, while the intention is clear from the fourth example in §2.9.1, it is not clear from the wording.
Erratum ContentThe wording of §2.9 and §2.9.1 of TAP-1.0 is inconsistent with the rules for VOTable error documents. §2.9 says
TABLE element will normally be present, only one or more INFO elements.
This Erratum removes the inconsistency by changing:
| ||||||||
Changed: | ||||||||
< < | RESOURCE element identified with the attribute type='results' , containing a single TABLE element with the results of the query. | |||||||
> > | | |||||||
to
| ||||||||
Changed: | ||||||||
< < | RESOURCE element identified with the attribute type='results' , containing exactly one TABLE element with the results of the query if the job execution was successful or no TABLE element if the job execution failed to produce a result. | |||||||
> > | RESOURCE element identified with the attribute =type='results'=type='results'. In case of successful job execution, | |||||||
Added: | ||||||||
> > | this must contain exactly one TABLE element with the results of the query. [In case of job failure, the TABLE element may be absent.] | |||||||
Impact AssessmentSince the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services and consuming application is foreseen.Note | ||||||||
Changed: | ||||||||
< < | This Erratum was previously part of the TAP1Err1 Note still available on volute. The content reflects §6 of that Note at svn revision 2800. | |||||||
> > | This Erratum was previously part of the TAP1Err1 Note still available on volute. The content presented here started from §6 of that Note at svn revision 2800. | |||||||
<--
|
TAP-1.0 Erratum 5: VOTable usage in TAPAuthor: DAL WG Date last changed: 2014-12-22Rationale | ||||||||
Changed: | ||||||||
< < | The wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. | |||||||
> > | The wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. | |||||||
It is clear that §2.9 is discussing both successful and error outputs, and in the case of an error no TABLE element will normally be present, only one or more INFO elements. However, while the intention is clear from the fourth example in §2.9.1, it is not clear from the wording.
Erratum ContentThe wording of §2.9 and §2.9.1 of TAP-1.0 is inconsistent with the rules for VOTable error documents. §2.9 says
TABLE element will normally be present, only one or more INFO elements.
This Erratum removes the inconsistency by changing:
Impact AssessmentSince the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services and consuming application is foreseen.NoteThis Erratum was previously part of the TAP1Err1 Note still available on volute. The content reflects §6 of that Note at svn revision 2800.<--
|
TAP-1.0 Erratum 5: VOTable usage in TAPAuthor: DAL WG Date last changed: 2014-12-22RationaleThe wording in TAP-1.0 in §~2.9 and §2.9.1 about the use of VOTable is somewhat inconsistent about the format of VOTable error documents. It is clear that §2.9 is discussing both successful and error outputs, and in the case of an error noTABLE element will normally be present, only one or more INFO elements. However, while the intention is clear from the fourth example in §2.9.1, it is not clear from the wording.
Erratum ContentThe wording of §2.9 and §2.9.1 of TAP-1.0 is inconsistent with the rules for VOTable error documents. §2.9 says
TABLE element will normally be present, only one or more INFO elements.
This Erratum removes the inconsistency by changing:
Impact AssessmentSince the wording changes introduced by this Erratum are only meant to better describe the usage of an existing recommendation (the VOTable one) inside the TAP-1.0 protocol, no effects on TAP-1.0 services and consuming application is foreseen.NoteThis Erratum was previously part of the TAP1Err1 Note still available on volute. The content reflects §6 of that Note at svn revision 2800.<--
|