Datalink-1.0 Erratum 1: RESOURCE type valueAuthor: Markus Demleitner Date last changed: 2017-11-22 | ||||||||
Added: | ||||||||
> > | Date accepted: 2018-02-22 | |||||||
Erratum contentIn section 3.2.3, in the first line of the example, Datalink REC-1.0 says<RESOURCE type="service"...
This must be replaced with
<RESOURCE type="meta"...
In section 4.4, in line 18 of the example, Datalink REC-1.0 says
<RESOURCE type="service"...
This must be replaced with
<RESOURCE type="meta"...
RationaleDuring the development of Datalink, it was discovered that the type attribute of the VOTable RESOURCE element only admits a controlled vocabulary. The previous proposal to have type="service" for datalink service definition blocks was then retracted. Instead, conventional type="meta" blocks are to be used. In the editing process, two examples for the previous proposal were accidentally left in the text. This erratum corrects this oversight.Impact assessmentThere should be no impact, except to reduce possible confusion of implementors. No normative text is changed, and even if someone had tried to implement based on the erroneous examples, they would have yielded invalid VOTables, and thus their services would have been flagged invalid anyway.<--
|
| ||||||||
Added: | ||||||||
> > | Datalink-1.0 Erratum 1: RESOURCE type valueAuthor: Markus Demleitner Date last changed: 2017-11-22 | |||||||
Erratum contentIn section 3.2.3, in the first line of the example, Datalink REC-1.0 says<RESOURCE type="service"...
This must be replaced with
<RESOURCE type="meta"...
In section 4.4, in line 18 of the example, Datalink REC-1.0 says
<RESOURCE type="service"...
This must be replaced with
<RESOURCE type="meta"...
RationaleDuring the development of Datalink, it was discovered that the type attribute of the VOTable RESOURCE element only admits a controlled vocabulary. The previous proposal to have type="service" for datalink service definition blocks was then retracted. Instead, conventional type="meta" blocks are to be used. In the editing process, two examples for the previous proposal were accidentally left in the text. This erratum corrects this oversight.Impact assessmentThere should be no impact, except to reduce possible confusion of implementors. No normative text is changed, and even if someone had tried to implement based on the erroneous examples, they would have yielded invalid VOTables, and thus their services would have been flagged invalid anyway.<--
|
Erratum contentIn section 3.2.3, in the first line of the example, Datalink REC-1.0 says<RESOURCE type="service"...
This must be replaced with
<RESOURCE type="meta"...
In section 4.4, in line 18 of the example, Datalink REC-1.0 says
<RESOURCE type="service"...
This must be replaced with
<RESOURCE type="meta"...
RationaleDuring the development of Datalink, it was discovered that the type attribute of the VOTable RESOURCE element only admits a controlled vocabulary. The previous proposal to have type="service" for datalink service definition blocks was then retracted. Instead, conventional type="meta" blocks are to be used. In the editing process, two examples for the previous proposal were accidentally left in the text. This erratum corrects this oversight.Impact assessmentThere should be no impact, except to reduce possible confusion of implementors. No normative text is changed, and even if someone had tried to implement based on the erroneous examples, they would have yielded invalid VOTables, and thus their services would have been flagged invalid anyway.<--
|