<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Rex<br>
<br>
I'm not sure about the last sentence. It seems to say: "...to limit
changes ... to those that would make existing documents invalid." I
think you meant to say "... to limit the number of changes ... that
would make existing documents invalid.". Otherwise it would seem that
we are trying to invalidate existing documents through the changes
proposed!<br>
<br>
Francis<br>
<br>
<br>
<br>
Rex Jaeschke wrote:
<blockquote cite="mid00b601ca72f1$018aaa30$049ffe90$@com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@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";}
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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]-->
<div class="Section1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Here’s
the proposed
wording to deal with the comments regarding moving corrections from the
DCOR1
set to the FPDAM1 set. I have taken my original words and integrated
the suggestions
from Alex and Francis. This response will go with each of these
comments
including those also having individual responses (such as MY-0001).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Rex<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">“Rejected.
Technical
corrigenda inherently address technical issues identified with the
standard. As such, it is virtually impossible to have them avoid
impacting existing implementations. </span><span
style="color: rgb(31, 73, 125);" lang="EN-GB">When a technical defect
in a feature is corrected, all
existing implementations of that feature, that did not interpret it as
if the
correction had already been made, will be broken to some extent by the
change.
In other words, Corrigenda routinely break all existing implementations
that
have failed to anticipate the correction. </span><span
style="color: rgb(31, 73, 125);">WG4
understands the necessity of providing a stable standard for
implementers and,
as such, has acted in good faith to limit changes proposed via
technical
corrigenda to those that would make existing documents invalid.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
</blockquote>
</body>
</html>