<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#1E66AE;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#1E66AE;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.cat
{mso-style-name:cat;}
span.ct
{mso-style-name:ct;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.attach, li.attach, div.attach
{mso-style-name:attach;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:9.0pt;
font-family:"Arial","sans-serif";}
p.bold, li.bold, div.bold
{mso-style-name:bold;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial","sans-serif";
font-weight:bold;}
p.green, li.green, div.green
{mso-style-name:green;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#628C2A;}
p.replbq, li.replbq, div.replbq
{mso-style-name:replbq;
margin:3.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad, li.ad, div.ad
{mso-style-name:ad;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.underline, li.underline, div.underline
{mso-style-name:underline;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.yshortcuts
{mso-style-name:yshortcuts;}
p.ad1, li.ad1, div.ad1
{mso-style-name:ad1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad2, li.ad2, div.ad2
{mso-style-name:ad2;
mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:7.5pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.underline1, li.underline1, div.underline1
{mso-style-name:underline1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
text-decoration:underline;}
span.yshortcuts1
{mso-style-name:yshortcuts1;
font-family:"Verdana","sans-serif";
font-weight:bold;}
span.yshortcuts2
{mso-style-name:yshortcuts2;
font-family:"Verdana","sans-serif";
font-weight:normal;}
span.EmailStyle36
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1063678531;
mso-list-template-ids:-1836432982;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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 bgcolor=white lang=EN-US link="#1E66AE" vlink="#1E66AE">
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I would like to say that I completely agree with Leonardo. In
addition, I also would like to remind us all that we agreed to defer the
discussion of “mandatory/optional” features until after we have the
draft specification ready, and after we can evaluate the actual impact of each
proposed tag / attribute on a decoder implementation complexity.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think that in light of our prior discussions and the agreement
we’ve reached it would be reasonable to simply drop the notion of
optional components from consideration in the current draft.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thank you,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Vladimir<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
mpeg-OTspec@yahoogroups.com [mailto:mpeg-OTspec@yahoogroups.com] <b>On Behalf
Of </b>Leonardo Chiariglione<br>
<b>Sent:</b> Tuesday, December 15, 2009 5:08 PM<br>
<b>To:</b> 'Ken Lunde'<br>
<b>Cc:</b> mpeg-OTspec@yahoogroups.com<br>
<b>Subject:</b> RE: [mpeg-OTspec] New "Composite Font Standard"
document<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<div id=ygrp-mlmsg>
<div id=ygrp-msg>
<div id=ygrp-text>
<p style='margin-bottom:12.0pt'>Ken,<br>
To me the document is fine the way it is, save for the "optional"
part.<br>
The text <br>
<br>
NOTES: Although not yet reflected in this document, the notion of
"optional"<br>
refers to an attribute whose inclusion is deemed to be optional according to<br>
this specification. Likewise, some attributes are required. A future version<br>
of this document will make the "optional" versus "required"
distinction<br>
clear, for both tags and their attributes.<br>
<br>
As a matter of philosophy I object to the use of the term "optional"
in a<br>
standard, because the purpose of a standard is to tell users what they<br>
should do to achieve interoperability.<br>
Of course I know that not everybody may have the same notion or requirement<br>
of interoperability. As you may remember from an earlier post, since its<br>
early days MPEG has struggled with this reality and has come up with the<br>
"profile and level" approach. <br>
Instead of having a placeholder for "optional" with the intention to
give it<br>
a meaning later, I would like to give a meaning to "optional" and
then find<br>
a place for it.<br>
As I said interoperability requirements are not the same for all, so there<br>
is nothing new for MPEG in your request, but I would like to get a<br>
formalisation of the thing before admitting it in<br>
Leonardo <br>
<br>
-----Original Message-----<br>
From: Ken Lunde [mailto:<a href="mailto:lunde%40adobe.com">lunde@adobe.com</a>]
<br>
Sent: 15 December 2009 19:41<br>
To: <a href="mailto:leonardo%40chiariglione.org">leonardo@chiariglione.org</a><br>
Cc: <a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a><br>
Subject: Re: [mpeg-OTspec] New "Composite Font Standard" document<br>
<br>
Leonardo and others,<br>
<br>
I spent a significant part of my morning continuing the editing and refining<br>
of this document, and have issued a 2009/12/15 version. See:<br>
<br>
<a
href="http://groups.yahoo.com/group/mpeg-OTspec/files/CompositeFontStandard-200912">http://groups.yahoo.com/group/mpeg-OTspec/files/CompositeFontStandard-200912</a><br>
15_kl.doc<br>
<br>
I also hosted the same file on my website, along with a PDF version:<br>
<br>
<a href="http://lundestudio.com/PDF/CompositeFontStandard-20091215_kl.doc">http://lundestudio.com/PDF/CompositeFontStandard-20091215_kl.doc</a><br>
<a href="http://lundestudio.com/PDF/CompositeFontStandard-20091215_kl.pdf">http://lundestudio.com/PDF/CompositeFontStandard-20091215_kl.pdf</a><br>
<br>
Regards...<br>
<br>
-- Ken<br>
<br>
On 2009/12/15, at 4:12, Leonardo Chiariglione wrote:<br>
<br>
> Ken,<br>
> Excellent.<br>
> I have done the following<br>
> 1. Converted your pdf file to a doc file (MS word is the format<br>
adopted by MPEG because it allows reuse of text, a basic feature in a<br>
collaborative environment like this)<br>
> 2. Edited the file in track change mode<br>
> 3. Changed the file name by using yyyymmdd_lc<br>
> 4. Attached the file to this email<br>
> You may think that some changes are not essential and there may be<br>
elements of truth in this. However, if you agree to the changes we get<br>
agreement on issues that I believe are of substance.<br>
> I will try and explain my point<br>
> 1. The title of the first section has been changed to "Design<br>
features". OS independence is a consequence of the fact that CFS is an<br>
information representation standard, so it has been taken out of the<br>
bulleted list<br>
> 2. At the abstract level there are 4 actors: creator, encoder,<br>
decoder, consumer. Don't let's talk about the names, yet. If you don't like<br>
the names I am fine with calling the actors A,B, C and D, Creator and<br>
consumer are humans (maybe there are more general cases when they are not,<br>
but let's stick to humans for the moment).<br>
> 3. Creator has intentions that he captures in his encoder - an<br>
application<br>
> 4. Consumer has intentions that he expresses by setting his decoder<br>
> 5. The standard only addresses the decoder. The document is silent on<br>
exactly "what" of the decoder is specified. I guess that the
interface<br>
through which the consumer sets the decoder is not part of the standard, but<br>
then it would be good to say this explicitly (note that all this is work<br>
saved for the moment in which the standard will be written)<br>
> 6. In MPEG we use the name conformance, but you can read it as<br>
compliance<br>
> Please feel free to react on anything I did.<br>
> For me this is a very pleasant experience.<br>
> Leonardo<br>
> <br>
> From: <a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>
[mailto:<a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>]
On<br>
Behalf Of Ken Lunde<br>
> Sent: 14 December 2009 19:07<br>
> To: <a href="mailto:mpeg-OTspec%40yahoogroups.com">mpeg-OTspec@yahoogroups.com</a><br>
> Subject: [mpeg-OTspec] New "Composite Font Standard" document<br>
> <br>
> <br>
> All,<br>
> <br>
> In an effort to move this along, I spent the morning incorporated<br>
Leonardo's comments and suggestions, and produced a new version of the<br>
document. You should have received a "new document notification"
email with<br>
the following URL:<br>
> <br>
><br>
<a
href="http://groups.yahoo.com/group/mpeg-OTspec/files/CompositeFontStandard-121420">http://groups.yahoo.com/group/mpeg-OTspec/files/CompositeFontStandard-121420</a><br>
09.pdf<br>
> <br>
> I also hosted the same file on my website:<br>
> <br>
> <a href="http://lundestudio.com/PDF/CompositeFontStandard-12142009.pdf">http://lundestudio.com/PDF/CompositeFontStandard-12142009.pdf</a><br>
> <br>
> When you have a chance, please read this document and provide feedback.<br>
> <br>
> Regards...<br>
> <br>
> -- Ken<br>
> <br>
> <br>
> No virus found in this incoming message.<br>
> Checked by AVG - www.avg.com<br>
> Version: 8.5.427 / Virus Database: 270.14.106/2563 - Release Date:<br>
12/13/09 19:47:00<br>
> <br>
> <CompositeFontStandard-20091214_lc.doc><br>
<br>
No virus found in this incoming message.<br>
Checked by AVG - www.avg.com <br>
Version: 8.5.427 / Virus Database: 270.14.106/2563 - Release Date: 12/15/09<br>
07:52:00<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:white'><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>