<div dir="ltr">It would be helpful to start by understanding what changes people want to make and why. One possible approach would be to simply ask people to post their thoughts and share links back to the group (perhaps CG mailing list?), inspired by the Rust call for blogs (<a href="https://blog.rust-lang.org/2019/10/29/A-call-for-blogs-2020.html">https://blog.rust-lang.org/2019/10/29/A-call-for-blogs-2020.html</a>). </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Sep 13, 2020 at 10:02 AM Peter Constable <<a href="mailto:pgcon6@msn.com">pgcon6@msn.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-4249126922232139029WordSection1">
<p class="MsoNormal">> <span lang="EN-CA">I really hope we’re not going to try to define some entirely new font format by email.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-CA"><u></u> <u></u></span></p>
<p class="MsoNormal">Someone mentioned offline that my brief message, saying what I don’t want but not what I would want to see happen, might come across as trying to shut down discussion and block progress. I think that’s valid feedback, and so want to correct
that with a brief elaboration.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Clearly, my statement indicates a desire to shut down discussion—_<i>in this current mode and context</i>_.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">For one thing, I thought there had been general consensus that a topic like creating an entirely new format would be pending a discussion elsewhere (the TFCG) on what new areas of activity should be discussed and what the appropriate context(s)
for those should be. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Secondly, discussion was bringing up specific design details (dropping CFF, what OS/2 metrics are needed, how formats for graphic elements should be architected), which is putting the cart waaaaayyyy ahead of the horse: As Adam and Vlad
suggested, this topic needs to start with a cost-benefit analysis. I’d expand that a bit: any work to start in this direction would need a carefully thought-out business case _<i>and</i>_ strategic roadmap that can convince a broad range of vendors, including
most or all the majors, that there will be beneficial ROI and a feasible path to success that takes current realities into consideration. (Do I sound like a PM?) Engineering is first of all a matter of addressing real public or business problems or opportunities.
Without that, technical design is nothing more than a science project.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">And until vendors have bought into a business case and strategic roadmap, talk of a _<i>hugely</i>_ disruptive change (which is what is being discussed) is counter-productive: at best, a noisy distraction; and at worst, perceived as intended
to create discord and new font wars.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I’m all for designing a new and better mousetrap, and I’d be in favour of discussions that explore business case and possible paths to success. But I don’t think this email thread is net helping move toward that. Let’s progress one step
at a time, as generally agreed, in the TFCG.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Peter<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Peter Constable <br>
<b>Sent:</b> Friday, September 11, 2020 3:57 PM<br>
<b>To:</b> mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>><br>
<b>Subject:</b> RE: [MPEG-OTSPEC] Introducing breaking changes into the spec (was: RE: [EXTERNAL] Proposal to deprecate derived search values)<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-CA">I really hope we’re not going to try to define some entirely new font format by email.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-CA"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-CA"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-CA">Peter<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
mpeg-otspec mailing list<br>
<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
<a href="https://lists.aau.at/mailman/listinfo/mpeg-otspec" rel="noreferrer" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
</blockquote></div>