W3C home > Mailing lists > Public > public-secondscreen@w3.org > June 2015

Re: Timing of TAG review

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Fri, 26 Jun 2015 11:31:10 +0000
To: Francois Daoust <fd@w3.org>, "mark a. foltz" <mfoltz@google.com>
CC: "public-secondscreen@w3.org" <public-secondscreen@w3.org>
Message-ID: <0FC952CA-69A5-4B89-928D-0F7B61F64067@intel.com>
Hi MarkFo, Francois,

> On 19 Jun 2015, at 14:48, Francois Daoust <fd@w3.org> wrote:
> On 2015-06-18 22:52, mark a. foltz wrote:


>> Francois, can you help ensure the document is "pubrules-compliant"?

I tested that the generated releases/WD.html passes Pubrules Checker as well as Link Checker. The couple of warnings reported can be ignored.

> It is already as pubrules-compliant as possible except for a now broken reference to DOMException which is no longer defined in the DOM standard but got moved to WebIDL. All links to:
> https://dom.spec.whatwg.org/#domexception
> ... should be replaced by links to:
> https://heycam.github.io/webidl/#idl-DOMException


All - you should do a git pull in the xref repo to get the latest changes to the cross-references database. Otherwise the build will fail.

> To run the new pubrules checker on the editor's draft, just go to:
>  https://labs.w3.org/pubrules

The right URL is:


I.e. must include the trailing slash, otherwise you'll get a "Cannot GET /pubrules" error.

Francois - I suggest you inform the folks running the service that they should redirect the former URL to the latter.

> ... and enter the URL to check, selecting "Working Draft" as Profile and "Check that the document is valid for automatic publication with Echidna". The errors reported are all due to the fact that this is an Editor's Draft, and not a Working Draft. The changes I made to the Makefile should produce a working draft that fixes these errors.

Some further changes have been made to the Makefile to make it work on OS X. Hopefully it still works as expected on other OSes, fingers crossed.

> To check links:
> http://validator.w3.org/checklink?uri=http://w3c.github.io/presentation-api/&recursive=on

We pass this too.

> There is no real need to test the generated Working Draft before triggering Echidna. Echidna will run the pubrules checker and refuse to publish the draft if it contains errors in any case. Echidna will report the outcome to the public-tr-notifications mailing-list:
> https://lists.w3.org/Archives/Public/public-tr-notifications/2015Jun/

I noted Pubrules Checker in the instructions in step 8:




>> [1]
>> https://github.com/w3c/presentation-api/issues?q=is%3Aopen+is%3Aissue+label%3ATAG
>> [2] https://github.com/w3c/presentation-api/issues/93
>> [3] https://github.com/w3c/presentation-api/issues/91
Received on Friday, 26 June 2015 11:31:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:56 UTC