<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:"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:0cm;
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:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Preprocessing:<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>The Oxford online dictionary defines the verb “preprocess”, and gives the following example of its use in the gerund form:<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>“some preprocessing of the concordances is a desirable prerequisite to editing”<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>See <a href="https://en.oxforddictionaries.com/definition/preprocess">https://en.oxforddictionaries.com/definition/preprocess</a>. <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Francis<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> caroline arms <caroline.arms@gmail.com> <br><b>Sent:</b> 04 April 2018 18:46<br><b>To:</b> MURATA Makoto <eb2m-mrt@asahi-net.or.jp><br><b>Cc:</b> SC 34 WG4 <e-SC34-WG4@ecma-international.org><br><b>Subject:</b> Comments on Latest OPC draft -- Miscellaneous areas.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Sorry about the blank message I sent recently. Operator error with my mouse!!<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>This batch of comments relate to annexes and the bibliography.<o:p></o:p></p></div><div><p class=MsoNormal> Caroline<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Annex A.<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>2nd para<br>This preprocessing is neither required nor recommended.<o:p></o:p></p></div><p class=MsoNormal>Issue 1 I have never heard of "preprocessing" being used as a noun. Word's grammar-checking function objects to it, but not because it is wants to see a hyphen, although I would prefer to see one. I suggest "pre-processing outline" or "pre-processing procedure" or "pre-processing suggestion."<o:p></o:p></p><div><div><div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Issue 2<o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>I immediately think: if it is "not recommended" why is it here at all?<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>I assume "recommended" is a term of art, but we really need to change the wording here somehow. Perhaps one of the other native English speakers has a good suggestion. I might say something like.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>This pre-processing outline is not required. It is an example of an appropriate sequence of steps.<o:p></o:p></p></div><div><p class=MsoNormal>The pre-processing suggestion has eight steps<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Annex G. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>There was no Annex in the 2012 published edition of Part 2 devoted to streaming consumption. Perhaps we could give a hint to the fact that the requirements were in the Package model clause. I'm puzzled about the relationship of Annex F and Annex G and wondering whether the statement about dropping requirements associated with streaming consumption could be slipped in to Annex F instead.<br><br><o:p></o:p></p></div><div><p class=MsoNormal>Former Annex H: Guidelines for Meeting Conformance<o:p></o:p></p></div><div><p class=MsoNormal>Is it time to go through the old Annex H and identify any requirements that are not incorporated into the current OPC draft. I'm thinking about this because of the comments in 8.5.3.1 where Murata-San says he doesn't remember why the requirement that was re-iterated in Annex H at M1.25 was dropped. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p></div><p class=MsoNormal>Bibliography item 1. the URL <a href="https://www.w3.org/TR/charmod-norm/">https://www.w3.org/TR/charmod-norm/</a> currently refers to a W3C Working Draft from 07 April 2016. However, when there is a new published draft, it will point to that. If we want to ensure that we keep pointing to the 2016 published draft, we should use <a href="http://www.w3.org/TR/2016/WD-charmod-norm-20160407/">http://www.w3.org/TR/2016/WD-charmod-norm-20160407/</a> <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>FYI, there is a more recent, un-published draft. See <a href="http://w3c.github.io/charmod-norm/">http://w3c.github.io/charmod-norm/</a> -- which was date<span style='font-size:10.0pt'>d 25 February 2018 when I checked today.<br><br></span><o:p></o:p></p></div></div></div></div></div></div></div></body></html>