<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>W3C News</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/" />
    <link rel="self" type="application/atom+xml" href="http://www.w3.org/News/atom.xml" />
    <id>tag:www.w3.org,2008-09-29://4</id>
    <updated>2010-01-21T23:14:44Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.261</generator>

<entry>
    <title>W3C Invites Implementations of W3C XML Schema Definition Language (XSD): Component Designators</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8703" />
    <id>tag:www.w3.org,2010://4.8703</id>

    <published>2010-01-21T23:12:47Z</published>
    <updated>2010-01-21T23:12:47Z</updated>

    <summary>The XML Schema Working Group invites implementation of the Candidate Recommendation of W3C XML Schema Definition Language (XSD): Component Designators. XML Schema: Component Designators defines a scheme for identifying XML Schema components as specified by XML Schema Part 1: Structures...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="XML Core Technologies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/XML/Schema">XML Schema Working Group</a> invites implementation of the Candidate Recommendation of <a href="/TR/2010/CR-xmlschema-ref-20100119/">W3C XML Schema Definition Language (XSD): Component Designators</a>. XML Schema: Component Designators defines a scheme for identifying XML Schema components as specified by XML Schema Part 1: Structures and XML Schema Part 2: Datatypes. Learn more about the <a href="/XML/">Extensible Markup Language (XML) Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Updated Draft: Use Cases and Requirements for Ontology and API for Media Resource 1.0 </title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8702" />
    <id>tag:www.w3.org,2010://4.8702</id>

    <published>2010-01-21T23:07:27Z</published>
    <updated>2010-01-21T23:07:27Z</updated>

    <summary>The Media Annotations Working Group has published a Working Draft of Use Cases and Requirements for Ontology and API for Media Resource 1.0. This document specifies use cases and requirements as an input for the development of the &quot;Ontology for...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Semantic Web" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2008/WebVideo/Annotations/">Media Annotations Working Group</a> has published  a Working Draft of <a href="/TR/2010/WD-media-annot-reqs-20100121">Use Cases and Requirements for Ontology and API for Media Resource 1.0</a>.
    This document specifies use cases and requirements as an input for the
development of the "Ontology for Media Resource 1.0" and the "API for Media
Resource 1.0". The ontology will be a simple ontology to support
cross-community data integration of information related to media resources on
the Web. The API will provide read access and potentially write access to media
resources, relying on the definitions from the ontology. Learn more about the <a href="/2008/WebVideo/">Video in the Web Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Last Call: CSS Styling Attributes Level 1</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8701" />
    <id>tag:www.w3.org,2010://4.8701</id>

    <published>2010-01-21T23:05:27Z</published>
    <updated>2010-01-21T23:05:27Z</updated>

    <summary>The Cascading Style Sheets (CSS) Working Group has published a Last Call Working Draft of CSS Styling Attributes Level 1. Markup languages such as HTML and SVG provide a styling attribute on most elements, to hold a fragment of a...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> has published a Last Call Working Draft of <a href="/TR/2010/WD-css-style-attr-20100121/">CSS Styling Attributes Level 1</a>. Markup languages such as HTML and SVG provide a styling attribute on most elements, to hold a fragment of a style sheet that applies to those elements. One of the possible style sheet languages is CSS. This draft describes the syntax and interpretation of the CSS fragment that can be used in such styling attributes. Comments are welcome through 09 February. Learn more about the <a href="/Style/">Style Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Contacts API First Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8700" />
    <id>tag:www.w3.org,2010://4.8700</id>

    <published>2010-01-21T23:03:29Z</published>
    <updated>2010-01-21T23:03:29Z</updated>

    <summary>The Device APIs and Policy Working Group has published the First Public Working Draft of Contacts API. This API provides access to the user???s address book from within a browser environment. Learn more about JavaScript interfaces developed in W3C....</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2009/dap/">Device APIs and Policy Working Group</a> has published the First Public Working Draft of <a href="/TR/2010/WD-contacts-api-20100121/">Contacts API</a>. This API provides access to the user???s address book from within a browser environment. Learn more about <a href="/standards/techs/js">JavaScript interfaces developed in W3C</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Interested in Next Steps for RDF? Come to the W3C Workshop!</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8699" />
    <id>tag:www.w3.org,2010://4.8699</id>

    <published>2010-01-20T22:41:04Z</published>
    <updated>2010-01-20T22:41:04Z</updated>

    <summary>W3C is organizing a Workshop on the Next Steps for RDF around June 2010; we will announce the exact dates and location as soon as possible. Since its publication in 2004, the Resource Description Framework (RDF) has become the core...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Semantic Web" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Top Story" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>W3C is organizing a 
<a href="/2009/12/rdf-ws/cfp">Workshop on the Next Steps for RDF</a> around June 2010; we will announce the exact dates and location as soon as possible. Since its publication in 2004, the <a href="/TR/2004/REC-rdf-concepts-20040210/">Resource
Description Framework (RDF)</a> has become the core architectural block of the <a href="/2001/sw/">Semantic Web</a>. The standard is now widely deployed in terms of tools and applications. Due to this wide deployment, additional R&amp;D activities, and the publication of newer standards (e.g., <a href="/TR/rdf-sparql-query/">SPARQL</a>,
<a href="/TR/owl2-overview/">OWL</a>, <a href="/TR/powder-primer/">POWDER</a>, and <a href="/TR/skos-reference">SKOS</a>), a number of
issues regarding RDF have come to the fore. Workshop articipants 
will discuss these issues and help determine whether it is time for a new version of RDF.
W3C Membership is not required to participate
in the Workshop, but each participant must be associated with an accepted
position paper. The deadline for position papers is 29 March 2010; see the  <a
href="/2009/12/rdf-ws/cfp">Call for Participation</a> for
more information. Updates (including the exact date and location of the Workshop) will be added to the Call for Participation and will be announced on the <a
href="/2001/sw/anews">Semantic Web Activity News Blog</a>.</p>
]]>
    </content>
</entry>

<entry>
    <title>Selectors API Level 2 First Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8698" />
    <id>tag:www.w3.org,2010://4.8698</id>

    <published>2010-01-19T21:08:40Z</published>
    <updated>2010-01-19T21:08:40Z</updated>

    <summary>The Web Applications Working Group has published the First Public Working Draft of Selectors API Level 2. Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2008/webapps/">Web Applications Working Group</a> has published the First Public Working Draft of <a href="/TR/2010/WD-selectors-api2-20100119/">Selectors API Level 2</a>. Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors, and for testing if a given element matches a particular selector. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring and testing specific elements, especially compared with the more verbose techniques defined and used in the past. Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Call for Review: WebCGM 2.1 Proposed Recommendation Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8696" />
    <id>tag:www.w3.org,2010://4.8696</id>

    <published>2010-01-14T15:11:43Z</published>
    <updated>2010-01-14T15:11:43Z</updated>

    <summary>The WebCGM Working Group has published a Proposed Recommendation of WebCGM 2.1. Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM,...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/Graphics/WebCGM/WG/">WebCGM Working Group</a> has published a Proposed Recommendation of <a href="/TR/2010/PR-webcgm21-20100114/">WebCGM 2.1</a>. Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. WebCGM 2.1, refines and completes the features of the major WebCGM 2.0 release. WebCGM 2.0 added a DOM (API) specification for programmatic access to WebCGM objects, a specification of an XML Companion File (XCF) architecture, and extended the graphical and intelligent content of WebCGM 1.0. Comments are welcome through 11 February. Learn more about the <a href="/Graphics/">Graphics Activity</a>. <em>The review end date was corrected on 20 January.</em></p>]]>
    </content>
</entry>

<entry>
    <title>Programmable HTTP Caching and Serving Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8695" />
    <id>tag:www.w3.org,2010://4.8695</id>

    <published>2010-01-14T15:10:22Z</published>
    <updated>2010-01-14T15:10:22Z</updated>

    <summary>The Web Applications Working Group has published a Working Draft of Programmable HTTP Caching and Serving. This document defines APIs for off-line serving of requests to HTTP resources using static and dynamic responses. It extends the function of application caches...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2008/webapps/">Web Applications Working Group</a> has published a Working Draft of <a href="/TR/2010/WD-DataCache-20100114/">Programmable HTTP Caching and Serving</a>. This document defines APIs for off-line serving of requests to HTTP resources using static and dynamic responses. It extends the function of application caches defined in HTML5. Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title> W3C Advisory Committee Elects Technical Architecture Group Participants [CORRECTION]</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8694" />
    <id>tag:www.w3.org,2010://4.8694</id>

    <published>2010-01-11T17:39:54Z</published>
    <updated>2010-01-11T17:39:54Z</updated>

    <summary>Correction 13 January 2010 : The W3C Advisory Committee has elected Daniel Appelquist (Vodafone) and Henry Thompson (U. of Edinburgh) to the W3C Technical Architecture Group (TAG). The Director has appointed Ashok Malhotra (Oracle), Noah Mendelsohn, and Jonathan Rees. This...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Web Architecture" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p><em>Correction 13 January 2010</em> :  The W3C Advisory Committee has elected Daniel Appelquist (Vodafone) and Henry Thompson (U. of Edinburgh) to the W3C <a href="/2001/tag/">Technical Architecture Group (TAG)</a>. The Director has appointed Ashok Malhotra (Oracle), Noah Mendelsohn, and Jonathan Rees. This outcome reflects the correct application of the tie-breaking algorithm.</p>


<p><em>Original message from 11 January:</em> The W3C Advisory Committee has re-elected Ashok Malhotra (Oracle) and Henry Thompson (U. of Edinburgh) to the W3C <a href="/2001/tag/">Technical Architecture Group (TAG)</a>. Continuing TAG participants are John Kemp (Nokia), Larry Masinter (Adobe), T.V. Raman (Google). The Director is also expected to appoint three individuals very soon. The <a href="/2004/10/27-tag-charter.html#Mission">mission</a> of the TAG is to build consensus around principles of Web architecture and to interpret and clarify these principles when necessary, to resolve issues involving general Web architecture brought to the TAG, and to help coordinate cross-technology architecture developments inside and outside W3C.</p>]]>
    </content>
</entry>

<entry>
    <title>New WAI Resource: Contacting Organizations about Inaccessible Websites</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8692" />
    <id>tag:www.w3.org,2010://4.8692</id>

    <published>2010-01-06T14:16:51Z</published>
    <updated>2010-01-06T14:16:51Z</updated>

    <summary>The Web Accessibility Initiative (WAI) Education and Outreach Working Group (EOWG) today published Contacting Organizations about Inaccessible Websites as part of the WAI-AGE Project. This new WAI resource guides you through telling organizations about accessibility barriers on their website. WAI...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The Web Accessibility Initiative (WAI) Education and Outreach Working Group (<a href="/WAI/EO/">EOWG</a>) today published <strong><a href="/WAI/users/inaccessible">Contacting Organizations about Inaccessible Websites</a></strong> as part of the <a href="/WAI/WAI-AGE/">WAI-AGE Project</a>. This new WAI resource guides you through telling organizations about accessibility barriers on their website. WAI would like to know how this resource works for you and how we can improve it. See the blog post: <a href="/QA/2010/01/encourage_accessibility_make_a_difference.html">Take a few minutes to encourage web accessibility. Your voice counts</a>. <strong>Learn about <a href="/standards/webdesign/accessibility">Accessibility</a></strong> and visit the <a href="/WAI/">WAI home page</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Last Call: XProc: An XML Pipeline Language</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8690" />
    <id>tag:www.w3.org,2010://4.8690</id>

    <published>2010-01-05T19:00:46Z</published>
    <updated>2010-01-05T19:00:46Z</updated>

    <summary>The XML Processing Model Working Group has published a Last Call Working Draft of XProc: An XML Pipeline Language, a language for describing operations to be performed on XML documents. A pipeline consists of steps. Like pipelines, steps take zero...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="XML Core Technologies" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/XML/Processing/">XML Processing Model Working Group</a> has published a Last Call Working Draft of <a href="/TR/2010/WD-xproc-20100105/">XProc: An XML Pipeline Language</a>, a language for describing operations to be performed on XML documents. A pipeline consists of steps. Like pipelines, steps take zero or more XML documents as their inputs and produce zero or more XML documents as their outputs. The inputs of a step come from the web, from the pipeline document, from the inputs to the pipeline itself, or from the outputs of other steps in the pipeline. The outputs from a step are consumed by other steps, are outputs of the pipeline as a whole, or are discarded. Comments are welcome through 02 February. Learn more about the <a href="/XML/">Extensible Markup Language (XML) Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Indexed Database API Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2010.html#entry-8689" />
    <id>tag:www.w3.org,2010://4.8689</id>

    <published>2010-01-05T14:54:45Z</published>
    <updated>2010-01-05T14:54:45Z</updated>

    <summary>The Web Applications Working Group has published a Working Draft of Indexed Database API. User agents need to store large numbers of objects locally in order to satisfy off-line data requirements of Web applications. The Web Storage specification is useful...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2008/webapps/">Web Applications Working Group</a> has published a Working Draft of <a href="/TR/2010/WD-IndexedDB-20100105/">Indexed Database API</a>. User agents need to store large numbers of objects locally in order to satisfy off-line data requirements of Web applications. The Web Storage specification is useful for storing pairs of keys and their corresponding values. However, it does not provide in-order retrieval of keys, efficient searching over values, or storage of duplicate values for a key. The current specification provides a concrete API to perform advanced key-value data management that is at the heart of most sophisticated query processors. It does so by using transactional databases to store keys and their corresponding values (one or more per key), and providing a means of traversing keys in a deterministic order. Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Seven API Publications Advance Web Applications Stack</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8688" />
    <id>tag:www.w3.org,2009://4.8688</id>

    <published>2009-12-22T15:15:51Z</published>
    <updated>2009-12-22T15:15:51Z</updated>

    <summary>The Web Applications Working Group has published updates to seven specifications related to APIs that enhance the open Web platform as a runtime environment for full-featured applications. W3C invites implementation experience for the two newest Candidate Recommendations: The Widget Interface...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2008/webapps/">Web Applications Working Group</a>
has published updates to seven specifications related to 
APIs that enhance the open Web platform as a runtime environment
for full-featured applications. 
W3C invites implementation experience for the two newest
Candidate Recommendations: </p>

<ul class="show_items">
<li><a href="/TR/2009/CR-widgets-apis-20091222/">The Widget Interface</a> 
defines an application programming interface (API) for widgets that provides functionality for accessing a widget's metadata and persistently storing data.
The group's <a href="http://dev.w3.org/2006/waf/widgets-api/imp-report/">implementation report</a> will be used to track progress.</li>
<li><a href="/TR/2009/CR-selectors-api-20091222/">Selectors API Level 1</a> 
defines methods for retrieving Element nodes from the DOM by matching against a group of selectors (such as those used in Cascading Style Sheets). The
group is developing a <a href="http://dev.w3.org/2006/webapi/selectors-api-testsuite/">selectors API test suite</a>.</li>
</ul>


<p>Comments on these Last Call Working Drafts are welcome until 30 June 2010:</p>

<ul class="show_items">
 <li><a href="/TR/2009/WD-webstorage-20091222/">Web Storage</a>
 provides APIs for Web applications to store key-value data on
 the client side.</li>
 <li><a href="/TR/2009/WD-workers-20091222/">Web Workers</a>
 defines an API for enabling thread-like operations (using
 message passing) in Web applications, so that certain
 application tasks can be run in parallel.</li>
 <li><a href="/TR/2009/WD-eventsource-20091222/">Server-Sent Events</a>
 defines an API for a Web application to open an HTTP connection
 for receiving push notifications from a server, in the form of
 DOM events.</li>
</ul>

<p>The group also updated these Working Drafts:</p>

<ul class="show_items">
 <li><a href="/TR/2009/WD-websockets-20091222/">Web Sockets API</a>
 provides an API for full-duplex communication between a Web
 application and a remote host.</li>
 <li><a href="/TR/2009/WD-webdatabase-20091222/">Web SQL Database</a>
 defines an API for Web applications to store data in client-side
 databases that can be queried using a variant of SQL.</li>
</ul>

<p>Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>
]]>
    </content>
</entry>

<entry>
    <title>W3C Invites Implementations of Web Security Context: User Interface Guidelines</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8687" />
    <id>tag:www.w3.org,2009://4.8687</id>

    <published>2009-12-22T15:10:35Z</published>
    <updated>2009-12-22T15:10:35Z</updated>

    <summary>The Web Security Context Working Group invites implementation of the Candidate Recommendation of Web Security Context: User Interface Guidelines. This specification deals with the trust decisions that users must make online, and with ways to support them in making safe...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Authoring Tools" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/2006/WSC/">Web Security Context Working Group</a> invites implementation of the Candidate Recommendation of <a href="/TR/2009/CR-wsc-ui-20091222/">Web Security Context: User Interface Guidelines</a>. This specification deals with the trust decisions that users must make online, and with ways to support them in making safe and informed decisions where possible. It specifies user interactions with a goal toward making security usable, based on known best practice in this area. Read the group's expectations about <a href="http://www.w3.org/TR/2008/NOTE-wsc-usecases-20080306/#usability-testing">implementation and testing</a> and learn more about the <a href="/Security/">Security Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>W3C Invites Implementations of CSS Backgrounds and Borders Module Level 3, Multi-Column Layout</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8686" />
    <id>tag:www.w3.org,2009://4.8686</id>

    <published>2009-12-17T18:27:18Z</published>
    <updated>2009-12-17T18:27:18Z</updated>

    <summary>The Cascading Style Sheets (CSS) Working Group invites implementation of two Candidate Recommendations: CSS Backgrounds and Borders Module Level 3 and CSS Multi-column Layout Module. CSS is a language for describing the rendering of structured documents (such as HTML and...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The <a href="/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> invites implementation of two Candidate Recommendations: <a href="/TR/2009/CR-css3-background-20091217/">CSS Backgrounds and Borders Module Level 3</a> and <a href="/TR/2009/CR-css3-multicol-20091217/">CSS Multi-column Layout Module</a>. CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. The main extensions in Backgrounds and Borders over CSS 2 related to borders consisting of images, boxes with multiple backgrounds, boxes with rounded corners and boxes with shadows. Multicolumn features allow authors to flow content into multiple columns with a gap and a rule between them. Learn more about the <a href="/Style/">Style Activity</a>.</p>]]>
    </content>
</entry>

</feed>
