Difference between revisions of "Process for requesting publication of errata"
| Line 1: | Line 1: | ||
Formalization of process for requesting publication of errata (from [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=2585&start=0 TSC Tracker 2403]. Errata publications go to the CTO (Wayne) and not the TSC. | Formalization of process for requesting publication of errata (from [http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemEdit&tracker_item_id=2585&start=0 TSC Tracker 2403]. Errata publications go to the CTO (Wayne) and not the TSC. | ||
| − | As of 2013Jan the TSC included a different element on the publication request for errata. This new process using publication request form indicates a committee vote but would require final approved by | + | As of 2013Jan the TSC included a different element on the publication request for errata. This new process using publication request form indicates a committee vote but would require final approved by Wayne Kubick, the CTO. |
If the changes to a published standard are significant they should be balloted. Otherwise a list of addenda must be compiled. While a full re-publication release with errata would be more useful to implementers, most WGs would not want to re-publish the whole standard, as to ANSI, republishing is considered a new version. | If the changes to a published standard are significant they should be balloted. Otherwise a list of addenda must be compiled. While a full re-publication release with errata would be more useful to implementers, most WGs would not want to re-publish the whole standard, as to ANSI, republishing is considered a new version. | ||
Revision as of 21:26, 20 April 2016
Formalization of process for requesting publication of errata (from TSC Tracker 2403. Errata publications go to the CTO (Wayne) and not the TSC.
As of 2013Jan the TSC included a different element on the publication request for errata. This new process using publication request form indicates a committee vote but would require final approved by Wayne Kubick, the CTO.
If the changes to a published standard are significant they should be balloted. Otherwise a list of addenda must be compiled. While a full re-publication release with errata would be more useful to implementers, most WGs would not want to re-publish the whole standard, as to ANSI, republishing is considered a new version.
Summary - Normative publications go to HQ, Informative and DSTU come to TSC for approval, and errata are approved by John.
Work Groups that formerly gathered errata comments on the wiki have moved efforts largely to the DSTU comments site due to improvements on the web site.
