Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Ambiguous text and wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 Date accepted:2023-07-26RationaleIn section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX single value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting from version 1.5. PARAMs and FIELDs with "interval" xtype do not apply a specific rule for MIN/MAX interpretration. | ||||||||
Changed: | ||||||||
< < | In addition the closing tag of the VALUES element is wrongly written <verbatim></VALUE></verbatim> | |||||||
> > | In addition the closing tag of the VALUES element is wrongly written /VALUE | |||||||
Changed: | ||||||||
< < | instead of <verbatim></VALUES></verbatim> | |||||||
> > | instead of /VALUES | |||||||
This ambiguity orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2)
Erratum ContentThis Erratum proposes following changes.Modify text and fix VOTable syntaxIn §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND text and example in fromFor float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} should be used to communicate the range of values for which clients can expect to receive data. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUE> </PARAM>to For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} are single values which apply to the two elements in the BAND array, as stated in the VOTable specification starting from version 1.5, and in the DALI specification starting from version 1.2. There is no specific rule to apply for parameters with xtype=interval. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted. MIN (resp. MAX) is the minimal (reps. maximal) value of the two bounds of the interval</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUES> </PARAM> Impact AssessmentMaking the text less ambiguous will help implementers to deliver correct values of MIN/MAX elements for intervals. Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. | ||||||||
Added: | ||||||||
> > |
Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Ambiguous text and wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 | ||||||||
Changed: | ||||||||
< < | Date accepted: | |||||||
> > | Date accepted:2023-07-26 | |||||||
RationaleIn section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX single value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting from version 1.5. PARAMs and FIELDs with "interval" xtype do not apply a specific rule for MIN/MAX interpretration. In addition the closing tag of the VALUES element is wrongly written<verbatim></VALUE></verbatim> instead of <verbatim></VALUES></verbatim> This ambiguity orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) Erratum ContentThis Erratum proposes following changes.Modify text and fix VOTable syntaxIn §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND text and example in from | ||||||||
Added: | ||||||||
> > | ||||||||
For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} should be used to communicate the range of values for which clients can expect to receive data. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUE> </PARAM>to | ||||||||
Added: | ||||||||
> > | ||||||||
For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} are single values which apply to the two elements in the BAND array, as stated in the VOTable specification starting from version 1.5, and in the DALI specification starting from version 1.2. There is no specific rule to apply for parameters with xtype=interval. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted. MIN (resp. MAX) is the minimal (reps. maximal) value of the two bounds of the interval</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUES> </PARAM> Impact AssessmentMaking the text less ambiguous will help implementers to deliver correct values of MIN/MAX elements for intervals. Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. |
Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Ambiguous text and wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 Date accepted:Rationale | ||||||||
Changed: | ||||||||
< < | In section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX single value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting for version 1.5. PARAMs and FIELDs with "interval" xtype do not apply a specific rule for MIN/MAX interpretration. | |||||||
> > | In section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX single value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting from version 1.5. PARAMs and FIELDs with "interval" xtype do not apply a specific rule for MIN/MAX interpretration. | |||||||
In addition the closing tag of the VALUES element is wrongly written <verbatim></VALUE></verbatim> instead of <verbatim></VALUES></verbatim> This ambiguity orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) Erratum ContentThis Erratum proposes following changes.Modify text and fix VOTable syntaxIn §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND text and example in from | ||||||||
Deleted: | ||||||||
< < | ||||||||
For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} should be used to communicate the range of values for which clients can expect to receive data. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUE> </PARAM>to | ||||||||
Deleted: | ||||||||
< < | ||||||||
For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} are single values which apply to the two elements in the BAND array, as stated in the VOTable specification starting from version 1.5, and in the DALI specification starting from version 1.2. There is no specific rule to apply for parameters with xtype=interval. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted. MIN (resp. MAX) is the minimal (reps. maximal) value of the two bounds of the interval</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUES> </PARAM> | ||||||||
Deleted: | ||||||||
< < | ||||||||
Impact AssessmentMaking the text less ambiguous will help implementers to deliver correct values of MIN/MAX elements for intervals. | ||||||||
Changed: | ||||||||
< < | Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. | |||||||
> > | Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. | |||||||
Deleted: | ||||||||
< < |
Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Ambiguous text and wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 Date accepted:RationaleIn section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX single value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting for version 1.5. PARAMs and FIELDs with "interval" xtype do not apply a specific rule for MIN/MAX interpretration. In addition the closing tag of the VALUES element is wrongly written<verbatim></VALUE></verbatim> instead of <verbatim></VALUES></verbatim> This ambiguity orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) Erratum ContentThis Erratum proposes following changes.Modify text and fix VOTable syntaxIn §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND text and example in fromFor float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} should be used to communicate the range of values for which clients can expect to receive data. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
to
For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} are single values | ||||||||
Changed: | ||||||||
< < | which apply to the two elements in the BAND array, as stated in the VOTable specification starting from version 1.5. | |||||||
> > | which apply to the two elements in the BAND array, as stated in the VOTable specification starting from version 1.5, and in the DALI specification starting from version 1.2. | |||||||
There is no specific rule to apply for parameters with xtype=interval. Example:
<PARAM name="BAND" unit="m" ucd="em.wl;stat.interval"
datatype="double" arraysize="2"
xtype="interval" value="">
Impact AssessmentMaking the text less ambiguous will help implementers to deliver correct values of MIN/MAX elements for intervals. Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. |
| ||||||||
Changed: | ||||||||
< < | Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Wrong VOTable syntax in BAND example | |||||||
> > | Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Ambiguous text and wrong VOTable syntax in BAND example | |||||||
Author: François Bonnarel
Date last changed: 2023-01-23
Date accepted:
Rationale | ||||||||
Changed: | ||||||||
< < | In section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting for version 1.5. In addition the closing tag of the VALUES element is wrongly written <verbatim></VALUE></verbatim> | |||||||
> > | In section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX single value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting for version 1.5. PARAMs and FIELDs with "interval" xtype do not apply a specific rule for MIN/MAX interpretration. | |||||||
Added: | ||||||||
> > | In addition the closing tag of the VALUES element is wrongly written <verbatim></VALUE></verbatim> | |||||||
instead of <verbatim></VALUES></verbatim> This ambiguity orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) Erratum ContentThis Erratum proposes following changes. | ||||||||
Changed: | ||||||||
< < | Fix VOTable syntax | |||||||
> > | Modify text and fix VOTable syntax | |||||||
In §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND text and example in from | ||||||||
Changed: | ||||||||
< < | For float-valued intervals (e.g., the standard BAND and TIME parameters), VALUES/MIN and VALUES/MAX should be used to communicate the range | |||||||
> > | For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} should be used to communicate the range | |||||||
of values for which clients can expect to receive data. Example:
<PARAM name="BAND" unit="m" ucd="em.wl;stat.interval"
datatype="double" arraysize="2"
xtype="interval" value="">
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Deleted: | ||||||||
< < |
<MIN value="3e-7"/> | |||||||
to | ||||||||
Changed: | ||||||||
< < | <MIN value="3e-7 5.5e-7"/> | |||||||
> > | ||||||||
Added: | ||||||||
> > | For float-valued intervals (e.g., the standard BAND and TIME parameters), \xmlel{VALUES/MIN} and \xmlel{VALUES/MAX} are single values
which apply to the two elements in the BAND array, as stated in the VOTable specification starting from version 1.5.
There is no specific rule to apply for parameters with xtype=interval. Example:
<PARAM name="BAND" unit="m" ucd="em.wl;stat.interval"
datatype="double" arraysize="2"
xtype="interval" value="">
| |||||||
Deleted: | ||||||||
< < | from | |||||||
Deleted: | ||||||||
< < | <MAX value="8e-7"/>to <MAX value="2e-7 8e-7"/>from </VALUE>to </VALUES> | |||||||
Impact Assessment | ||||||||
Changed: | ||||||||
< < | Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. | |||||||
> > | Making the text less ambiguous will help implementers to deliver correct values of MIN/MAX elements for intervals. | |||||||
Added: | ||||||||
> > | Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. |
Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 Date accepted:Rationale | ||||||||
Changed: | ||||||||
< < | In section 4.2, the VOTable excerpt given for the BAND PARAM is written following a wrong syntax for the MIN and MAX elements. The values of these elements are not consistent with the BAND arraysize attribute because they only contain a single number. MIN and MAX should actually contain arrays of 2 numbers. The MIN array should give the minimum length interval and the MAX array should give the maximum length interval. In addition the closing tag of the VALUES element is wrongly written <verbatim></VALUE></verbatim> | |||||||
> > | In section 4.2, the VOTable excerpt given for the BAND PARAM is somewhat ambiguous for the MIN and MAX elements syntax. The values of these elements are single doubles while the BAND arraysize attribute is 2. It has to be clarified that the MIN single value applies to the two elements in the BAND array as well as the MAX value. This is consistent with a generic rule for MIN/MAX values for array-valued PARAMs and FIELDS as described in the VOTable specification starting for version 1.5. In addition the closing tag of the VALUES element is wrongly written <verbatim></VALUE></verbatim> | |||||||
instead of <verbatim></VALUES></verbatim> | ||||||||
Changed: | ||||||||
< < | This bug orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) | |||||||
> > | This ambiguity orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) | |||||||
Erratum ContentThis Erratum proposes following changes.Fix VOTable syntax | ||||||||
Changed: | ||||||||
< < | In §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND example MIN tag in | |||||||
> > | In §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND text and example in | |||||||
Changed: | ||||||||
< < | <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" | |||||||
> > | from | |||||||
Added: | ||||||||
> > |
For float-valued intervals (e.g., the standard BAND and TIME parameters), VALUES/MIN and VALUES/MAX should be used to communicate the range of values for which clients can expect to receive data. Example: <PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" | |||||||
datatype="double" arraysize="2"
xtype="interval" value="">
| ||||||||
Changed: | ||||||||
< < | from | |||||||
> > | ||||||||
<MIN value="3e-7"/>to <MIN value="3e-7 5.5e-7"/>from <MAX value="8e-7"/>to <MAX value="2e-7 8e-7"/>from </VALUE>to </VALUES> Impact AssessmentFixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. |
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 Date accepted:RationaleIn section 4.2, the VOTable excerpt given for the BAND PARAM is written following a wrong syntax for the MIN and MAX elements. The values of these elements are not consistent with the BAND arraysize attribute because they only contain a single number. MIN and MAX should actually contain arrays of 2 numbers. The MIN array should give the minimum length interval and the MAX array should give the maximum length interval. In addition the closing tag of the VALUES element is wrongly written<verbatim></VALUE></verbatim> instead of <verbatim></VALUES></verbatim> This bug orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) Erratum ContentThis Erratum proposes following changes.Fix VOTable syntaxIn §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND example MIN tag in<PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUE> </PARAM>from <MIN value="3e-7"/>to <MIN value="3e-7 5.5e-7"/>from <MAX value="8e-7"/>to <MAX value="2e-7 8e-7"/>from </VALUE>to </VALUES> Impact AssessmentFixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. | ||||||||
Deleted: | ||||||||
< < |
Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 Date accepted:RationaleIn section 4.2, the VOTable excerpt given for the BAND PARAM is written following a wrong syntax for the MIN and MAX elements. The values of these elements are not consistent with the BAND arraysize attribute because they only contain a single number. MIN and MAX should actually contain arrays of 2 numbers. The MIN array should give the minimum length interval and the MAX array should give the maximum length interval. In addition the closing tag of the VALUES element is wrongly written<verbatim></VALUE></verbatim> instead of <verbatim></VALUES></verbatim> This bug orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) Erratum ContentThis Erratum proposes following changes.Fix VOTable syntaxIn §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND example MIN tag in<PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUE> </PARAM>from | ||||||||
Changed: | ||||||||
< < | <verbatim><OPTION>I</OPTION></verbatim> | |||||||
> > | <MIN value="3e-7"/> | |||||||
to | ||||||||
Changed: | ||||||||
< < | <verbatim><OPTION value=I"/></verbatim> | |||||||
> > | <MIN value="3e-7 5.5e-7"/> | |||||||
from | ||||||||
Changed: | ||||||||
< < | <verbatim><OPTION>V</OPTION></verbatim> | |||||||
> > | <MAX value="8e-7"/> | |||||||
to | ||||||||
Changed: | ||||||||
< < | <verbatim><OPTION value=V"/></verbatim> | |||||||
> > | <MAX value="2e-7 8e-7"/> | |||||||
from | ||||||||
Changed: | ||||||||
< < | <verbatim></VALUE></verbatim> | |||||||
> > | </VALUE> | |||||||
to | ||||||||
Changed: | ||||||||
< < | <verbatim></VALUES></verbatim> | |||||||
> > | </VALUES> | |||||||
Impact Assessment | ||||||||
Changed: | ||||||||
< < | Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writng code delivering incorrect VOTables. | |||||||
> > | Fixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writing code delivering incorrect VOTables. | |||||||
Server-side Operations for Data Access version 1.0 Proposed Erratum 3: Wrong VOTable syntax in BAND exampleAuthor: François Bonnarel Date last changed: 2023-01-23 Date accepted:RationaleIn section 4.2, the VOTable excerpt given for the BAND PARAM is written following a wrong syntax for the MIN and MAX elements. The values of these elements are not consistent with the BAND arraysize attribute because they only contain a single number. MIN and MAX should actually contain arrays of 2 numbers. The MIN array should give the minimum length interval and the MAX array should give the maximum length interval. In addition the closing tag of the VALUES element is wrongly written<verbatim></VALUE></verbatim> instead of <verbatim></VALUES></verbatim> This bug orignally described on github in SODA issue #2 (https://github.com/ivoa-std/SODA/issues/2) Erratum ContentThis Erratum proposes following changes.Fix VOTable syntaxIn §4.2 "*SODA Service Descriptor from DataLink*" of SODA-1.0, update the BAND example MIN tag in<PARAM name="BAND" unit="m" ucd="em.wl;stat.interval" datatype="double" arraysize="2" xtype="interval" value=""> <DESCRIPTION>The wavelength intervals to be extracted</DESCRIPTION> <VALUES> <MIN value="3e-7"/> <MAX value="8e-7"/> </VALUE> </PARAM>from <verbatim><OPTION>I</OPTION></verbatim> to <verbatim><OPTION value=I"/></verbatim> from <verbatim><OPTION>V</OPTION></verbatim> to <verbatim><OPTION value=V"/></verbatim> from <verbatim></VALUE></verbatim> to <verbatim></VALUES></verbatim> Impact AssessmentFixing the VOTable syntax in an example will make no harm to any service and will avoid implementers writng code delivering incorrect VOTables. |