<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Recent Publications</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>2013-06-18T22:30:23Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.34-en</generator>

<entry>
    <title>Scalable Vector Graphics (SVG) 2 Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9866" />
    <id>tag:www.w3.org,2013://4.9866</id>

    <published>2013-06-18T22:29:41Z</published>
    <updated>2013-06-18T22:30:23Z</updated>

    <summary>The SVG Working Group has published a Working Draft of Scalable Vector Graphics (SVG) 2. This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 2, a language for describing two-dimensional vector and mixed vector/raster graphics. Changes...</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="http://www.w3.org/Graphics/SVG/WG/">SVG Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-SVG2-20130409/">Scalable Vector Graphics (SVG) 2</a>. This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 2, a language for describing two-dimensional vector and mixed vector/raster graphics. Changes in this working draft include introduction of a new <a href="http://www.w3.org/TR/SVG2/pservers.html#Hatches">‘hatch’</a> element as a refinement on patterns, improved accessibility and integration with HTML through the addition of the <a href="http://www.w3.org/TR/SVG2/interact.html#SVGElementTabindexAttribute">‘tabindex’</a> attribute and changes to the <a href="http://www.w3.org/TR/SVG2/extend.html#ForeignObjectElement">‘foreignObject’</a> element, addition of a new 'auto-start-reverse' attribute value for markers, clarification of CSS transforms on SVG content, and various updates to bring SVG closer in line with CSS best practices. See the <a href="http://www.w3.org/TR/SVG2/changes.html">full list of modifications</a> in the SVG changes appendix. Learn more about the <a href="http://www.w3.org/Graphics/">Graphics Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Test cases for Canonical XML 2.0 Note Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9865" />
    <id>tag:www.w3.org,2013://4.9865</id>

    <published>2013-06-18T22:27:30Z</published>
    <updated>2013-06-18T22:27:45Z</updated>

    <summary>The XML Security Working Group has published a Group Note of Test cases for Canonical XML 2.0. This document outlines test cases for Canonical XML 2.0. Learn more about the Security Activity....</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="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="http://www.w3.org/2008/xmlsec/">XML Security Working Group</a> has published a Group Note of <a href="http://www.w3.org/TR/2013/NOTE-xml-c14n2-testcases-20130618/">Test cases for Canonical XML 2.0</a>. This document outlines test cases for Canonical XML 2.0. Learn more about the <a href="http://www.w3.org/Security/">Security Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Mobile Accessibility Examples: Implementing UAAG 2.0 Updated</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9859" />
    <id>tag:www.w3.org,2013://4.9859</id>

    <published>2013-06-06T13:57:37Z</published>
    <updated>2013-06-06T14:02:05Z</updated>

    <summary>One aspect of mobile accessibility is how web browsers on mobile devices support the accessibility needs of people with disabilities. Accessibility of web browsers is covered in User Agent Accessibility Guidelines (UAAG). The User Agent Accessibility Guidelines Working Group (UAWG)...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Authoring Tools" 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" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Services" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>One aspect of mobile accessibility is how web browsers on mobile devices support the accessibility needs of people with disabilities. Accessibility of web browsers is covered in User Agent Accessibility Guidelines (<a href="http://www.w3.org/WAI/intro/uaag">UAAG</a>). The User Agent Accessibility Guidelines Working Group (<a href="http://www.w3.org/WAI/UA/">UAWG</a>) today published an updated Working Draft of Implementing UAAG 2.0, which explains how browsers, media players, and other &quot;user agents&quot; should support accessibility for people with disabilities and work with assistive technologies. The update provides a page of <a href="http://www.w3.org/TR/IMPLEMENTING-UAAG20/mobile"><strong>Mobile Accessibility Examples from UAAG</strong></a> that show how web browsers that follow UAAG benefit people with disabilities using the Web on mobile devices. Learn more about  W3C WAI's broader work related to <a href="http://www.w3.org/WAI/mobile"><strong>Mobile Accessibility</strong></a> and about the <a href="http://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</a>.</p> ]]>
    </content>
</entry>

<entry>
    <title>HTML5 Image Description Extension Working Draft</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9858" />
    <id>tag:www.w3.org,2013://4.9858</id>

    <published>2013-06-06T13:52:06Z</published>
    <updated>2013-06-18T22:29:29Z</updated>

    <summary><![CDATA[The HTML Working Group has published an updated Working Draft of the HTML5 Image Description Extension. This specification defines the &quot;longdesc&quot; attribute that enables web authors to provide longer text descriptions for complex images. It is developed by the HTML...]]></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" />
    
        <category term="Web of Services" 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="http://www.w3.org/html/wg/">HTML Working Group</a> has published an updated Working Draft of the <a href="http://www.w3.org/TR/2013/WD-html-longdesc-20130606/"> HTML5 Image Description Extension</a>. This specification defines the &quot;longdesc&quot; attribute that enables web authors to provide longer text descriptions for complex images. It is developed by the <a href="http://www.w3.org/WAI/PF/html-accessibility-tf.html">HTML Accessibility Task Force</a> in coordination with the <a href="http://www.w3.org/html/wg/">HTML Working Group</a>  and the <a href="http://www.w3.org/WAI/">WAI</a> Protocols and Formats Working Group (<a href="http://www.w3.org/WAI/PF/">PFWG</a>). Please see important additional information in the <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2013AprJun/0262.html">call for review e-mail</a>. This Working Draft is available for review through 20 June 2013 to determine if there are any outstanding issues before it progresses to Last Call. Learn more about the <a href="http://www.w3.org/MarkUp/Activity">HTML Activity</a> and the <a href="http://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Widget Updates Note, Introduction to Web Components Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9851" />
    <id>tag:www.w3.org,2013://4.9851</id>

    <published>2013-06-06T13:50:42Z</published>
    <updated>2013-06-18T22:28:59Z</updated>

    <summary>The Web Applications Working Group has published two documents today: A Group Note of Widget Updates. This specification defines a process and a document format to allow a user agent to update an installed widget package with a different version...</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="http://www.w3.org/2008/webapps/">Web Applications Working Group</a> has published two documents today:</p>
<ul class="show_items">
<li>A Group Note of <a href="http://www.w3.org/TR/2013/NOTE-widgets-updates-20130606/">Widget Updates</a>. This specification defines a process and a document format to allow a user agent to update an installed widget package with a different version of a widget package. A widget cannot automatically update itself; instead, a widget relies on the user agent to manage the update process. The working group reached consensus to stop work on this specification. It is published for archival reasons and no longer progresses along the W3C's Recommendation Track.</li>
<li>A Working Draft of <a href="http://www.w3.org/TR/2013/WD-components-intro-20130606/">Introduction to Web Components</a>. This document is a non-normative reference, which provides an overview of Web Components. It summarizes the normative information in the respective specifications in easy-to-digest prose with illustrations.</li>
</ul>
<p>Learn more about the <a href="http://www.w3.org/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>HTML Working Group Updated HTML 5.1, Differences from HTML4, Canvas 2D Context Level 2, and Published Three Notes</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9855" />
    <id>tag:www.w3.org,2013://4.9855</id>

    <published>2013-06-04T14:21:43Z</published>
    <updated>2013-06-06T14:06:57Z</updated>

    <summary>The HTML Working Group has updated three Working Drafts and published three Group Notes: a Working Draft of HTML 5.1. This specification defines the 5th major version, first minor revision of the core language of the World Wide Web: the...</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="http://www.w3.org/html/wg/">HTML Working Group</a> has updated three Working Drafts and published three Group Notes:</p>
<ul class="show_items">
<li>a Working Draft of <a href="http://www.w3.org/TR/2013/WD-html51-20130528/">HTML 5.1</a>. This specification defines the 5th major version, first minor revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features continue to be introduced to help Web application authors, new elements continue to be introduced based on research into prevailing authoring practices, and special attention continues to be given to defining clear conformance criteria for user agents in an effort to improve interoperability.</li>
<li>a Working Draft of <a href="http://www.w3.org/TR/2013/WD-html5-diff-20130528/">Differences from HTML4</a>. HTML is the core language of the World Wide Web. The W3C publishes HTML5 and HTML5.1. The WHATWG publishes HTML, which is a rough superset of W3C HTML5.1. "Differences from HTML4" describes the differences of the HTML specifications from those of HTML4, and calls out cases where they differ from each other. </li>
<li>a Working Draft of <a href="http://www.w3.org/TR/2013/WD-2dcontext2-20130528/">HTML Canvas 2D Context, Level 2</a>. This specification defines the 2D Context for the HTML canvas element. The 2D Context provides objects, methods, and properties to draw and manipulate graphics on a canvas drawing surface.</li>
<li>a Group Note of <a href="http://www.w3.org/TR/2013/NOTE-html5-author-20130528/">HTML5: Edition for Web Authors</a>. This document, now discontinued and made available for historical purposes, is targeted toward Web authors and others who are not UA implementors and who want a view of the HTML specification that focuses more precisely on details relevant to using the HTML language to create Web documents and Web applications.</li>
<li>a Group Note of <a href="http://www.w3.org/TR/2013/NOTE-html-main-element-20130528/">main element - an HTML5 extension specification</a>. This specification, now integrated into the HTML specification and no longer developed separately, defines an element to be used for the identification of the main content area of a document. It also defines an HTML element that embodies the semantics and function of the WAI-ARIA landmark role=main.</li>
<li>a Group Note of <a href="http://www.w3.org/TR/2013/NOTE-html-markup-20130528/">HTML: The Markup Language (an HTML language reference)</a>. This document describes the HTML markup language and provides details to help producers of HTML content create documents that conform to the language. This document has been discontinued and is only made available for historical purposes. For an up to date reference on HTML elements (and more) please consult <a href="http://docs.webplatform.org/wiki/Main_Page">Web Platform Docs</a>.</li>
</ul>
<p>Learn more about the <a href="http://www.w3.org/MarkUp/Activity">HTML Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>First Public Working Draft of URLs in Data Primer Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9854" />
    <id>tag:www.w3.org,2013://4.9854</id>

    <published>2013-06-04T13:07:11Z</published>
    <updated>2013-06-06T14:06:04Z</updated>

    <summary>The Technical Architecture Group has published the First Public Working Draft of URLs in Data Primer. This document describes how to define data formats and publish the information necessary to support an application in determining which mode is intended when...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <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>The <a href="http://www.w3.org/2001/tag/">Technical Architecture Group</a> has published the First Public Working Draft of <a href="http://www.w3.org/TR/2013/WD-urls-in-data-20130604/">URLs in Data Primer</a>. This document describes how to define data formats and publish the information necessary to support an application in determining which mode is intended when it encounters a URL in data. Learn more about the <a href="http://www.w3.org/2001/tag/">Technical Architecture Group</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Content Security Policy 1.1 Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9852" />
    <id>tag:www.w3.org,2013://4.9852</id>

    <published>2013-06-04T12:25:47Z</published>
    <updated>2013-06-06T14:05:57Z</updated>

    <summary>The Web Application Security Working Group has published a Working Draft of Content Security Policy 1.1. This document defines a policy language used to declare a set of content restrictions for a Web resource, and a mechanism for transmitting the...</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" />
    
        <category term="Web Design and Applications" 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="http://www.w3.org/2011/webappsec/">Web Application Security Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-CSP11-20130604/">Content Security Policy 1.1</a>. This document defines a policy language used to declare a set of content restrictions for a Web resource, and a mechanism for transmitting the policy from a server to a client where the policy is enforced. Learn more about the <a href="http://www.w3.org/Security/">Security Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Two Notes Published by the Government Linked Data Working Group</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9843" />
    <id>tag:www.w3.org,2013://4.9843</id>

    <published>2013-05-28T13:57:10Z</published>
    <updated>2013-05-30T14:27:36Z</updated>

    <summary>The Government Linked Data Working Group has published two Group Notes today: Registered Organization Vocabulary. The Registered Organization Vocabulary is a profile of the Organization Ontology for describing organizations that have gained legal entity status through a formal registration process,...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Semantic Web" 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="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> has published two Group Notes today:</p>
<ul class="show_items">
<li><a href="http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130528/">Registered Organization Vocabulary</a>. The Registered Organization Vocabulary is a profile of the Organization Ontology for describing organizations that have gained legal entity status through a formal registration process, typically in a national or regional register.</li>
<li><a href="http://www.w3.org/TR/2013/NOTE-vocab-adms-20130528/">Asset Description Metadata Schema (ADMS)</a>. ADMS is a profile of DCAT, used to describe semantic assets (or just 'Assets'), defined as highly reusable metadata (e.g. xml schemata, generic data models) and reference data (e.g. code lists, taxonomies, dictionaries, vocabularies) that are used for eGovernment system development.</li>
</ul>
<p>Learn more about the <a href="http://www.w3.org/2007/eGov/">eGovernment Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Filter Effects 1.0 Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9842" />
    <id>tag:www.w3.org,2013://4.9842</id>

    <published>2013-05-28T13:44:33Z</published>
    <updated>2013-05-30T14:31:53Z</updated>

    <summary>The Cascading Style Sheets (CSS) Working Group and the SVG Working Group have published a Working Draft of Filter Effects 1.0. Filter effects are a way of processing an element&apos;s rendering before it is displayed in the document. Typically, rendering...</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="http://www.w3.org/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> and the <a href="http://www.w3.org/Graphics/SVG/">SVG Working Group</a> have published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-filter-effects-20130523/">Filter Effects 1.0</a>. Filter effects are a way of processing an element's rendering before it is displayed in the document. Typically, rendering an element via CSS or SVG can conceptually be described as if the element, including its children, are drawn into a buffer (such as a raster image) and then that buffer is composited into the elements parent. Filters apply an effect before the compositing stage. Examples of such effects are blurring, changing color intensity and warping the image. Although originally designed for use in SVG, filter effects are a set of operations to apply on an image buffer and therefore can be applied to nearly any presentational environment, including CSS. They are triggered by a style instruction (the ‘filter’ property). This specification describes filters in a manner that allows them to be used in content styled by CSS, such as HTML and SVG. It also defines a CSS property value function that produces a CSS &lt;image&gt; value. Learn more about the <a href="http://www.w3.org/Style/">Style Activity</a>, and the <a href="http://www.w3.org/Graphics/">Graphics Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>CSS Exclusions  and CSS Regions Drafts Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9841" />
    <id>tag:www.w3.org,2013://4.9841</id>

    <published>2013-05-28T13:36:01Z</published>
    <updated>2013-06-04T12:20:00Z</updated>

    <summary>The Cascading Style Sheets (CSS) Working Group has published three Working Drafts today: CSS Exclusions Module Level 1. CSS Exclusions define arbitrary areas around which inline content (CSS21) can flow. CSS Exclusions can be defined on any CSS block-level elements....</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="http://www.w3.org/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> has published three Working Drafts today:</p>
<ul class="show_items">
<li><a href="http://www.w3.org/TR/2013/WD-css3-exclusions-20130528/">CSS Exclusions Module Level 1</a>. CSS Exclusions define arbitrary areas around which inline content (CSS21) can flow. CSS Exclusions can be defined on any CSS block-level elements. CSS Exclusions extend the notion of content wrapping previously limited to floats.</li>
<li><a href="http://www.w3.org/TR/2013/WD-css3-regions-20130528/">CSS Regions Module Level 1</a>. The CSS regions module allows content to flow across multiple areas called regions. The regions are not necessarily contiguous in the document order. The CSS regions module provides an advanced content flow mechanism, which can be combined with positioning schemes as defined by other CSS modules such as the Multi-Column Module or the Grid Layout Module to position the regions where content flows.</li>
</ul>
<p>Learn more about the <a href="http://www.w3.org/Style/">Style Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>User Interface Security Directives for Content Security Policy Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9838" />
    <id>tag:www.w3.org,2013://4.9838</id>

    <published>2013-05-23T16:18:05Z</published>
    <updated>2013-05-28T14:02:58Z</updated>

    <summary>The Web Application Security Working Group has published a Working Draft of User Interface Security Directives for Content Security Policy. This document defines directives for the Content Security Policy mechanism to declare a set of input protections for a web...</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" />
    
        <category term="Web Design and Applications" 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="http://www.w3.org/2011/webappsec/">Web Application Security Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2013/WD-UISecurity-20130523/">User Interface Security Directives for Content Security Policy</a>. This document defines directives for the Content Security Policy mechanism to declare a set of input protections for a web resource's user interface, defines a non-normative set of heuristics for Web user agents to implement these input protections, and a reporting mechanism for when they are triggered. Learn more about the <a href="http://www.w3.org/Security/">Security Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Web Intents Note Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9837" />
    <id>tag:www.w3.org,2013://4.9837</id>

    <published>2013-05-23T16:15:00Z</published>
    <updated>2013-05-28T14:02:53Z</updated>

    <summary>The Device APIs Working Group and the Web Applications (WebApps) Working Group have published Working Group Note of Web Intents. This informative specification defines a service discovery and light-weight RPC mechanism for web apps called Web Intents. This document defines...</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="http://www.w3.org/2009/dap/">Device APIs Working Group</a> and the <a href="http://www.w3.org/2008/webapps/">Web Applications (WebApps) Working Group</a> have published Working Group Note of <a href="http://www.w3.org/TR/2013/NOTE-web-intents-20130523/">Web Intents</a>. This informative specification defines a service discovery and light-weight RPC mechanism for web apps called Web Intents. This document defines DOM interfaces and markup used by client and service pages to create, receive, and reply to Web Intents messages, and the procedures the User Agent carries out to facilitate that process. Learn more about the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Last Call: Vibration API</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9836" />
    <id>tag:www.w3.org,2013://4.9836</id>

    <published>2013-05-23T15:58:39Z</published>
    <updated>2013-05-28T14:02:48Z</updated>

    <summary>The Device APIs Working Group has published a Last Call Working Draft of Vibration API. This specification defines an API that provides access to the vibration mechanism of the hosting device. Vibration is a form of tactile feedback. Comments are...</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="http://www.w3.org/2009/dap/">Device APIs Working Group</a> has published a Last Call Working Draft of <a href="http://www.w3.org/TR/2013/WD-vibration-20130523/">Vibration API</a>. This specification defines an API that provides access to the vibration mechanism of the hosting device. Vibration is a form of tactile feedback. Comments are welcome through 13 June. Learn more about the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>User Agent Accessibility Guidelines (UAAG) 2.0 and Implementing UAAG 2.0 Working Drafts</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2013.html#entry-9835" />
    <id>tag:www.w3.org,2013://4.9835</id>

    <published>2013-05-23T15:30:06Z</published>
    <updated>2013-05-28T14:02:43Z</updated>

    <summary><![CDATA[The User Agent Accessibility Guidelines Working Group (UAWG) today published updated Working Drafts of User Agent Accessibility Guidelines (UAAG) 2.0 and Implementing UAAG 2.0, which define how browsers, media players, and other &quot;user agents&quot; should support accessibility for people with...]]></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" />
    
        <category term="Web Design and Applications" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Services" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p>The User Agent Accessibility Guidelines Working Group (<a href="http://www.w3.org/WAI/UA/">UAWG</a>) today published updated Working Drafts of <a href="http://www.w3.org/TR/UAAG20/">User Agent Accessibility Guidelines (UAAG) 2.0</a> and <a href="http://www.w3.org/TR/Implementing-UAAG20/">Implementing UAAG 2.0</a>, which define how browsers, media players, and other &quot;user agents&quot; should support accessibility for people with disabilities and work with assistive technologies. These drafts have new examples of how UAAG applies in the mobile environment, an updated conformance section, and new definitions of level A, AA, and AAA. Learn more in the <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2013AprJun/0235.html">call for review  e-mail</a> and read about the <a
href="http://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</a>.</p>]]>
    </content>
</entry>

</feed>
