- From: Glenn Adams <glenn@skynav.com>
- Date: Fri, 19 Jun 2015 07:00:17 -0600
- To: Thierry MICHEL <tmichel@w3.org>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Philip Jägenstedt <philipj@opera.com>, David Singer <singer@apple.com>, W3C Public TTWG <public-tt@w3.org>
- Message-ID: <CACQ=j+ft1Q_jCjw28D-UnMr_z5mrhSoJj-heKpp3yTaCj67MLA@mail.gmail.com>
On Fri, Jun 19, 2015 at 6:47 AM, Thierry MICHEL <tmichel@w3.org> wrote: > > > On 19/06/2015 11:44, Silvia Pfeiffer wrote: > >> I'm in favour of using this approach, but I'm going to have to let >> Philip speak, too, since he has automated the publishing approach for >> the WebVTT spec. >> > > Sure. > >> >> WebVTT is written in respec, so it will be ready to adapt. >> > > good news. should be easy to provide a TR ready WD then. > >> >> David, I believe you will have to ask the TTWG for approval to take this >> approach next. The rest should be simple. >> > > Yes that is the way to go. > Needs discussion about using a single TTWG approuval for all future WD > publications or a TTWG approuval for each future WD publication. > I do not expect agreement on a blanket use of the new tool for *all* future WDs, e.g., TTML is authored in XML using the xmlspec DTD. This is unlikely to change. > > Best, > Thierry > > > >> Best Regards, >> Silvia. >> >> On 19 Jun 2015 6:02 pm, "Thierry MICHEL" <tmichel@w3.org >> >> <mailto:tmichel@w3.org>> wrote: >> >> WebVTT editors and TTWG collegues, >> >> The W3C has recently provided a new tool for publishing Working >> Drafts in TR space. This tool (Echidna) provides easy publication >> without the need of the Webmaster (or Team contact) for the editor. >> >> WebVTT FPWD last publication was done on Nov 13th 2014. We probably >> need to republish on TR soon. >> >> My proposal is to try this new tool for the publication of WebVTT >> WD. This new publication system is a beta. >> >> If this tool should ease the publication process, allowing >> publication by the editor (or Team contact). It requires 4 actions: >> >> 1-Approuval of publication with Echidna by the WG. >> In order for the editor to publish documents using the new process, >> the TTWG needs to get consensus to do so. The chair will generally >> put out a Call for Consensus (CFC). >> >> - Approuval once by the TTWG for any iteration of WebVTT WD >> publications. >> This would facilitate publication by the editor without waitting for >> a TTWG approuval for each publication. On the other hand the TTWG >> may be less informed of the changes made into the document, before >> publication in TR, without an approuval for each publication). Maybe >> a section "changes log" in WebVTT spec would help. >> >> - other solution is Approuval by the TTWG for each Publication of >> WebVTT WD publication. >> This would delay a bit the WD publication in TR, requiring the >> editor to wait for TTWG approuval for each publication. But it would >> aallow the TTWG to better monitor the WebVTT publication in TR. >> >> >> 2- Require a token for the spec >> The first time only, the team contact has to request a token for the >> spec. Team contact communicates token for spec to editor, who keeps >> it safe >> >> Request of token needs to parameter: >> - specification url: the latest version url of the specification, >> e.g. http://www.w3.org/TR/<shortname> >> - source of the specification: for security reasons, a token is also >> associated with a document origin. >> >> >> 3-The Editor IDs >> You will need to get the IDs for the Editors of your spec. You can >> find yours by going to your W3C profile. >> >> 4- Prepare the document >> Unfortunatly the WebVTT editor's draft in the CG and the WebVTT >> Working Draft in the TTWG to be published on TR differ: >> >> - style sheets are different >> - copyrights are different >> - Status of this document present in TR version >> - Dated URI and shortname URIs present in TR version >> -etc. >> >> Therefore before trying to publish with Echidna, one must provide a >> document with the proper above styling and informtion. >> Are the editors using Respec ? In this case an output to specific TR >> formatting could be done to have a proper source document for >> Echidna. >> >> The source document to be publish by Echidna needs to pass the >> validators and purules. >> >> * Check your spec with new Specberus >> https://labs.w3.org/pubrules/ >> >> >> * Publishing using Echidna >> >> Once you have a document, a Group decision, and a token, you can >> submit your document : >> >> Publish using reference UI, developed in-house, >> https://w3.org/publish/ >> >> Provide: >> - Spec URL, eg http://www.w3.org/TR/flux-capacitor >> - Source URL, eg https://w3c.github.io/FluxCapacitorSpec >> >> For more information for publishing with Echidna >> >> https://labs.w3.org/echidna/ >> https://github.com/w3c/echidna/wiki >> >> We should also use this process for TTML2 WD publications. >> For IMSC1, it isn't possible, Echidna only support WD publications >> (not FPWG, CR, PR and REC). So we will use the regulr publication >> process with the webmaster. >> >> Best, >> >> Thierry. >> >> >> >> >> >
Received on Friday, 19 June 2015 13:01:11 UTC