<div dir="ltr">Dear colleagues,<div><br></div><div>I studied WG4 N344, DR 10-0048 (Annex C Changes). Attached </div><div>please find an improved draft.</div><div><div><br></div><div><div>First, I find the whole point of Table C-7 is to allow an Microsoft</div><div>extra field for representing growth hints. I thus reintroduced this</div><div>table, referenced 9.3.8 (Growth hint) from this table, and referenced</div><div>this table from the description of extra fields.</div><div><br></div><div>Second, I replaced "No" by "Not allowed". "No" is a bit confusing,</div><div>since it can be interpreted as "no additional constraints by this</div><div>specification". But "Not allowed" clearly prohibits the particular</div><div>construct.</div><div><br></div><div>Third, I corrected some mistakes in the "version needed to extract"</div><div>field. 1.0, 1.1, and 2.0 should not be marked as "Not allowed".</div><div>Indeed, these are used by MS Word.</div><div><br></div><div>Fourth, I mistakenly disallowed "no compression" in Table 4. Fixed.</div><div><br></div><div>Fifth, in Table C-6, I mistakenly marked almost all fields as</div><div>"Partially -- the value shall be set to 0". They should be simply</div><div>disallowed. Note that extra fields do not have to exist. Fixed.</div><div><br></div><div>Fourth, I do not understand what is meant by "All 64-bit stream record</div><div>sizes and offsets shall have the high-order bit = 0. [M3.20]" at the</div><div>end of this annex. What does this mean?</div></div><div><br></div><div>Regards,</div><div>Makoto</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-12 8:25 GMT+09:00 MURATA Makoto <span dir="ltr"><<a href="mailto:eb2m-mrt@asahi-net.or.jp" target="_blank">eb2m-mrt@asahi-net.or.jp</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Unfortunately, the draft after the Kyoto meeting is lost. I created a new <div>rewrite.</div><div><br></div><div>Regards,</div><div>Makoto</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2014-06-19 20:42 GMT+09:00 Chris Rae <span dir="ltr"><<a href="mailto:Chris.Rae@microsoft.com" target="_blank">Chris.Rae@microsoft.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">One piece of information I think is lost in my current draft is the records for which “supported” is “no” but “pass-through on editing” is set to “yes” (this
includes the one DR 10-0048 was originally directed at). I’m wondering whether we could introduce a setting of “Ignored”, meaning that the record is permitted to exist in an OPC file but an OPC consumer must not use its content. It would then be down to implementations
to determine whether to round-trip the record or not.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chris<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Francis Cave [mailto:<a href="mailto:francis@franciscave.com" target="_blank">francis@franciscave.com</a>]
<br>
<b>Sent:</b> Thursday, June 19, 2014 12:11<br>
<b>To:</b> <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
<b>Subject:</b> RE: DR 10-0048 (OPC Annex C) proposed changes<u></u><u></u></span></p>
</div>
</div><div><div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">In the Table Key at the top of C.3 the term “Optional” is defined, but is not used in any of the tables. I think this relates to Chris’ comment
as to whether ‘Yes’ always means ‘may’ or perhaps sometimes means ‘must’.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Francis<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:eb2mmrt@gmail.com" target="_blank">eb2mmrt@gmail.com</a> [<a href="mailto:eb2mmrt@gmail.com" target="_blank">mailto:eb2mmrt@gmail.com</a>]
<b>On Behalf Of </b>MURATA Makoto<br>
<b>Sent:</b> 19 June 2014 02:26<br>
<b>To:</b> <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
<b>Subject:</b> Re: DR 10-0048 (OPC Annex C) proposed changes<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">I love this rewrite. Thanks!<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Regards,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Makoto<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">2014-06-19 7:22 GMT+09:00 Chris Rae <<a href="mailto:Chris.Rae@microsoft.com" target="_blank">Chris.Rae@microsoft.com</a>>:<u></u><u></u></span></p>
<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">
<p class="MsoNormal"><span lang="EN-GB">Attached is a first draft of my proposed rewording of OPC's Annex C. I've tried to cut it down so that the annex refers only to the file format and not to implementations, and as a result have removed quite a lot of normative
text that I believe was relevant only to the MS Office implementation. More work is definitely needed (I've added questions as comments in several places) but hopefully we can use this as a draft to continue work from.<br>
<span style="color:#888888"><br>
<span>Chris</span></span><u></u><u></u></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-GB"><br>
<br clear="all">
<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB">-- <br>
<br>
Praying for the victims of the Japan Tohoku earthquake<br>
<br>
Makoto <u></u><u></u></span></p>
</div>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature"><br>Praying for the victims of the Japan Tohoku earthquake<br><br>Makoto</div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><br>Praying for the victims of the Japan Tohoku earthquake<br><br>Makoto</div>
</div>