[MPEG-OTSPEC] Acknowledging sources

[Simon Cozens]

Let’s extend that: all chapters describing tables should start with a table of metadata containing:

* version introduced
* version deprecated
* version to be removed in
* originating person or entity
* requirement status

Simon

> On 15 Aug 2020, at 09:35, Behdad Esfahbod <behdad at behdad.org> wrote:
> 
> 
>> On Sat, Aug 15, 2020 at 1:05 AM Simon Cozens <simon at simon-cozens.org> wrote:
> 
>> On 14/08/2020 23:16, Behdad Esfahbod wrote:
>> > - You on behalf of MS demanded that LSB/RSB variations (and by extension 
>> > TSB/BSB variations) be encoded in the HVAR/VVAR tables because the 
>> > obsolete GDI "ABC" API "needs them" and can't be bothered to get them 
>> > from the outlines.
>> 
>> One thing which would at least mitigate some of these problems would for 
>> the spec to be honest about how ideas were originated and included. The 
>> features registry at least does this, so there's precedent.
>> 
>> In a truly community-owned spec this would be unnecessary, as there 
>> would be an expectation that it was the consensus of multiple 
>> contributors. But for a spec which is maintained by one corporate 
>> entity, which claims ownership over the spec, to include contributions 
>> from others without acknowledging the source of those contributions is 
>> dishonest and disingenuous.
>> 
>> Those of us with long memories of "embrace and extend" have some 
>> sensitivity for how MS has taken the ideas of others and berated them 
>> publicly before implementing them and claiming them as its own - this 
>> destroys trust and dissuades future contributions.
> 
> More importantly to the final product: mark junk like `post` table as "required on Microsoft platforms" instead of "required".
>  
>> S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200815/b38a4335/attachment.html>