Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 123 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 129 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 136 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 170 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 200 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 206 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 231 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 242 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 254 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 293 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 351 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 352 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 353 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 354 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 355 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php on line 571 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_misc.funcs.php on line 197 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_misc.funcs.php on line 202 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_connect_db.inc.php on line 27 Warning: Cannot modify header information - headers already sent by (output started at /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php:123) in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/sessions/_session.class.php on line 222 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/generic/_genericelement.class.php on line 112 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/dataobjects/_dataobject.class.php on line 428 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/dataobjects/_dataobject.class.php on line 437 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/collections/_category.funcs.php on line 390 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_resultsel.class.php on line 549 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_resultsel.class.php on line 563 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist.class.php on line 602 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_item.class.php on line 2952 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_misc/_plugins.class.php(3113) : eval()'d code on line 1 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_blog_main.inc.php on line 306 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist2.class.php on line 120 Deprecated: Assigning the return value of new by reference is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/items/_itemlist2.class.php on line 796 Deprecated: Function ereg() is deprecated in /afs/w3.org/pub/WWW/2005/06/blog/inc/_blog_main.inc.php on line 413 Warning: Cannot modify header information - headers already sent by (output started at /afs/w3.org/pub/WWW/2005/06/blog/inc/_main.inc.php:123) in /afs/w3.org/pub/WWW/2005/06/blog/inc/MODEL/skins/_skin.funcs.php on line 71
The MW4D IG held its 30th teleconference on December 7 2009.
The approved minutes are available at http://www.w3.org/2009/12/07-mw4d-minutes.html
Previous meeting minutes are available from the teleconference archives
Two CSS modules became Candidate Recommendation: CSS Backgrounds and Borders and CSS Multi-column Layout.
It is now time to see if the specifications can be implemented. Large parts of both modules have already been implemented experimentally in various browsers and other software. Over the next six months, the working group plans to develop a test suite and then use the results of testing to decide if the specifications are ready to become W3C Recommendations.
Feedback on the specifications, in particular experience with implementing them, can be sent to the mailing list <www-style@w3.org>. Please, include the short name of the specification between square brackets [] in the subject of any message you send. That is:
[css3-multicol]
or
[css3-background]
Many thanks to all who helped with comments, tests, and implementations! The Selectors specification was just advanced to Proposed Recommendation by the W3C Director. That means that the specification has successfully passed public review and has been sufficiently implemented to no longer need a status as Candidate Recommendation (which is also known as “call for implementations”).
Currently, the W3C members are reviewing the specification one last time. Of course, we think we have done our job well and they won't find anything wrong. They have a little over a month for that task.
However, the specification will not immediately become a W3C Recommendation at the end of the review period. That is because Selectors has normative references in its bibliography to CSS 2.1 and to the CSS Namespaces module, and so it was decided that those have to become Recommendations first. That ensures that W3C Recommendations are as stable as possible, by only depending on other Recommendations.
A bit of history: Selectors became Candidate Recommendation already in 2001, but a couple of proposed features (':contains', '::selection') were never implemented and turned out to be difficult enough that we abandoned them for now. To fix the draft with respect to those problems, a new working draft was made in 2005, which was updated one last time earlier this year.
You can see the last changes we made to the specification in the disposition of comments. Nothing major changed, but a number of descriptions were improved.
The CSS Validator implements the latest Selectors. To check a style sheet, it is enough to choose “CSS level 3” as the profile in the Web interface.
Thanks to the Sorin Velescu, the following articles have been translated into Romanian.
Schimbarea codificarii paginii (X)HTML in UTF-8 (Changing (X)HTML page encoding to UTF-8)
CSS3 si textul international (CSS3 and International Text)
[search keys: qa-changing-encoding article-css3-text]
Thanks to the Spanish Translation Team, Spanish Translation US, the following articles have been translated into Spanish.
Verificación de encabezados HTTP (Checking HTTP Headers)
Configuración de información charset en .htaccess (Setting charset information in .htaccess)
Verificación de la codificación de caracteres mediante el verificador (Checking the character encoding using the validator)
[search keys: qa-headers-charset qa-htaccess-charset qa-validator-charset-check]
The MW4D IG held its 29th teleconference on November 9 2009.
The approved minutes are available at http://www.w3.org/2009/11/09-mw4d-minutes.html
Previous meeting minutes are available from the teleconference archives
We’ve heard from several groups and individuals that they would like W3C to host a public decentralized versioning repository for W3C-related work items, such as editors drafts, test suites, tools and software.
The goal of such a repository would be to host the reference versions of these items, while allowing as many people as possible to modify, branch, patch the content of the repository, without the hurdles that CVS creates for this kind of cooperation.
As we are looking into experimenting with such a service, we are hitting the question that many others have encountered in that process: which decentralized versioning system to choose?
The main two contenders seems to be Git and Mercurial; Git seems to have a growing number of tools, and more advanced features; Mercurial seems to be easier to use, and possibly easier to set up on a larger number of platforms. Here are some of the comparions we have found in our early investigations:
We’re interested to hear feedback on this question, in particular in the form of sharing experience of using them (inside or outside of the W3C community), and pros and cons of both systems.
We’re trying to have that discussion on our publicly archived mailing list public-qa-dev@w3.org (where I sent a message similar to this post), but feel free to use blog comments if you find that more practical.
FAQ-based article: Which language tag is right for me? How do I choose language and other subtags?
Following the publication of RFC 5646 earlier this year (replacing RFC 4646 as part of BCP 47), the IANA Subtag Registry now contains almost 8,000 subtags, and the list of subtag types was increased with the introduction of extended language subtags. This article tries to simplify the choice of an appropriate language tag for your needs by outlining the necessary decisions in a step-wise fashion.
By Richard Ishida, W3C. [search key: qa-choosing-language-tags]
The W3C Evaluation and Repair Tools Working Group (ERT WG) has published new or updated a number of RDF vocabularies that are part of the Evaluation and Report Language (EARL). These working drafts include:
See also the Evaluation and Report Language (EARL) 1.0 Guide.
EARL provides a format for expressing test results, such as those generated by Web accessibility evaluation tools, using a vendor-neutral and platform-independent format. While the review period has ended, ERT WG encourages you to review EARL 1.0 documents and submit any comments. See Call for Review: EARL 1.0 Last Call Working Draft e-mail for more information.
pointer-events applied to HTML (not just SVG). Only two values are supported: auto and none.color-correction addition.start and end values to float (CSS3 Box Model)background-opacity; considering functionality for future specs, but probably not in that form. (See previous discussions on targetting filters.)box-break: continuous | each-box will be renamed box-decoration-break: slice | clone unless there is consensus on a better proposal.