[MPEG-OTSPEC] Introducing breaking changes into the spec (was: RE: [EXTERNAL] Proposal to deprecate derived search values)

[Roderick Sheeter]

FWIW I interpret the responses as more of a nudge to do our due
diligence than "stop stop stop."

On Wed, Sep 16, 2020 at 9:03 AM Levantovsky, Vladimir <
Vladimir.Levantovsky at monotype.com> wrote:

> Dear Dave,
>
> I will try to keep this one short. J
>
>
>
> On Tuesday, September 15, 2020 11:31 PM Dave Crossland wrote:
>
> Dear Vlad,
>
>
>
> Another long one from me I'm afraid. Adam, don't get jealous 😂
>
> On Tue, Sep 15, 2020, 1:15 PM Levantovsky, Vladimir <
> Vladimir.Levantovsky at monotype.com> wrote:
>
> We just have to remember if we want other people to implement we need to
> do our due diligence at some point and get the spec updated.
>
>
>
> We also need to be realistic of the potential challenges with new
> technology adoption _*from the end-user point of view*_. Today’s reality
> is that the current implementations are widespread,
>
>
>
> Err, I'm not sure about that, it's not the reality I am living in :)
>
>
>
> In my reality, support for CFF2 or SVG in OT is not widespread, nor CBDT.
> COLR is getting there.
>
> <snip>
>
> Even focusing on the most widely implemented parts of MOFF, uneven
> implementation reigns in my reality:
>
> <snip>
>
>
>
> I tried to make an emphasis on end-user point of view. Yes, the existing
> implementations are never perfect and not complete, there is always
> something to be desired … but that’s not the point. I see success when a
> user can simply select any font they want, declare it as one to be used to
> render text on their website, and then actually see the text rendered
> exactly as desired – on any device, in any browser. The running counter of
> font views on Google Fonts analytics page
> <https://fonts.google.com/analytics> is a testament to this success,
> because the number is mind-boggling!
>
>
>
> Now look, I don't mean to diminish the achievements of the last 5, 10, 25
> years. But I also think it's equally important to be clear about the
> current shortcomings, and to metabolise the energy in the AHG for
> multi-track improvements through clearly written down protocols of change
> management.
>
>
>
> The change is here and it needs to be managed.
>
>
>
> I think we are both in violent agreement on the perception of the events
> of the last 20 years and on what is happening now. I am experiencing a pure
> joy thinking about how this group and the community at large was able to
> achieve something that literally changed the world of CE devices and the
> web.
>
> <snip>
>
>
>
> If an incremental update can offer a smooth transition path, such as
> specifying that when a font engine's client is seeking an old value, it can
> compute that value from the deduplicated new format and return it, that's
> desirable. Terence Dowling posted last week some kind of koans for this
> kind of thing.
>
>
>
> Suggestions to the AHG to consider that kind of thing will, I expect, be
> very fruitful.
>
>
>
> But saying stuff that rhymes with "slow down kids, be REALISTIC, stop stop
> stop, no no no," is, I think, going to rub people the wrong way, and risks
> the opposite of what is intended.
>
>
>
> This is not what I said! If we were a team getting ready for a debate –
> wouldn’t you want to brainstorm all possible questions all get all the
> answers and arguments ready, before the debate starts? Would you want to _
> *know*_ the questions you may be asked (I do not imply cheating) and get
> our story so compelling that it tells everybody “trust us, we know what we
> are doing”?
>
>
>
> This is what I was talking about – making our business case where all ‘i’s
> are dotted and ‘t’s are crossed, and an attempt to foresee any and all
> possible questions, and present our solutions making the arguments for our
> case so compelling! We don’t get there if we cut corners hoping that
> questions won’t be asked, or shortcomings won’t be noticed.
>
>
>
> Vlad
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200916/2e01cbb8/attachment.html>