[MPEG-OTSPEC] [EXTERNAL] Re: Request for OFF Github Repo

[David Singer]

I think it might help to take the Table of Contents, and explain a vision of the new way a spec. should flow, and what a re-structured document’s ToC might look like. That’s not toooo much work, and if it appears fruitful and gaining consensus, we can work out how to get to the next level.

> On 18Sep, 2020, at 9:22 , Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com> wrote:
> 
> Simon Cozens wrote:
>> How would you like these proposals to be formatted and delivered? It sounds like (from other messages) you would like this mailing list to be the official arena for the development of consensus. Would it be appropriate to raise proposals as issues in Github containing the new text, and then send an email to the list?
> 
> This can definitely be a way to do things going forward.
> Vlad
> 
> -----Original Message-----
> From: Simon Cozens <simon at simon-cozens.org> 
> Sent: Friday, September 18, 2020 12:19 PM
> To: Levantovsky, Vladimir <Vladimir.Levantovsky at monotype.com>; Adam Twardoch (Lists) <list.adam at twardoch.com>; Dave Crossland <dcrossland at google.com>
> Cc: mpeg-otspec <mpeg-otspec at lists.aau.at>
> Subject: Re: [MPEG-OTSPEC] [EXTERNAL] Re: Request for OFF Github Repo
> 
> On 18/09/2020 17:00, Levantovsky, Vladimir wrote:
>> Here is what I am hearing and this is something we need to think about 
>> ahead of time. You are essentially contemplating [and proposing] that 
>> there is a need for two new work items – a major structural and 
>> editorial rewrite of the existing OFF spec, and a completely new 
>> document that will be created based on this updated OFF text. The 
>> former doesn’t introduce major technical changes, and the latter will. 
>> The way to accomplish this, in my opinion, is to develop new edition 
>> of the OFF, and consider OFF2 an entirely new ISO standard, with its own part number.
> 
> I completely agree with this summary of the needs and the way forward!
> 
>> For that, we would benefit from having the current source 
>> representation in a format which is useful for collaborative editing.
> 
> This would be ideal, yes. How do we get there? Will ISO be able to release the current version in such a format, or do I have to point Peter to the git-filter-branch man page again? :-)
> 
>> So, as a group – we have a clean and known starting point – every 
>> single participant can view the documents and develop their own 
>> proposals based on them – proposed new structure, proposed new text 
>> for each clause/subclause that would benefit from editorial rewrite, etc.
> 
> How would you like these proposals to be formatted and delivered? It sounds like (from other messages) you would like this mailing list to be the official arena for the development of consensus. Would it be appropriate to raise proposals as issues in Github containing the new text, and then send an email to the list?
> 
> S
> 
> _______________________________________________
> mpeg-otspec mailing list
> mpeg-otspec at lists.aau.at
> https://lists.aau.at/mailman/listinfo/mpeg-otspec

Dave Singer
Multimedia and Software Standards, Apple

singer at apple.com