Re: [css-2015] Snapshot prose, prefixing policy updated

On Tue, Jul 21, 2015 at 4:26 PM, Sebastian Zartner
<sebastianzartner@gmail.com> wrote:
> On 20 July 2015 at 23:06, fantasai <fantasai.lists@inkedblade.net> wrote:
>> Hi everyone,
>> Tab and I just finished compiling a first draft of the 2015 Snapshot copy.
>> We haven't incorporated the new specs into the indexes (it's still the
>> 2010 set), but we updated the intro, the process summary, and most
>> importantly
>>
>>   We updated the prefixing policy to reflect the San Diego 2012 resolutions:
>>     http://www.w3.org/blog/CSS/2012/08/30/resolutions-53/
>>
>> Many thanks to Florian Rivoal for the initial draft of the new policy.
>>
>> Here's a link to the Editor's Draft:
>>   http://drafts.csswg.org/css-2015/#experimental
>>
>> We're hereby requesting that the CSSWG review and, if the wording is an
>> acceptable representation of the resolutions, approve the new policy.
>
> Editorial nits:
> - Link to 'This version' is broken.

It won't be, once the spec is actually up on /TR.  (And messing with
how Bikeshed generates it would be annoying and low-value; NOTE is
considered a "/TR" status, and auto-generates the /TR url that it will
eventually be installed on.)

> - Link to 'CSS Speech Module Level 1' is broken.
> - First sentence in the second note should be "... their inclusion
> does not mean they are frozen.".
> - Semicolon in description for CSS Conditional Rules Level 3 should be
> removed (or replaced by a comma).
> - Description for CSS Image Values and Replaced Content Level 3 should
> be "... syntax for gradients as images in CSS.".

Fixed.

> - Description for CSS Flexible Box Module Level 1 should be more specific.

What do you want to see?  It seems roughly similar to the descriptions
that other modules receive.

> - Point 2 and 3 within 'Implementations of Unstable and Proprietary
> Features' should refer to user agents, not browsers or be web-centric
> (right?)

No, those are web-centric on purpose.  We can verify with the WG that
we want to keep them like this, but they were drafted and intended to
be browser/web specific originally.  Point 2 is very specifically
about the current major browser population; for Point 3, proprietary
devices and networks can do what they want.

~TJ

Received on Wednesday, 22 July 2015 01:33:32 UTC