<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=us-ascii"><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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
--></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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Recording your second point Murata-san, of course Annex H has no new requirements; it’s clearly marked as being informative!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For convenience, all the rules are gathered here, so a reader can find them easily by rule number. In order to avoid synchronization errors, the rule text in that annex is not hard-coded; it gets copied verbatim from the normative text via named bookmarks when references are updated.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So, if that annex is not wrong, then it might be useful for some readers (especially those outside of WG4). To those who don’t care to read it, they can simply ignore it. What’s to be concerned about?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>And why should all the Parts of 29500 have similar-looking annexes? Clearly, Parts 2 and 3 are quite different from each other and from Parts 1 and 4.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rex<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></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"'> eb2mmrt@gmail.com [mailto:eb2mmrt@gmail.com] <b>On Behalf Of </b>MURATA Makoto<br><b>Sent:</b> Tuesday, February 04, 2014 7:41 AM<br><b>To:</b> John Haug<br><b>Cc:</b> SC34<br><b>Subject:</b> SPAM-HIGH: Re: Proposed overview/scope of work for OPC revision<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>OPC conformance has been an issue even before the BRM.<o:p></o:p></p><div><p class=MsoNormal>Although there were a number of improvements in the BRM, <o:p></o:p></p></div><div><p class=MsoNormal>I still have two concerns.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>First, although OPC conformance is now defined as purely <o:p></o:p></p></div><div><p class=MsoNormal>data conformance, many sentences in OPC look like application <o:p></o:p></p></div><div><p class=MsoNormal>conformance.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Second, Annex H <o:p></o:p></p></div><div><p class=MsoNormal>provides copies of normative sentences in the body, without <o:p></o:p></p></div><div><p class=MsoNormal>any new requirements. No other parts of OOXML have such <o:p></o:p></p></div><div><p class=MsoNormal>Annex.<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></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>2014-01-08 John Haug <<a href="mailto:johnhaug@exchange.microsoft.com" target="_blank">johnhaug@exchange.microsoft.com</a>>:<o:p></o:p></p><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=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>To reach consensus on scope and to better understand what we’re intending to accomplish before we get lost in details, may I suggest the following as the list of topics we want to address in our changes to Part 2? All open DRs marked for Part 2 should be included below. Anything to add/remove/change before we agree on what we’re going to do?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I’m going to try to organize a set of reference info, more thorough than the short list I sent out quickly on Thursday, to include numerous of old e-mail threads, documents, etc. If I am able to do so, I may put it on a new Wiki page on the WG 4 Assembla wiki (<a href="https://www.assembla.com/spaces/IS29500/wiki" target="_blank">https://www.assembla.com/spaces/IS29500/wiki</a>). I would also add the below, plus changes.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>1. Combining IRI/URI<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0280 – general DR about sections of OPC assuming non-ASCII is disallowed<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0281 – terminology; all uses of “part” should specify what kind of part is meant<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0283 – similar to 09-0280<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0284 – terminology; need to re-associate the ABNF term names with the prose for part names<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0285 – terminology; use of “part IRI” and “part URI”<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0286 – need to update 9.2 (Part Addressing) to specify the format of a reference, based on the changes to be made to 9.1.1 (Part Names)<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0288 – same as 09-0286, but for 9.3.2 (Relationship Markup)<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0291 – terminology; specify what “Unicode string” means, based on the changes to be made to 9.1.1<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0292 – which characters are allowed in a part name (e.g., whitespace, delimiters, special characters) <o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>13-0002 – fix previous changes made to Annex H for introduction of non-ASCII support<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>Add cautionary language noting that implementations might only support ASCII/URIs? Anything to note in Part 1?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>2. Relative/absolute referencing<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>10-0015 – clarify “source part” for relationships<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>Add cautionary language about detailed interpretations of relative vs. absolute references as defined in RFC 3986?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>3. Pack URI<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0293 – decide how, and whether, to handle IANA registration<o:p></o:p></p><p style='margin-left:1.0in'><span style='font-family:"Courier New"'>o</span><span style='font-size:7.0pt'> </span>(see also historic info, including issues with Pack URI, here: <a href="http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml" target="_blank">http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml</a>, <a href="http://www.iana.org/assignments/uri-schemes/historic/pack" target="_blank">http://www.iana.org/assignments/uri-schemes/historic/pack</a>)<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>4. Digital signatures<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>11-0029 – is content from xmldsig-core duplicated in 13.2.4 (Digital Signature Markup)?<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>11-0030 – update normative reference to xmldsig-core?<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>11-0031 – update reference to xmlsec schema?<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>What, if anything, needs to be said about ensuring XAdES use is allowed?<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>5. Versioning<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>09-0168 – cannot distinguish between ECMA 1<sup>st</sup> ed OPC package and later versions (e.g., 29500 supports non-ASCII)<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>6. Editorial misc<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>12-0001 – unify capitalization of “relationship part”<o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>Remove reference to Part 3 from clause 8 (Overview)<o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <br><br>Praying for the victims of the Japan Tohoku earthquake<br><br>Makoto <o:p></o:p></p></div></div></body></html>