<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'>If you remember, I experimented with adding foreign OPC parts to hold ONIX metadata. Recent versions of MS Office don’t appear to throw away such foreign parts, but the version of LIbreOffice that I tested does appear to throw them away.<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'>Nevertheless, I think we should explore the idea of using a foreign OPC part for character repertoire checking data, as this avoids the need to embed such data in content. I prefer this approach to the use of application-defined extension elements or ignorable elements. As you say, so far as implementations of the existing standard are concerned, new application-defined extension elements would have to be in ignorable namespaces, otherwise the implementations would be broken.<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'>Regards,<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'>Francis<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'><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> 13 December 2014 08:32<br><b>To:</b> SC34<br><b>Subject:</b> 30114-2: ignorables, app-defined ext elems, or custom OPC parts<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Summary: Avoid ignorable elements but use application-defined<o:p></o:p></p></div><div><p class=MsoNormal>extension elements or additional OPC parts instead.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I have thought that we should use ignorable elements for representing<o:p></o:p></p></div><div><p class=MsoNormal>data for character repertoire checking. The first CD does use them.<o:p></o:p></p></div><div><p class=MsoNormal>This approach is easy to standardize and implement, but existing<o:p></o:p></p></div><div><p class=MsoNormal>implementations will surely throw away data for character repertoire<o:p></o:p></p></div><div><p class=MsoNormal>checking. I have stupidly thought that this is OK. But no users are<o:p></o:p></p></div><div><p class=MsoNormal>willing to use what is thrown away by existing MS Office and Libre<o:p></o:p></p></div><div><p class=MsoNormal>Office.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The use of application-defined extension elements ensures that data<o:p></o:p></p></div><div><p class=MsoNormal>for character repertoire checking is preserved. But locations of<o:p></o:p></p></div><div><p class=MsoNormal>application-defined extension elements are already set in stone, and<o:p></o:p></p></div><div><p class=MsoNormal>cannot be changed without making existing implementations<o:p></o:p></p></div><div><p class=MsoNormal>non-conformant.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Another option is to use additional OPC parts. If implementations do<o:p></o:p></p></div><div><p class=MsoNormal>not throw away targets of valid relationships, data for character<o:p></o:p></p></div><div><p class=MsoNormal>repertoire checking is preserved.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I can imagine that the use of additional OPC parts has its own<o:p></o:p></p></div><div><p class=MsoNormal>problems. But we should try seriously.<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><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>