<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:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">This looks like another topic for next week but, on initial investigation, I agree. Annex H [Murata-san, I think you were off-by-one]
is far too wordy and data-focused to be informative, and only contains information repeated elsewhere. I think there might still be a use for a truly informative description of OPC packages, but something much more high-level along the lines of “<i>A valid
OPC package contains data stored in parts (9.1), indexed in a Content Types Part (9.1.2), and references from parts to other parts are made using relationships (9.3) defined in a Relationships Part (9.3.1). All content is stored in a physical package (10).</i>”
I can see some value in some sort of drawn-out version of that, but not the normative-style declarations in the current Annex H.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">We’d need to remove all reference to “conformance requirements” in clause 2, as these requirements were only specified in an informative
annex. Which is a bit odd in itself.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">Chris<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" 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> 14 September 2014 19:43<br>
<b>To:</b> SC34<br>
<b>Subject:</b> On Annex G of 29500-2<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Folks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would argue that Annex G (Guidelines for Meeting Conformance) <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">should be dropped and that Clause 2 (Conformance) should be <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">modified accordingly.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">First, Annex G adds nothing new. It merely repeats what is<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">already stated elsewhere.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Second, Annex G is a partial and misleading list of<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">requirements. This is because it is very difficult or even<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">impossible for Annex G to repeat all requirements in the body.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">For example, some of the requirements (e.g, permissible<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">locations of isegments) in the EBNF have never been captured by<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Annex G.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Third, maintaining Annex G in accordance with the body is a<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">heavy burden for this revision.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Fourth, I believe that standards on data should focus on<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">requirements on data rather than those on applications. In<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">fact, Clause 2 already says "OPC conformance is purely<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">syntactic." Requirements on creators should always be captured<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">as requirements on data. Some requirements on consumers may be<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">rewritten as recommendations to consumers.<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>
<p class="MsoNormal">Regards,<br>
Makoto <o:p></o:p></p>
</div>
</div>
</body>
</html>