W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: CfC - publish Selectors API as CR

From: Maciej Stachowiak <mjs@apple.com>
Date: Fri, 27 Nov 2009 20:17:26 -0800
Cc: Charles McCathieNevile <chaals@opera.com>, public-webapps@w3.org
Message-id: <6D7C76CF-7FB1-4CF8-9781-E5159D2CF1CA@apple.com>
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>

On Nov 26, 2009, at 6:05 AM, Lachlan Hunt wrote:

> Maciej Stachowiak wrote:
>>> The proposed exit criteria are in a separate thread, but  
>>> essentially are:
>>>
>>> For a set of tests based on HTML, CSS 2.1 selectors and this spec,
>>> there are two implementations that pass every test interoperably,  
>>> and
>>> do not fail any "additional" tests based on misimplementing this
>>> specification (i.e. failures based on not supporting a technology  
>>> used
>>> only in the additional tests, such as MathML, will not be taken into
>>> account).
>>
>> Request for clarification. Does this require:
>>
>> A) There must be two implementations, each of which passes every test
>> (i.e. the same two implementations pass all the tests); or
>> B) For each test, there are two implementations that pass it (but not
>> necessarily the same two for every test).
>>
>> It reads like (A), but I have seen similar wording interpreted as  
>> (B) in
>> the context of other specs...
>
> The intention in the original exit criteria proposal [1] was for  
> there to be at least two complete implementations, each passing 100%  
> of the baseline tests.  I can make this clearer in the exit criteria  
> as follows:
>

The wording below seems very clear and unambiguous to me. Thanks.

  - Maciej

> ---
>
> There must be at least two complete, independent implementations,  
> each of which must pass 100% of the baseline testsuite and should  
> pass additional tests, dependent on the following conditions:
>
> * The implementations must be native implementations in shipping
>  products.  (JavaScript library implementations don't count).
>
> * The baseline testsuite comprises tests that check for conformance to
>  all requirements in the API using only HTML and Selectors defined in
>  CSS 2.1.
>
> * Tests using Selectors introduced in Selectors Level 3, or XHTML+SVG,
>  are considered to be additional tests.
>
> * An additional test may be marked as N/A for an implementation if:
>  - The test uses a selector that the implementation does not support
>  - The test uses XHTML+SVG that the implementation does not support
>
> * Implementations are not required to pass all additional tests,
>  however no failures must be caused by an incorrect implementation of
>  the API itself. Failures of additional tests caused only by an
>  incorrect implementation of Selectors do not count.
>
> ---
Received on Saturday, 28 November 2009 04:18:01 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT