<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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: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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@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>As those of you who have followed the thread with subject “ Which RFC(s) for media type should we refer to?” will realize, I got started with looking at the issue of content type and media type. I have now stopped, waiting for experts in BNF and regular expressions to figure out how best to specify the syntax needed for media types in OPC.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My suggestions so far are:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText>4.9<o:p></o:p></p><p class=MsoPlainText>content type<o:p></o:p></p><p class=MsoPlainText>characterization of the content stored in a part<o:p></o:p></p><p class=MsoPlainText>Note: In this standard the values used for characterizing content are Internet media types as defined in RFC ???? [TBD]<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>4.26<o:p></o:p></p><p class=MsoPlainText>part<o:p></o:p></p><p class=MsoPlainText>stream of bytes with a content type and associated common properties [dropping “MIME” – should we mention that a part is in a package, or does that make the definitions look circular?]<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>7. Overview<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Para 1.<o:p></o:p></p><p class=MsoNormal>Currently:<o:p></o:p></p><p class=MsoNormal>"This Open Packaging specification describes an abstract model and physical format conventions for the use of XML, Unicode, ZIP, and other openly available technologies and specifications to organize the content and resources of a document within a package. It is intended to support the content types and organization for various applications and is written for developers who are building systems that process package content."<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Suggested re-wording:<o:p></o:p></p><p class=MsoNormal>"This Open Packaging specification describes an abstract model and physical format conventions for the use of XML, Unicode, ZIP, and other openly available technologies and specifications to organize the content and resources of a document within a package. The package specification is intended to support typing and organization of related resources for various applications. The specification is written for developers who are building systems that process package content."<o:p></o:p></p><p class=MsoNormal>====<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have held back on clause 8 changes pending decision on the source we finally choose for specifying the syntax for Internet media types.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve been minimalist in these suggested changes, but would be happy to support further clarifications.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Caroline<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Caroline Arms<o:p></o:p></p><p class=MsoNormal>Library of Congress Contractor<o:p></o:p></p><p class=MsoNormal>Co-compiler of Sustainability of Digital Formats resource <a href="http://www.digitalpreservation.gov/formats/"><span style='color:blue'>http://www.digitalpreservation.gov/formats/</span></a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>** Views expressed are personal and not necessarily those of the institution **<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>