FW: Transition request: updated CR for CSS Values and Units

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

FW: Transition request: updated CR for CSS Values and Units

nigelmegitt
FYI CSS values and units CR transition request:

On 01/08/2016 21:42, "Chris Lilley" <[hidden email]> wrote:

>Hello Ralph,
>
>This is a Transition request for an updated CR for CSS Values and Units.
>The previous CR was published on  11 June 2015
>https://www.w3.org/TR/2015/CR-css-values-3-20150611/
>
>* Document title, URIs, and estimated publication date
>
>CSS Values and Units Module, Level 3
>   https://drafts.csswg.org/css-values-3/
>   Next Tuesday or Thursday after a successful transition meeting
>
>* The document Abstract and Status sections
>   https://drafts.csswg.org/css-values-3/#abstract
>   https://drafts.csswg.org/css-values-3/#status (as ED; will have same
>CR exit criteria as other CSS WG specifications)
>
>* Decision to request transition
>   RESOLVED: Start a level 4 draft of Values & Units, move calc()
>               serialization to it, and then publish the remainder of
>               Values & Units 3 as CR.
>   https://lists.w3.org/Archives/Public/www-style/2016Jul/0051.html
>
>* Changes (since 11 June CR)
>   https://drafts.csswg.org/css-values-3/#changes
>One feature is at-risk; the attr() function, as notes in the Status
>section.
>
>* Requirements satisfied
>   (No requirements document; CSS has had property values and used units
>since CSS1)
>
>* Dependencies met (or not)
>Looking at the normative references:
>https://drafts.csswg.org/css-values-3/#normative
>
>This module collects together any new units of measurement and new
>syntactic constructs used for property values by other CSS modules. This
>is done to allow these syntactic constructions to be shared between
>modules. However, the normative definition of the semantics remains the
>actual module which first defined them. Thus, there are many normative
>references to other modules, which may be at earlier maturity levels. It
>is understood that Values and Units Level 3 will therefore not move to
>Recommendation until the normative dependencies are all more mature. A
>level 4 of Values and Units has been started.
>
>There is an IANA considerations appendix, which describes the
>about:invalid url scheme.
>https://drafts.csswg.org/css-values-3/#about-invalid
>This has been registered with IANA, in 2012
>http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xhtml
>
>* Wide review
>
>27 comments were received since publication of the previous CR.
>
>There is a Security and Privacy appendix:
>https://drafts.csswg.org/css-values-3/#sec-pri
>
>* Issues addressed
>
>The disposition of comments for the most recent wide review (for changes
>since the previous CR) is at:
>   https://drafts.csswg.org/css-values-3/issues-cr-2015
>
>* Formal objections
>There were no formal objections
>
>* Implementation
>Implementation of parsing and of serialization can be tested. The
>formatting semantics of individual properties are out of scope for this
>module. The test suite has 103 tests, results are at:
>   https://test.csswg.org/harness/results/css-values-3_dev/grouped/
>73/103 tests currently met CR exit criteria.
>
>* Patent disclosures
>None, see
>   https://www.w3.org/2004/01/pp-impl/32061/status
>
>--
>Chris Lilley
>@svgeesus
>Technical Director, W3C Interaction Domain
>
>



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------