<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft..com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h1
{mso-style-link:"Heading 1 Char";
margin-top:24.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
text-align:justify;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level1 lfo1;
font-size:14.0pt;
font-family:"Cambria","serif";
color:#365F91;
letter-spacing:.4pt;}
h2
{mso-style-link:"Heading 2 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level2 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
h3
{mso-style-link:"Heading 3 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level3 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
h4
{mso-style-link:"Heading 4 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level4 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
h5
{mso-style-link:"Heading 5 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level5 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
h6
{mso-style-link:"Heading 6 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level6 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
{mso-style-link:"Heading 7 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level7 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
{mso-style-link:"Heading 8 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level8 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
{mso-style-link:"Heading 9 Char";
margin-top:5.0pt;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-indent:0in;
page-break-after:avoid;
mso-list:l0 level9 lfo1;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
p.MsoList, li.MsoList, div.MsoList
{mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.25in;
margin-bottom:.0001pt;
text-indent:-.25in;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
{margin-top:0in;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:17.0pt;
text-align:justify;
text-indent:-17.0pt;
mso-list:l7 level1 lfo2;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
p.MsoListNumber, li.MsoListNumber, div.MsoListNumber
{margin-top:0in;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:17.0pt;
text-align:justify;
text-indent:-17.0pt;
mso-list:l3 level1 lfo3;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
letter-spacing:.4pt;
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-link:"Heading 2";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-link:"Heading 3";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
span.Heading4Char
{mso-style-name:"Heading 4 Char";
mso-style-link:"Heading 4";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-link:"Heading 5";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
span.Heading6Char
{mso-style-name:"Heading 6 Char";
mso-style-link:"Heading 6";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
span.Heading7Char
{mso-style-name:"Heading 7 Char";
mso-style-link:"Heading 7";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
span.Heading8Char
{mso-style-name:"Heading 8 Char";
mso-style-link:"Heading 8";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
span.Heading9Char
{mso-style-name:"Heading 9 Char";
mso-style-link:"Heading 9";
font-family:"Arial","sans-serif";
letter-spacing:.4pt;
font-weight:bold;}
p.PARAGRAPH, li.PARAGRAPH, div.PARAGRAPH
{mso-style-name:PARAGRAPH;
margin-top:5.0pt;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
text-align:justify;
font-size:10.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
p.NOTE, li.NOTE, div.NOTE
{mso-style-name:NOTE;
margin-top:0in;
margin-right:0in;
margin-bottom:5.0pt;
margin-left:0in;
text-align:justify;
font-size:8.0pt;
font-family:"Arial","sans-serif";
letter-spacing:.4pt;}
..MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:-5;
mso-list-template-ids:-1;}
@list l0:level1
{mso-level-style-link:"Heading 1";
mso-level-text:%1;
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:8.5pt;
margin-left:0in;
text-indent:0in;}
@list l0:level2
{mso-level-style-link:"Heading 2";
mso-level-text:"%1\.%2";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:8.5pt;
margin-left:0in;
text-indent:0in;}
@list l0:level3
{mso-level-style-link:"Heading 3";
mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:.1in;
margin-left:0in;
text-indent:0in;}
@list l0:level4
{mso-level-style-link:"Heading 4";
mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:.1in;
margin-left:0in;
text-indent:0in;}
@list l0:level5
{mso-level-style-link:"Heading 5";
mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:.1in;
margin-left:0in;
text-indent:0in;}
@list l0:level6
{mso-level-style-link:"Heading 6";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:.1in;
margin-left:0in;
text-indent:0in;}
@list l0:level7
{mso-level-style-link:"Heading 7";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:.1in;
margin-left:0in;
text-indent:0in;}
@list l0:level8
{mso-level-style-link:"Heading 8";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:.1in;
margin-left:0in;
text-indent:0in;}
@list l0:level9
{mso-level-style-link:"Heading 9";
mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:0in;
mso-level-legacy-space:.1in;
margin-left:0in;
text-indent:0in;}
@list l1
{mso-list-id:-2;
mso-list-type:simple;
mso-list-template-ids:-1;}
@list l1:level1
{mso-level-start-at:0;
mso-level-text:*;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:0in;
text-indent:0in;}
@list l2
{mso-list-id:819536006;
mso-list-type:hybrid;
mso-list-template-ids:-1074115914 367429932 67698691 67698703 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:922686745;
mso-list-type:simple;
mso-list-template-ids:-1401513912;}
@list l3:level1
{mso-level-number-format:alpha-lower;
mso-level-style-link:"List Number";
mso-level-text:"%1\)";
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l4
{mso-list-id:1045253816;
mso-list-type:hybrid;
mso-list-template-ids:2045567248 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l4:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:38.4pt;
text-indent:-.25in;}
@list l5
{mso-list-id:1363438153;
mso-list-type:hybrid;
mso-list-template-ids:-350028244 367429932 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l5:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l5:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l6
{mso-list-id:1549299030;
mso-list-type:simple;
mso-list-template-ids:-774073814;}
@list l6:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:17.85pt;
text-indent:-17.85pt;}
@list l7
{mso-list-id:1590231519;
mso-list-type:simple;
mso-list-template-ids:1172705504;}
@list l7:level1
{mso-level-number-format:bullet;
mso-level-style-link:"List Bullet";
mso-level-text:\F0B7;
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;
color:windowtext;}
@list l1:level1 lfo4
{mso-level-number-format:bullet;
mso-level-numbering:continue;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
mso-level-legacy:yes;
mso-level-legacy-indent:17.0pt;
mso-level-legacy-space:0in;
margin-left:17.0pt;
text-indent:-17.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText>The JTC1 Directives (and the ISO/IEC Directives, same
text) say :<o:p></o:p></p>
<p class=MsoPlainText><i>technical defect - A technical error or ambiguity in
an IS inadvertently introduced either in drafting or in printing which could lead
to incorrect or unsafe application of the IS.<o:p></o:p></i></p>
<p class=MsoPlainText><i><o:p> </o:p></i></p>
<p class=MsoPlainText><i>technical addition or change - Alteration or addition
to previously agreed technical provisions in an existing IS.<o:p></o:p></i></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>As Murata-san, Rex and Francis point out, this is not
sufficient to draw a clear line between Amendments and Corrigenda. However
there may be some additional guidance in the process itself. The Directives
texts, examined with previous experience in maintaining ISO/IEC standards,
show that:<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l5 level1 lfo6'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>A Technical Defect prevents the correct
application/implementation of a standard; it will lead to “incorrect or
unsafe” implementations, or implementations which will not interoperate.
It must be corrected promptly in order not to let those incorrect or unsafe
implementations from becoming widespread. To this effect, the process makes
clear that :<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:1.0in;text-indent:-.25in;mso-list:
l5 level2 lfo6'><![if !supportLists]><span style='font-family:"Courier New"'><span
style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>The Project Editor, who has the deepest
understanding of the text of the standard, is in charge of making the qualification
of a Defect Report into:<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:1.5in;text-indent:-.25in;mso-list:
l2 level3 lfo7'><![if !supportLists]><span style='mso-list:Ignore'>1.<span
style='font:7.0pt "Times New Roman"'> </span></span><![endif]> Editorial
Defect <o:p></o:p></p>
<p class=MsoPlainText style='margin-left:1.5in;text-indent:-.25in;mso-list:
l2 level3 lfo7'><![if !supportLists]><span style='mso-list:Ignore'>2.<span
style='font:7.0pt "Times New Roman"'> </span></span><![endif]>Technical
Defect<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:1.5in;text-indent:-.25in;mso-list:
l2 level3 lfo7'><![if !supportLists]><span style='mso-list:Ignore'>3.<span
style='font:7.0pt "Times New Roman"'> </span></span><![endif]>No
change required<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:1.5in;text-indent:-.25in;mso-list:
l2 level3 lfo7'><![if !supportLists]><span style='mso-list:Ignore'>4.<span
style='font:7.0pt "Times New Roman"'> </span></span><![endif]>further
consideration required<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:1.0in;text-indent:-.25in;mso-list:
l5 level2 lfo6'><![if !supportLists]><span style='font-family:"Courier New"'><span
style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>Case 2 was designed with the intent of the
correction to the defect being approved and published as quickly as possible,
so that implementations of the standard get based on corrected text. It implies
that the problem is recognized and the correction readily available (either from
the defect report submitter or devised by the Editing Group). To expedite
the correction of the defect, the vote is a three-months letter ballot in the SC,
initiated by the SC Secretariat upon reception of the proposed Technical
Corrigendum from the Project Editor. If the vote is positive, the accompanying comments,
if any, are dealt with by the Project Editor, again in the interest of a
timely correction. Publication is deemed to occur quickly.<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:1.0in;text-indent:-.25in;mso-list:
l5 level2 lfo6'><![if !supportLists]><span style='font-family:"Courier New"'><span
style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>Case 4 is the situation where there is no
urgency in modifying the standard, ie the proposed change or addition does not
impact the application of the standard nor the interoperability of implementations.
In this case, the item is referred to the WG, for development of a full
proposal (with the defect report as a starting point), which is carried
along the normal procedure and results in an Amendment. The procedure for
development of an amendment is the same as for the development of a standard,
ie either a new work item (3 months ballot at JTC1 level) or subdivision
of an ongoing work item, followed (or concurrent with) the development of a
proposal, then approval at ISO/IEC level. Considering the possible groupings,
in practice 8-10 months are a minimum.<o:p></o:p></p>
<p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l5 level1 lfo6'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>An amendment to a standard is typically a new piece of the
standard (which may be prompted by a Defect Report or by a NB or liaison
request). The process is designed so that NBs are able to plan the
corresponding allocation of resources (it is one of the functions of the NWI or
subdivision step) for something which is to be designed, while a Corrigendum does
not need this resource allocation (the change is already available and the vote
at SC level, ie among the experts that have likely been associated to the discussion).
In terms of volume, there is no precise rule, but a quick look at published
standards in the ISO store (<a href="http://www.iso.org/iso/iso_catalogue..htm">http://www.iso.org/iso/iso_catalogue.htm</a>
) show that Technical Corrigenda are often short (one or two pages) while
Amendments, much less frequent, correspond to a more substantial piece of
standardisation. See for example ISO/IEC 10118-2:2000/Cor 2:2007, 2 pages, vs ISO/IEC
10118-3:2004/Amd 1:2006 <b>, </b>Dedicated Hash-Function 8 (SHA-224), 16
pages.<b> </b><o:p></o:p></p>
<p class=MsoPlainText style='margin-left:.5in;text-indent:-.25in;mso-list:l5 level1 lfo6'><![if !supportLists]><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>It must be noted that the two solutions are not
automatically exclusive, in particular in difficult cases. For example, a
Defect Report may raise a real problem which needs to be fixed quickly, however
the fix processed as a Technical Corrigendum may be conservative (merely making
sure that implementations are not at risk) while a longer-term, more
comprehensive solution will need to be worked out as an Amendment. <o:p></o:p></p>
<p class=MsoPlainText style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoPlainText>There is a meeting of the JTC1 Directives group next week
in Delft (Netherlands). Although it is too late for making a formal
contribution to this group, it may be possible for NB delegations, if they find
some of the provisions of the Directives unclear, to discuss the matter
informally with other delegations, the JTC1 Chairman or the ITTF
representative. The ITTF representative in these meetings is usually very
helpful. <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Best regards<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Isabelle<o:p></o:p></p>
<p class=MsoPlainText>-----Original Message-----<br>
From: Francis Cave [mailto:francis@franciscave.com] <br>
Sent: Thursday, February 19, 2009 6:34 AM<br>
To: e-SC34-WG4@ecma-international.org<br>
Subject: RE: COR .vs. AM<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>What is the meaning of "ambiguity" in the JTC 1
Directives? The only<o:p></o:p></p>
<p class=MsoPlainText>possible interpretation is that the text of the standard
is ambiguous if it<o:p></o:p></p>
<p class=MsoPlainText>is possible to implement it in two or more inconsistent
ways, based upon<o:p></o:p></p>
<p class=MsoPlainText>various differing interpretations of the ambiguity. I
think one can argue<o:p></o:p></p>
<p class=MsoPlainText>that any correction of an ambiguity will carry a high
risk of breaking<o:p></o:p></p>
<p class=MsoPlainText>implementations that have interpreted the ambiguity
"incorrectly", i.e. to<o:p></o:p></p>
<p class=MsoPlainText>mean something different from what is finally agreed that
it should mean.<o:p></o:p></p>
<p class=MsoPlainText>The results before and after such a change will in such
cases not, in<o:p></o:p></p>
<p class=MsoPlainText>general, be the same. If one is to accept what ITTF are
saying, that would<o:p></o:p></p>
<p class=MsoPlainText>suggest that no ambiguities can be corrected by a COR but
only by an AMD. I<o:p></o:p></p>
<p class=MsoPlainText>don't believe that their interpretation is reasonable.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Francis Cave<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>> From: Rex Jaeschke [mailto:rex@RexJaeschke.com]<o:p></o:p></p>
<p class=MsoPlainText>> Sent: 19 February 2009 13:42<o:p></o:p></p>
<p class=MsoPlainText>> To: e-SC34-WG4@ecma-international.org<o:p></o:p></p>
<p class=MsoPlainText>> Subject: RE: COR .vs. AM<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> In December, I raised this question with an editor
at ITTF in Geneva.<o:p></o:p></p>
<p class=MsoPlainText>> Here<o:p></o:p></p>
<p class=MsoPlainText>> is the relevant extract from his reply:<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> "From a JTC 1 Directives perspective what is
important is the result<o:p></o:p></p>
<p class=MsoPlainText>> achieved when the standard (ISO 29500) is applied.
In other words, if<o:p></o:p></p>
<p class=MsoPlainText>> someone applies ISO 29500 prior to some change, and
another person<o:p></o:p></p>
<p class=MsoPlainText>> applies<o:p></o:p></p>
<p class=MsoPlainText>> ISO 29500 after that change, will the result(s)
achieved by the two be<o:p></o:p></p>
<p class=MsoPlainText>> identical?<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> If the change has no impact on the result achieved
when applying ISO<o:p></o:p></p>
<p class=MsoPlainText>> 29500,<o:p></o:p></p>
<p class=MsoPlainText>> then a Corrigendum (DR) is sufficient. If the change
does, then an<o:p></o:p></p>
<p class=MsoPlainText>> Amendment<o:p></o:p></p>
<p class=MsoPlainText>> or revision is required."<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> I've decided that that explanation really is
insufficient. Let me use a<o:p></o:p></p>
<p class=MsoPlainText>> specific example:<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> We treated DR 08-0009 (from GB) as a DR and we
closed it. It relates to<o:p></o:p></p>
<p class=MsoPlainText>> the<o:p></o:p></p>
<p class=MsoPlainText>> WordprocessingML field usage FILESIZE \k and
FILESIZE \m.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Consider the case in which an implementer originally
interpreted<o:p></o:p></p>
<p class=MsoPlainText>> kilobytes<o:p></o:p></p>
<p class=MsoPlainText>> to mean 1024 bytes. If they apply the fix as we
agreed, the result of<o:p></o:p></p>
<p class=MsoPlainText>> this<o:p></o:p></p>
<p class=MsoPlainText>> field is now in thousands of bytes. Clearly, for
many files, the result<o:p></o:p></p>
<p class=MsoPlainText>> before and after the fix was applied would be
different. So, should<o:p></o:p></p>
<p class=MsoPlainText>> that<o:p></o:p></p>
<p class=MsoPlainText>> have been processed as an amendment? Actually, our
rationale for making<o:p></o:p></p>
<p class=MsoPlainText>> it a<o:p></o:p></p>
<p class=MsoPlainText>> DR was that the result of this fix was always the
initial intent and<o:p></o:p></p>
<p class=MsoPlainText>> that's<o:p></o:p></p>
<p class=MsoPlainText>> was existing implementations did. That is, it was an
oversight.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> The JTC 1 Directives give the following guidance,
but they still appear<o:p></o:p></p>
<p class=MsoPlainText>> to<o:p></o:p></p>
<p class=MsoPlainText>> leave room for interpretation:<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> technical defect - A technical error or ambiguity in
an IS<o:p></o:p></p>
<p class=MsoPlainText>> inadvertently<o:p></o:p></p>
<p class=MsoPlainText>> introduced either in drafting or in printing which
could lead to<o:p></o:p></p>
<p class=MsoPlainText>> incorrect<o:p></o:p></p>
<p class=MsoPlainText>> or unsafe application of the IS.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> technical addition or change - Alteration or
addition to previously<o:p></o:p></p>
<p class=MsoPlainText>> agreed<o:p></o:p></p>
<p class=MsoPlainText>> technical provisions in an existing IS.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> An amendment is issued to publish a technical
addition or change.<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> Rex<o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> > -----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>> > From: Shawn Villaron
[mailto:shawnv@exchange.microsoft.com]<o:p></o:p></p>
<p class=MsoPlainText>> > Sent: Wednesday, February 18, 2009 9:36 PM<o:p></o:p></p>
<p class=MsoPlainText>> > To: MURATA Makoto (FAMILY Given);
e-SC34-WG4@ecma-international.org<o:p></o:p></p>
<p class=MsoPlainText>> > Subject: RE: COR .vs. AM<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > Murata-san,<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > I think the biggest disconnect here is what
constitutes a bug fix<o:p></o:p></p>
<p class=MsoPlainText>> > versus an extension. Do you have any
thoughts as to guidance we<o:p></o:p></p>
<p class=MsoPlainText>> could<o:p></o:p></p>
<p class=MsoPlainText>> > provide regarding the how to differentiate
between a bug fix and an<o:p></o:p></p>
<p class=MsoPlainText>> > extension?<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > Thanks,<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > shawn<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > -----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>> > From: MURATA Makoto (FAMILY Given)
[mailto:eb2m-mrt@asahi-net.or.jp]<o:p></o:p></p>
<p class=MsoPlainText>> > Sent: Wednesday, February 18, 2009 6:04 PM<o:p></o:p></p>
<p class=MsoPlainText>> > To: e-SC34-WG4@ecma-international.org<o:p></o:p></p>
<p class=MsoPlainText>> > Subject: COR .vs. AM<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > The convenor wrote:<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > >In the Prague meeting, I would like WG4 to
decide (1) whether they<o:p></o:p></p>
<p class=MsoPlainText>> are<o:p></o:p></p>
<p class=MsoPlainText>> > >defects and (2) whether we should create
amendments for handling<o:p></o:p></p>
<p class=MsoPlainText>> them.<o:p></o:p></p>
<p class=MsoPlainText>> > >I would request every member body to think
about these questions in<o:p></o:p></p>
<p class=MsoPlainText>> > >advance.<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > The member body for Japan prefers amendments
when proposed solutions<o:p></o:p></p>
<p class=MsoPlainText>> > are actually extensions rather than bug fixes.<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > Cheers,<o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> > --<o:p></o:p></p>
<p class=MsoPlainText>> > MURATA Makoto (FAMILY Given)
<EB2M-MRT@asahi-net.or.jp><o:p></o:p></p>
<p class=MsoPlainText>> ><o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText>> <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
</div>
</body>
</html>