3 |
|
|
4 |
As a recommendation is published in the IVOA document repository, a |
As a recommendation is published in the IVOA document repository, a |
5 |
globally editable page[1] titled <standardname>-<currentversion>-Next is |
globally editable page[1] titled <standardname>-<currentversion>-Next is |
6 |
created and linked from the standard's landing page as well as from |
created. This page will have four sections: |
|
the document text. The standard preamble on the "Status of this |
|
|
Document" for a REC must now contain text to the effect that "Discussion |
|
|
on the evolution of this standard, as well as proposed, rejected, and |
|
|
accepted errata, can be found at <link to the -Next page>." |
|
|
|
|
|
One such Next-page is maintained per recommendation (i.e., standards |
|
|
version); as a new REC is passed, a new, empty -Next page is created. |
|
|
|
|
|
Theses pages have four sections: |
|
7 |
|
|
8 |
* Accepted Errata |
* Accepted Errata |
9 |
* Rejected Errata |
* Rejected Errata |
10 |
* Proposed Errata |
* Proposed Errata |
11 |
* Proposed Features |
* Proposed Features |
12 |
|
|
13 |
|
All the Errata sections will consist of listings whose items are |
14 |
|
pointers to globally editable pages titled |
15 |
|
<standardname>-<currentversion>-Erratum-<runningnumber> |
16 |
|
where the text for the erratum will physically reside. |
17 |
|
|
18 |
|
The Proposed Features section may have a similar structure or just |
19 |
|
consist of actual description of the features depending on the content |
20 |
|
length and complexity. |
21 |
|
|
22 |
|
The Accepted Errata elements (i.e. the errata reviewed by TCG and Exec as |
23 |
|
described later in this section) must be linked from the standard's |
24 |
|
landing page as well as from the document text. |
25 |
|
|
26 |
|
The standard preamble on the "Status of this |
27 |
|
Document" for a REC must now contain text to the effect that "Discussion |
28 |
|
on the evolution of this standard, as well as accepted errata, can be |
29 |
|
found at <links to the Accepted-Errata-page(s)>." |
30 |
|
|
31 |
|
Rejected and Proposed Errata not yet reviewed, as well as Proposed |
32 |
|
Features, will continue living in the -Next page as recollection of |
33 |
|
present and past activity on the specification. |
34 |
|
|
35 |
|
One such Next-page is maintained per recommendation (i.e., standards |
36 |
|
version); as a new REC is passed, a new, empty -Next page is created. |
37 |
|
|
38 |
Both Accepted and Rejected Errata may only be edited by the responsible |
Both Accepted and Rejected Errata may only be edited by the responsible |
39 |
working group chairs on behalf of the TCG as discussed below, who also |
working group chairs on behalf of the TCG as discussed below, who also |
40 |
MUST remove edits by other parties. |
MUST remove edits by other parties. |
53 |
* Rationale |
* Rationale |
54 |
* Impact Assessment |
* Impact Assessment |
55 |
|
|
56 |
Physically, the text resides on a globally editable page titled |
As already said, physically, the text resides on a globally editable |
57 |
<standardname>-<currentversion>-Erratum-<runningnumber>. A link to |
page linked from the Proposed Errata section of the -Next page. The |
58 |
this page is then added to the Proposed Errata section of the -Next |
proposed erratum is then announced on the Working Group's mailing |
59 |
page and announced on the Working Group's mailing list, which should |
list, which should also be the main medium of discussing the erratum. |
60 |
also be the main medium of discussing the erratum. Errata likely to |
Errata likely to affect other working groups should also be announced |
61 |
affect other working groups should also be announced on the full VO |
on the full VO community. |
|
community. |
|
62 |
|
|
63 |
Before each meeting of the TCG, the TCG chair collects a list of |
Before each meeting of the TCG, the TCG chair collects a list of |
64 |
proposed errata for the WG chairs. It must be circulated to all TCG |
proposed errata for the WG chairs. It must be circulated to all TCG |