<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=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (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;}
@font-face
{font-family:"Calibri\,Italic";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
..MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal>DR-09-0032: General: Inappropriate use of “content
type”<o:p></o:p></p>
<p class=MsoNormal>DR-09-0034: General: Numerous media types should be
registered at IANA<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Greetings,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’ve been going through many of the items listed in
the latest defect log and I was hoping someone could help me better understand DR-09-0032
and DR-09-0034.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b>DR-09-0032<o:p></o:p></b></p>
<p class=MsoNormal>In DR-09-0032, it is pointed out that in the Terms and
Definitions section, we define the term <i>content type</i> and provide a
reference to RFC 2616. The issue is that the term as it is currently used
would better be described using the term <i>media type</i> and that the better
reference would be RFC 2046.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>While I can appreciate being as specific as possible
regarding the terminology we use, I believe the intent of the opening paragraph
was to pre-empt this issue ( bold emphasis mine ):<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in;text-autospace:none'>For the
purposes of this document, the following terms and definitions apply. Other
terms are defined where they appear in <i><span style='font-family:"Calibri,Italic","sans-serif"'>italic
</span></i>typeface, on the left side of a syntax rule, or within subclauses of
language-specific grammars (§17.16 and §18.17). <b>Terms explicitly defined in
this Part of ISO/IEC 29500 are not to be presumed to refer implicitly to
similar terms defined elsewhere</b>. [<i><span style='font-family:"Calibri,Italic","sans-serif"'>Note</span></i>:
This part uses OPC-related terms, which are defined in ISO/IEC 29500-2. <i><span
style='font-family:"Calibri,Italic","sans-serif"'>end note</span></i>]<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Regardless of the intent, I am curious as to what form of
remedy we are being asked for; for example, is the remedy to change the prose
only in the Terms and Definitions section, is it to change the prose throughout
the standard, and/or does it include making schema changes? For example, how
does this relate to the [Content_Types].xml part in OPC? Changes impacting
schema and OPC could have profound consequences to existing implementations as
well as the corpus of existing documents.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b>DR-09-0034<o:p></o:p></b></p>
<p class=MsoNormal>In DR-09-0034 we are being asked to register the set of
content types/media types found in the standard. I must admit that my
understanding with regard to the pros/cons of IANA registration is lacking.
Could someone help me understand the benefits of registering these types? Are
they any tangible consequences to their registration? Does the group have thoughts
as to which entity should do the registration? Learning a bit more about IANA
registration would help me evaluate the practical impact on interoperability
these changes would have. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks in advance,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>shawn<o:p></o:p></p>
</div>
</body>
</html>