<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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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>At the most recent face-to-face meeting, which I did not attend, Chris Rae was tasked with getting back to me about adding a second example to the section of his draft that covers embedding of foreign OPC Parts. I had expressed a wish to see a second example, since I believed that it had earlier been agreed that using a foreign/unknown part might be an appropriate way to add rich metadata in a standard or well-known schema to an OOXML document.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Chris did not contact me during the short period between the face-to-face and his leaving Microsoft and on the recent conference call, I agreed to make a proposal and ask others, particularly Francis, to review it before it is integrated into the draft.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Attached is my attempt to introduce the second example into subclause 3.5.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As I worked, a several questions came to mind:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. The first paragraph uses both ‘foreign part’ and ‘unknown part.’ I don’t see ‘foreign’ and ‘unknown’ as quite synonymous. To me ‘foreign’ means non-OOXML, but ‘unknown’ means not understood in some context. The use of both terms here is a bit confusing. Part 1 uses ‘unknown.’. See Part 1, 9.1.4. Should we clarify? Or use ‘foreign’ throughout?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. Is there any way to declare/register a relationship type that is specific to ONIX or rich metadata? Chris has just used example.org, which was “established to be used for illustrative examples in documents.” I would be hoping for something more appropriate. Would it be reasonable to use the same host as Editeur uses for ONIX namespace URLs – which don’t resolve? An example of an ONIX namespace URI: is http://ns.editeur.org/onix/3.0/short<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Francis: Do you know someone at Editeur? Might they be open to letting us use ‘ http://ns.editeur.org/onix’, say? It’s only an example, of course, not normative.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3. For a foreign part, is it necessary to make sure there is an appropriate entry in [Content-Types].xml? If so, that probably needs to be said.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>4. I have to admit to always having been a bit confused by Part 1, 15.2.5 Custom XML Data Storage Part and whether that is also a way to get “foreign” data into an OOXML document. Is that construct worth a mention in this Best Practices TR?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>5. This one is for Rex: I was surprised to see “First, we need to add the file to the OPC package:”. The use of “we” seemed odd.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Have a good weekend.<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/">http://www.digitalpreservation.gov/formats/</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>