@@ This is a proposed charter! @@
The mission of the Cascading Style Sheets (CSS) Working Group, part of the Style Activity, is to develop and maintain CSS.
End date | 15 June 2016 |
---|---|
Confidentiality | Proceedings are public |
Initial Chairs | Daniel Glazman, Peter Linss |
Initial Team Contacts (FTE %: 71) | Bert Bos, Chris Lilley |
Usual Meeting Schedule | Teleconferences: Weekly Face-to-face: 3-4 per year |
The CSS WG develops the following, somewhat independent technologies:
An example of a language that uses only the syntax is STTS (developed by Disruptive Innovations). An example that uses the syntax, the cascading & inheritance, but not the layout model is the set of properties for styling SVG. CSS levels 1, 2 and 3 include the syntax, cascading & inheritance and rendering model.
CSS is a rather large and complex language. CSS beyond Level 2 is being developed as a set of modules each of which may advance on the W3C Recommendation Track independently. Among them are modules for syntax, cascading and inheritance, and, of course, many aspects of typography, page layout and presentation.
As individual CSS modules advance to REC, the Group periodically publishes a new snapshot of CSS. Each defines the set of CSS modules that are stable at that point.
Profiles are subsets of the features of CSS, usually for a specific kind of device. The CSS WG has published profiles for TV, mobile phones and low-end printers. The number of such profiles should stay as small as possible, but when needed, the working group tries to cooperate with the organizations that need the profiles.
The CSS WG not only develops CSS, but also checks that properties needed by other working groups and which could occur in a style sheet together with CSS properties, are compatible with CSS in general and consistent in their naming schemes. This affects properties such as those of SVG and Device Independence (such as media features), but not properties such as those in STTS nor the presentation attributes of XSL, SVG or DFXP.
Part of the work of the working group is also to develop test suites for the various specifications it publishes.
Another part is to maintain errata and, when needed, publish revised versions of the various specifications.
The CSS Working Group's work is considered a success if there are multiple independent complete and interoperable implementations of its deliverables that are widely used.
The following is a list of specifications that the WG has worked on in the past and is likely to work on again in this charter period, depending on demand and available resources. This list is not exclusive: The WG may also create new specifications, within its scope. Also, it may split or merge documents.
W3C staff maintains a public list of CSS-related documents and recent changes. Please, see that list for the current activities of the WG.
Documents under active development; one or more active editors, regular publication, test suites in development. Expected to progress on the Recommendation track during the charter period.
Documents under development as resources permit.
Errata mode.
Documents without active editor, or blocked on outstanding and unresolvable problems, or no developer interest.
The Group creates a comprehensive test suite for each CSS module before it becomes Recommendation.
The group will creata an automatic, up-to-date, index of all properties, with each property linked to the part(s) of the specification(s) that define(s) it.
The Group monitors, tracks, and encourages implementation of CSS, both during Candidate Recommendation and afterwards.
The WG will give priority to specifications that are dependencies of other specifications under development in W3C, such as HTML5 and SVG.
Specification transition estimates (for selected high-priority specifications only):
Note: The group will document significant changes from this initial schedule on the CSS roadmap page. | ||||||
Specification | FPWD | LC | CR | PR | Rec | |
---|---|---|---|---|---|---|
CSS Image Values and Replaced Content Module Level 3 | n/a | n/a | n/a | Nov 2014 | Dec 2014 | |
CSS Values and Units Module Level 3 | n/a | n/a | n/a | Nov 2014 | Dec 2014 | |
CSS Cascading and Inheritance Level 3 | n/a | n/a | n/a | Nov 2014 | Dec 2014 | |
CSS Basic User Interface Module Level 3 | n/a | Jul 2014 | Aug 2014 | Mar 2015 | Apr 2015 | |
CSS Object Model (CSSOM) | n/a | Nov 2014 | Jan 2015 | Aug 2015 | Sep 2015 | |
CSSOM View Module | n/a | Nov 2014 | Jan 2015 | Aug 2015 | Sep 2015 | |
Cascading Style Sheets Level 2 revision 2[PER] | n/a | n/a | n/a | May 2014 | Jun 2014 | |
CSS Animations | n/a | Jun 2014 | Jul 2014 | Mar 2015 | Apr 2015 | |
CSS Transitions | n/a | Jun 2014 | Jul 2014 | Mar 2015 | Apr 2015 | |
CSS Transforms Module Level 1 | n/a | Jun 2014 | Jul 2014 | Mar 2015 | Apr 2015 | |
Filter Effects Module Level 1 | n/a | Nov 2014 | Dec 2014 | Jul 2015 | Aug 2015 | |
CSS Masking Module Level 1 | n/a | n/a | May 2014 | Jan 2015 | Feb 2015 | |
Compositing and Blending Level 1 | n/a | n/a | May 2014 | Jan 2015 | Feb 2015 |
Furthermore, Cascading Style Sheets (CSS) Working Group expects to follow these W3C Recommendations:
To be successful, the group is expected to have 10 or more active participants for its duration. Effective participation is expected to consume one work day per week for each participant; two days per week for editors. The group allocates also the necessary resources for building Test Suites.
Participants are reminded of the Good Standing requirements of the W3C Process.
The Group holds weekly teleconferences, and primarily conducts its work on the public mailing list www-style@w3.org (archive) for technical discussions. A member-only mailing list w3c-css-wg@w3.org (archive) is also available for member-only communications
The list of current members of the CSS WG is public.
Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the CSS Working Group page and the CSS Working Group wiki.
As explained in the Process Document (section 3.3), this group seeks to make decisions when there is consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.
Decisions are made by consensus of the Working Group. In addition to decisions made on teleconferences or face to face meetings, decisions may also be made by a call for consensus on the public mailing list; consensus to be determined by the chairs after some reasonable interval for objections.
When the Chair conducts a formal vote to reach a decision on a substantive technical issue, eligible voters may vote on a proposal one of three ways: for a proposal, against a proposal, or abstain. For the proposal to pass there must be more votes for the proposal than against. In case of a tie, the Chair decides the outcome of the proposal. The Chair must only conduct a formal vote during a group meeting, and at least two-thirds of participants in Good Standing must be in attendance.
This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This charter for the Cascading Style Sheets (CSS) Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
The primary changes since the previous charter are:
Copyright© 2014 W3C ® (MIT, ERCIM, Keio, Beihang), All Rights Reserved.
$Date: 2014/04/30 20:49:10 $