<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.gmail-msonormal, li.gmail-msonormal, div.gmail-msonormal
{mso-style-name:gmail-msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1960599720;
mso-list-template-ids:-1513047684;}
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=WordSection1><p class=MsoNormal>I requested the exception in email to Richard Cook (the ITTF editor responsible for SC 34 projects at that time) and Henry Cuschieri, ITTF head, attaching the rationale I posted yesterday.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Here is the response from ITTF:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> Hannah EKBERG [mailto:EKBERG@iso.org] <br><b>Sent:</b> Thursday, May 24, 2012 1:27 PM<br><b>To:</b> Jaeschke Rex Mr. <rex@rexjaeschke.com><br><b>Cc:</b> Henry CUSCHIERI <CUSCHIERI@iso.org>; Richard COOK <COOK@iso.org><br><b>Subject:</b> ISO/IEC 29500 - ISO style rules exemption<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>Dear Rex Jaeschke,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>As the newly appointed editor to SC 34, I'm writing to you now to introduce myself, as well as to reply to you regarding your request for an exemption from ISO style rules for ISO/IEC 29500. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Firstly, I would like to say thank you for preparing such a detailed explanation for our team regarding your request; this is most helpful and we really appreciate your attention and concern to the matter.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Richard Cook and I have now discussed it in some detail, and given the circumstances that you've outlined, exceptionally <span style='background:lime;mso-highlight:lime'>we can accept your request</span>. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='background:lime;mso-highlight:lime'>Given the size and quantity of documents, we would also suggest that they are submitted as PDFs only. They will then be flagged to be processed as "Direct Publication" documents, which means that there will be little to no intervention in the documents, except for the cover pages and the introductory pages.</span><span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Thank you again for your attention to this matter and please don't hesitate to get in touch for any further concerns. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I'm looking forward to working with you in the future.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Hannah Ekberg<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN>Ms. Hannah Ekberg<br></span><i><span lang=EN-GB>Technical Editor<br></span></i><span lang=EN-GB>Standards Department<br><i><br></i>ISO Central Secretariat<i><br></i>1, chemin de la Voie Creuse<i><br></i>P.O. Box 56<i><br></i>CH-1211 Geneva 20<br><br>Tel. +41 22 749 01 11<br>Direct line +41 22 749 03 83<br>Fax +41 22 749 03 49<br><br>E-mail <a href="mailto:ekberg@iso.org"><span lang=EN>ekberg@iso.org</span></a><br>Web <a href="../../../../../../Documents%20and%20Settings/ekberg/Application%20Data/Microsoft/Signatures/www.iso.org"><span lang=EN>www.iso.org</span></a></span><span lang=EN-GB style='mso-fareast-language:EN-GB'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> eb2mmrt@gmail.com [mailto:eb2mmrt@gmail.com] <b>On Behalf Of </b>MURATA Makoto<br><b>Sent:</b> Friday, November 24, 2017 7:27 PM<br><b>To:</b> SC 34 WG4 <e-SC34-WG4@ecma-international.org><br><b>Cc:</b> TC45 <e-TC45@ecma-international.org><br><b>Subject:</b> SPAM-LOW: Re: Editions of 29500-1 (Strict) and 29500-4 (Transitional) beyond 2016<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Rex,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>2017<span style='font-family:"MS Gothic"'>年</span>11<span style='font-family:"MS Gothic"'>月</span>25<span style='font-family:"MS Gothic"'>日</span>(<span style='font-family:"MS Gothic"'>土</span>) 9:06 Rex Jaeschke <<a href="mailto:rex@rexjaeschke.com" target="_blank">rex@rexjaeschke.com</a>>:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=gmail-msonormal>The exemption from a few of the Directives-Part-2 rules resulted from a request from me to IITF. (That request is attached.) ITTF granted that request.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I have not been aware of your request and the reply from ITTF. Where <o:p></o:p></p></div><div><p class=MsoNormal>is the reply from ITTF?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>During the DIS ballot for 29500-3, Japan requested conformance to <o:p></o:p></p></div><div><p class=MsoNormal>Directives part 2. Most of the comments were accepted.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><a href="http://mailman.vse.cz/pipermail/sc34wg4/2014-September/003316.html">http://mailman.vse.cz/pipermail/sc34wg4/2014-September/003316.html</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Makoto<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Separately, ITTF agreed to accept PDF-only from us, and Kimura-san is aware of that; I only send her PDF submissions for forwarding to ITTF.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Rex<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal><b>From:</b> <a href="mailto:eb2mmrt@gmail.com" target="_blank">eb2mmrt@gmail.com</a> [mailto:<a href="mailto:eb2mmrt@gmail.com" target="_blank">eb2mmrt@gmail.com</a>] <b>On Behalf Of </b>MURATA Makoto<br><b>Sent:</b> Friday, November 24, 2017 5:54 PM<o:p></o:p></p></div></div><div><div><p class=gmail-msonormal><br><b>To:</b> SC 34 WG4 <<a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a>><br><b>Cc:</b> TC45 <<a href="mailto:e-TC45@ecma-international.org" target="_blank">e-TC45@ecma-international.org</a>><o:p></o:p></p></div></div><div><div><p class=gmail-msonormal><b>Subject:</b> SPAM-LOW: Re: Editions of 29500-1 (Strict) and 29500-4 (Transitional) beyond 2016<o:p></o:p></p></div></div><div><div><p class=gmail-msonormal> <o:p></o:p></p><div><p class=gmail-msonormal>Rex,<o:p></o:p></p><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal>Thanks for the clarification.<o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal>I thought that we have been exempted from conformance <o:p></o:p></p></div><div><p class=gmail-msonormal>to Directives, part 2 only because we have had DCOR <o:p></o:p></p></div><div><p class=gmail-msonormal>ballots and consolidation. I will speak with Kimura-san <o:p></o:p></p></div><div><p class=gmail-msonormal>about this.<o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal>We can start a letter ballot if any SC34 decisions are <o:p></o:p></p></div><div><p class=gmail-msonormal>needed.<o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal>Regards,<o:p></o:p></p></div><div><p class=gmail-msonormal>Makoto <o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div></div></div></div><div><div><div><div><p class=gmail-msonormal>2017-11-25 1:57 GMT+09:00 Francis Cave <<a href="mailto:francis@franciscave.com" target="_blank">francis@franciscave.com</a>>:<o:p></o:p></p></div></div></div></div><div><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=gmail-msonormal><span lang=EN-GB>Rex</span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB> </span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB>Thanks for this clarification. There are no current Resolutions of SC 34 that would make it possible to initiate a CD ballot on revisions of Parts 1 and 4, so this will need to be agreed by SC 34, probably at the next Plenary. I’m not aware of there being any particular urgency for this. It can also be argued that there is little point in publishing CORs for Parts 1 and 4, if a revision is likely to be published within a year of publishing a COR.</span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB> </span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB>Kind regards,</span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB> </span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB>Francis</span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB> </span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB> </span><o:p></o:p></p><p class=gmail-msonormal><span lang=EN-GB> </span><o:p></o:p></p></div></div></blockquote></div></div></div></div><div><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=gmail-msonormal><b>From:</b> Rex Jaeschke [mailto:<a href="mailto:rex@RexJaeschke.com" target="_blank">rex@RexJaeschke.com</a>] <br><b>Sent:</b> 24 November 2017 14:52<o:p></o:p></p></div></div></div></div></blockquote></div></div></div></div><div><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=gmail-msonormal><b>To:</b> SC 34 WG4 <<a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a>><br><b>Cc:</b> TC45 <<a href="mailto:e-TC45@ecma-international.org" target="_blank">e-TC45@ecma-international.org</a>><br><b>Subject:</b> Editions of 29500-1 (Strict) and 29500-4 (Transitional) beyond 2016<o:p></o:p></p></div></div></div></div></blockquote></div></div></div></div><div><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=gmail-msonormal><span lang=EN-GB> </span><o:p></o:p></p><p class=gmail-msonormal>Murata-san sent the following to me privately. I’m replying to the whole group, so hopefully we can avoid further confusion on this topic:<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Murata-san: I thought that we are going to create DCORs for 29500-1/4, finish the DCOR ballots, and then go for a DIS ballot after incorporating editorial changes. But I cannot find any records for our decisions for DCORs. Am I missing something?<o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>We’ve discussed this several times; here’s my understanding.<o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal>From the minutes of the Barcelona, ES, meeting 2016-02<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal style='break-after: avoid'><b><u><span lang=EN-GB>The Next Editions of 29500-1/-4 beyond 20017</span></u></b><o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>We froze the content of the 2015 editions about a year ago. Since then, any DRs closed that modify Parts 1 or 4 have been labelled “Closed in COR4”. Newly closed DRs will be labelled likewise. (As they all refer to clause and page numbering from the 2012 edition, these references will all have to be changed to the 2016 edition, once that becomes available.)<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>We have <u>never</u> done a revision of Parts 1 and 4; we’ve simply produced one or more CORs and then rolled them into a consolidated reprint of the previous base standard to produce a new one. Going forward, we’ll probably want to go through the more formal revision process, at the very least so we can incorporate the fixes for those DRs that require lots of fiddly editing that are onerous to describe in a DR/COR. However, we can limit the revision to that and to the incorporation of DR resolutions, and we don’t have to start the formal revision process until we pretty much have a final WD.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>We can discuss this further in future F2F meetings.<o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>The Barcelona meeting was before the 2016 issue was completed. For previous editions, we’d produced 1 or 2 CORs, which were balloted in SC 34 only. Then I applied those CORs to the base standard to produce what used to be known as “a consolidated reprint”. As this needed *<b>no</b>* further balloting, it was published directly, and the whole process was editorial. <o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>ISO ITTF changed the process starting with the 2016 edition. Once I applied the CORs to the base standard, ITTF told us we had to do a combined JTC 1 ballot, which meant JTC 1, ISO, and ISO members all got a vote, instead of just SC 34 members. This delayed the process, but no changes resulted from those ballots. We were told by ITTF that we’d have to do this with future editions.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>The consolidated reprint idea is no more. What we have now is always called a “revision”, a term we’ve long avoided using.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Going forward, our options are to produce zero or more CORs. When we are ready to produce a new edition, we’d apply those CORs (if any) to the base standards, as before, and the whole thing would go to a combined ballot. However, the new capability is that since the result is considered a revision, we can make changes to the spec *<b>outside</b>* of the COR process. We discussed this, and I created two new dispositions for DRs that resulted in change: COR4 (edits go into the next COR) and REV3 (edits go into the next revision, but not via a COR).<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Candidates for REV3 are editorial changes, and certain (typically repetitive) technical changes for which we don’t want to write out every edit in the DR resolution. We first used this designation in Seoul.<o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>From the minutes of the Seoul, KR, meeting 2016-09<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><div style='border:solid windowtext 1.0pt;padding:1.0pt 4.0pt 1.0pt 4.0pt'><p class=gmail-msonormal style='break-after: avoid'><b><span lang=EN-GB>DR 15-0016 “DML: Remove drawingml namespace qualification from attributes in Part 1”</span></b><o:p></o:p></p></div><p class=gmail-msonormal>We agreed to close this, but rather than put it onto a COR, it can be put into the new edition along with editorial changes. Closed in REV3.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><div style='border:solid windowtext 1.0pt;padding:1.0pt 4.0pt 1.0pt 4.0pt'><p class=gmail-msonormal style='break-after: avoid'><b><span lang=EN-GB>DR 15-0017 “DML: Remove redundant drawingml attributes from Part 4”</span></b><o:p></o:p></p></div><p class=gmail-msonormal>We agreed to close this, but rather than put it onto a COR, it can be put into the new edition along with editorial changes. Closed in REV3.<o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>In Geneva, we assigned this designation to two more DRs we closed there.<o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>From the minutes of the Geneva, CH, meeting 2017-11<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><div style='border:solid windowtext 1.0pt;padding:1.0pt 4.0pt 1.0pt 4.0pt'><p class=gmail-msonormal style='break-after: avoid'><b><span lang=EN-GB>DR 16-0025 “Primer: Part 4 stuff”</span></b><o:p></o:p></p></div><p class=gmail-msonormal style='margin-top:6.0pt'>We agreed with Rex’s proposed approach. Closed in REV3.<o:p></o:p></p><div style='border:solid windowtext 1.0pt;padding:1.0pt 4.0pt 1.0pt 4.0pt'><p class=gmail-msonormal style='break-after: avoid'><b><span lang=EN-GB>DR 17-0010 “VML: Attribute examples”</span></b><o:p></o:p></p></div><p class=gmail-msonormal style='margin-top:6.0pt'>Murata-san presented his plan for resolving this issue. First, he’ll add the following subclauses, which because they are the end of their parent clauses, will not adversely affect section numbering.<o:p></o:p></p></div></div></blockquote></div></div></div></div><div><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=gmail-msonormal style='margin-top:6.0pt'><o:p></o:p></p></div></div></blockquote></div></div></div></div><div><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=gmail-msonormal style='margin-top:6.0pt'>Then he’ll move one copy of each attribute group to the corresponding new subclause, and he’ll delete all the duplicates <u>without change tracking</u>. He’ll add the necessary customized text to each affected element to point to its corresponding attribute group subclause.<o:p></o:p></p><p class=gmail-msonormal style='margin-top:6.0pt'>Closed in REV3.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal style='break-after: avoid'><b><u><span lang=EN-GB>29500-1 and 29500-4 WDs</span></u></b><o:p></o:p></p><p class=gmail-msonormal>Soon, Rex will start work on 29500-1 WD1, which will incorporate the resolutions for all closed DRs impacting Part 1. He plans to track the changes. He expects to be able to deliver this by the 2018-03 F2F meeting.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Once Murata-san has implemented the resolution of DR 17-0010, he’ll hand back ownership of 29500-4 to Rex, who will then produce 29500-4 WD1, which will incorporate the resolutions for all closed DRs impacting Part 4. He plans to track the changes. He expects to be able to deliver this by the 2018-03 F2F meeting.<o:p></o:p></p><div style='border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>As I’ve reported several times, I’ve started work on WD1 for 29500-4, and my plan is to complete that prior to the Prague meeting. My private copy of that draft contains the DRs closed as COR4, (and will contain any designated REV3) and *<b>also</b>* numerous editorial changes to correct/improve the English, none of which came from a DR. I plan to do the same for a WG1 for 29500-1.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Eventually, we’ll have a final WD that will be balloted and will become a new edition. As to whether we publish any CORs along the way has not yet been decided, not does it need to be any time soon. If we decide to publish a COR for Part 1 and/or 4, we can do so at any time, but that takes time and effort, and doesn’t help us in WG4, as we’ll already have our own internal consolidated reprint via the WD. <o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>So here are the steps leading to the next revision of 29500-1/-4:<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>If we think it necessary, we can produce one or more CORs, and ballot them in SC 34. (If we chose to *<b>not</b>* publish a CD, then all DRs marked COR4 will be treated as though they were marked REV3.)<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Eventually, we get permission from SC 34 to revise.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>I produce a CD for each Part, that is the 2016 standard + any COR4 fixes + any REV3 fixes<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>We have the (hopefully) Final CD ballot and then the combined (F)DIS ballot.<o:p></o:p></li></ol><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Recently, Murata-san questioned our having WDs without having asked for permission to do a revision. As a WG, we can have whatever WDs we want internally. It’s only when we want to have a CD that we need to have a revision project, and we don’t need a CD until we decide to start the clock ticking on the next edition, which will be called a revision.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>I hope this clarifies things,<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Rex<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p></div></div></blockquote></div></div></div></div><div><div><div><p class=gmail-msonormal><br><br clear=all><o:p></o:p></p><div><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal>-- <o:p></o:p></p><div><p class=gmail-msonormal><br>Praying for the victims of the Japan Tohoku earthquake<br><br>Makoto<o:p></o:p></p></div></div></div></div></blockquote></div></div></div></div></body></html>