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

[Levantovsky, Vladimir]

I did NOT say they can’t happen here, but this is exactly the kind of decision that cannot be taken lightly, and it is definitely not a joke!

New specs can be written easily, but it’s the wide adoption [not the spec itself] that we should care about the most because, in the end, it is what benefits users. You seem to care a lot about consensus decisions, and this is exactly why consensus decisions are so important.

From: Dave Crossland <dcrossland at google.com>
Sent: Friday, September 11, 2020 4:04 PM
To: Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com>
Cc: Renzhi Li <Renzhi.Li at microsoft.com>; mpeg-otspec <mpeg-otspec at lists.aau.at>
Subject: Re: Introducing breaking changes into the spec (was: RE: [MPEG-OTSPEC] [EXTERNAL] Proposal to deprecate derived search values)



On Fri, Sep 11, 2020 at 4:01 PM Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com<mailto:Vladimir.Levantovsky at monotype.com>> wrote:
With my chair hat on, I’d like to point out that comments made in passing about 1.X vs. 2.0 aren’t helpful.

They are going to happen, and if they aren't welcome at all here, I expect that the new format will be developed elsewhere. Is that what you want? :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200911/a9235b1d/attachment.html>