<?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>2009-11-19T19:05:06Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.261</generator>

<entry>
    <title>Last Call: XMLHttpRequest</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8660" />
    <id>tag:www.w3.org,2009://4.8660</id>

    <published>2009-11-19T19:04:21Z</published>
    <updated>2009-11-19T19:04:21Z</updated>

    <summary>The Web Applications Working Group has published a Last Call Working Draft of XMLHttpRequest. The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server. It is the ECMAScript HTTP API....</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Web Design and Applications" 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="/2008/webapps/">Web Applications Working Group</a> has published a Last Call Working Draft of <a href="/TR/2009/WD-XMLHttpRequest-20091119/">XMLHttpRequest</a>. The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server. It is the ECMAScript HTTP API. Comments are welcome through 16 December. Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>First Draft of File API Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8658" />
    <id>tag:www.w3.org,2009://4.8658</id>

    <published>2009-11-18T03:41:58Z</published>
    <updated>2009-11-18T03:41:58Z</updated>

    <summary>The Web Applications Working Group has published the First Public Working Draft of File API. This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data. This API is...</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/2009/WD-FileAPI-20091117/">File API</a>. This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data. This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest (e.g. with an overloaded send() method for File objects), postMessage, DataTransfer (part of the drag and drop API defined in [HTML5,]) and Web Workers. Additionally, it should be possible to programmatically obtain a list of files from the input element [HTML5] when it is in the File Upload state. These kinds of behaviors are defined in the appropriate affiliated specifications. Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Last Call: Widgets 1.0: The widget Interface</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8657" />
    <id>tag:www.w3.org,2009://4.8657</id>

    <published>2009-11-17T16:38:20Z</published>
    <updated>2009-11-17T16:38:20Z</updated>

    <summary>The Web Applications Working Group has published a Last Call Working Draft of Widgets 1.0: The widget Interface. This specification defines an application programming interface (API) for widgets that provides, amongst other things, functionality for accessing a widget&apos;s metadata and...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Other Agents" 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="/2008/webapps/">Web Applications Working Group</a> has published a Last Call Working Draft of <a href="/TR/2009/WD-widgets-apis-20091117/">Widgets 1.0: The widget Interface</a>. This specification defines an application programming interface (API) for widgets that provides, amongst other things, functionality for accessing a widget's metadata and persistently storing data. Comments are welcome through 08 December. Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Last Call: XML Entity definitions for Characters</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8656" />
    <id>tag:www.w3.org,2009://4.8656</id>

    <published>2009-11-17T16:35:51Z</published>
    <updated>2009-11-17T16:35:51Z</updated>

    <summary>The Math Working Group has published a Last Call Working Draft of XML Entity definitions for Characters. It is difficult to write science fluently if scientific characters are not available for use. It is difficult to read science if corresponding...</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="/Math/">Math Working Group</a> has published a Last Call Working Draft of <a href="/TR/2009/WD-xml-entity-names-20091117/">XML Entity definitions for Characters</a>. It is difficult to write science fluently if scientific characters are not available for use. It is difficult to read science if corresponding glyphs are not available for presentation. In the majority of cases it is preferable to store characters directly as Unicode character data or as XML numeric character references. However, in some environments it is more convenient to use the ASCII input mechanism provided by XML entity references. Many entity names are in common use, and this specification aims to provide standard mappings to Unicode for each of these names. It introduces no names that have not already been used in earlier specifications. Comments are welcome through 08 December. Learn more about the <a href="/Math/">Math Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>First Draft of Mobile Web for Social Development Roadmap Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8655" />
    <id>tag:www.w3.org,2009://4.8655</id>

    <published>2009-11-17T16:23:34Z</published>
    <updated>2009-11-17T16:23:34Z</updated>

    <summary>The Mobile Web For Social Development (MW4D) Interest Group has published a Group Note of Mobile Web for Social Development Roadmap. This document describes some of the current challenges of deploying development-oriented services on mobile phones. It suggests the most...</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 of Devices" 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/MW4D/">Mobile Web For Social Development (MW4D) Interest Group</a> has published a Group Note of <a href="/TR/2009/NOTE-mw4d-roadmap-20091117/">Mobile Web for Social Development Roadmap</a>. This document describes some of the current challenges of deploying development-oriented services on mobile phones. It suggests the most promising directions for lowering barriers to developing, deploying and accessing services on mobile phones and thereby creating an enabling environment for more social-oriented services to appear. Learn more about the <a href="/Mobile/">Mobile Web Initiative Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>World Wide Web Foundation Launches Operations and First Projects</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8654" />
    <id>tag:www.w3.org,2009://4.8654</id>

    <published>2009-11-15T13:35:29Z</published>
    <updated>2009-11-15T13:35:29Z</updated>

    <summary>Speaking at the Internet Governance Forum in Sharm el Sheikh, Egypt, Tim Berners-Lee announced today that World Wide Web Foundation is open for business. World Wide Web Foundation was created with W3C&apos;s support in September 2008, and focuses on advancing...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Home Page Stories" 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>Speaking at the <a href="http://igf09.eg/homeeng.html">Internet Governance Forum</a> in Sharm el Sheikh, Egypt, Tim Berners-Lee announced today that <a href="http://www.webfoundation.org">World Wide Web Foundation</a> is open for business. World Wide Web Foundation was <a href="/News/2008.html#entry-6786">created</a> with W3C's support in September 2008, and focuses on advancing the Web as a medium that empowers people to make positive social and economic change. Web Foundation's first two projects will help people to better leverage the Web to support <a href="http://www.webfoundation.org/projects/greening-africa/">agriculture in near-desert environments in Africa</a>, and <a href="http://www-dev.webfoundation.org/projects/empower-youth/">empowering youth in inner-city centers</a> by teaching them how to create Web content. Such projects are consistent with W3C's own work to ensure that One Web is available to all, including work on <a href="/2008/MW4D/">mobile Web for social development</a>, <a href="/WAI/">accessibility</a>, and <a href="/International/">internationalization</a>. W3C looks forward to collaborating with World Wide Web Foundation to further lower barriers to access and to promote the development of free and open Web standards.</p>]]>
    </content>
</entry>

<entry>
    <title>W3C Technical Plenary Convenes</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8651" />
    <id>tag:www.w3.org,2009://4.8651</id>

    <published>2009-11-04T18:37:58Z</published>
    <updated>2009-11-04T18:37:58Z</updated>

    <summary> The W3C community convenes today in Santa Clara, California for Technical Plenary (TPAC) 2009 to discuss: Decentralized Extensibility in HTML5 Maintaining a Healthy Internet Ecosystem -- Challenges to an Open Internet Infrastructure Privacy on the Web of Applications --...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/">
        
        <![CDATA[<p class="newsImage">
<a class="imageLink" href="/2009/11/TPAC/"><img alt="Natural Bridges (Santa Cruz, CA)" src="/2009/11/scbeach.jpg" height="133" width="200" /></a>
The W3C community convenes today in Santa Clara, California for <a href="/2009/11/TPAC/">Technical Plenary (TPAC) 2009</a> to discuss:</p>

<ul class="show_items newsImage">
<li>Decentralized Extensibility in HTML5</li>
<li>Maintaining a Healthy Internet Ecosystem -- Challenges to an Open Internet Infrastructure</li>
<li>Privacy on the Web of Applications -- Challenges and Opportunities</li>
<li>Web Apps vs App. Stores</li>
<li>Future of the Social Web</li>
<li>Twelve lightning talks</li>
</ul>

<p>This year, the <a href="http://www.isoc.org/">Internet Society (ISOC)</a>, as part of its mission to support the development of open standards, is sponsoring TPAC 2009. Tomorrow, the public will participate in discussion at W3C's first <a href="/2009/11/TPAC/DevMeeting">Developer Gathering</a>. Follow the goings-on via hash code "#tpac09" in various social networking channels. Procedings from the Plenary Day will be public. </p>]]>
    </content>
</entry>

<entry>
    <title>Five API Working Drafts Updated</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8650" />
    <id>tag:www.w3.org,2009://4.8650</id>

    <published>2009-10-30T20:02:36Z</published>
    <updated>2009-10-30T20:02:36Z</updated>

    <summary>The Web Applications Working Group has published updates to five Working Drafts of specifications for APIs that enhance the open Web platform as a runtime environment for full-featured applications: Web Sockets API provides an API for full-duplex communication between a...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Other Agents" 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="/2008/webapps/">Web Applications Working Group</a>
has published updates to five Working Drafts of specifications for
APIs that enhance the open Web platform as a runtime environment
for full-featured applications:</p>

<ul class="show_items">
 <li><a href="/TR/2009/WD-websockets-20091029/">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-webstorage-20091029/">Web Storage</a>
 provides APIs for Web applications to store key-value data on
 the client side.</li>
 <li><a href="/TR/2009/WD-webdatabase-20091029/">Web 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>
 <li><a href="/TR/2009/WD-workers-20091029/">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-20091029/">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>Note that the
<a href="/TR/2009/WD-webstorage-20091029/">Web Storage</a>
and <a href="/TR/2009/WD-webdatabase-20091029/">Web Database</a>
specifications were previously published as a single Working
Draft, but have now been split out into separate Working Drafts.
Learn more about the
<a href="/2006/rwc/">Rich Web Client Activity</a>.</p>
]]>
    </content>
</entry>

<entry>
    <title>Widgets 1.0: Packaging and Configuration Draft Updated</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8649" />
    <id>tag:www.w3.org,2009://4.8649</id>

    <published>2009-10-30T20:00:29Z</published>
    <updated>2009-10-30T20:00:29Z</updated>

    <summary>The Web Applications Working Group has published an updated Working Draft of Widgets 1.0: Packaging and Configuration, which standardizes a packaging format for software known as widgets. The specification relies on PKWare&apos;s Zip specification as the archive format, XML as...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Other Agents" 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="/2008/webapps/">Web Applications Working Group</a>
has published an updated Working Draft of
<a href="/TR/2009/WD-widgets-20091029/">Widgets 1.0: Packaging and Configuration</a>,
which standardizes a packaging format for software known as
widgets. The specification relies on PKWare's Zip specification as
the archive format, XML as a configuration document format, and
provides a series of steps that widget runtimes follow when
processing and verifying various aspects of a package. This
updated Working Draft addresses issues reported during the first
Candidate Recommendation phase (see the
<a href="/TR/2009/WD-widgets-20091029/#list-of-changes">list of changes</a>).
Learn more about the <a href="/2006/rwc/">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>DataCache API First Working Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8648" />
    <id>tag:www.w3.org,2009://4.8648</id>

    <published>2009-10-30T19:57:42Z</published>
    <updated>2009-10-30T19:57:42Z</updated>

    <summary>The Web Applications Working Group has published a First Public Working Draft of DataCache API, which provides Web applications with a means to programatically add and remove resources to a “data cache”, which can then be statically served by user...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Other Agents" 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="/2008/webapps/">Web Applications Working Group</a> has published a First Public Working Draft of
<a href="/TR/2009/WD-DataCache-20091029/">DataCache API</a>,
which provides Web applications with a means to programatically
add and remove resources to a “data cache”, which can then be
statically served by user agents when a particular resource is
requested. Learn more about the
<a href="/2006/rwc/Activity.html">Rich Web Client Activity</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>State Chart XML (SCXML) Working Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8647" />
    <id>tag:www.w3.org,2009://4.8647</id>

    <published>2009-10-30T19:56:19Z</published>
    <updated>2009-10-30T19:56:19Z</updated>

    <summary>The Voice Browser Working Group has published an updated Working Draft of State Chart XML (SCXML): State Machine Notation for Control Abstraction. SCXML is a general-purpose event-based state machine language that may be used in a number of ways, including...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Devices" 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="/Voice/">Voice Browser Working Group</a> has published
an updated Working Draft of <a href="/TR/2009/WD-scxml-20091029/">State Chart XML (SCXML): State Machine Notation for Control Abstraction</a>.
<abbr title="State Chart eXtensible Markup Language">SCXML</abbr> is a
general-purpose event-based state machine language that may be used in
a number of ways, including as a high-level dialog language
controlling VoiceXML 3.0's encapsulated speech modules, or as a
multimodal control language in the MultiModal Interaction
framework. The main difference from the
<a href="/TR/2009/WD-scxml-20090507/">previous draft</a> is
the correction of various inconsistencies. A
<a href="/TR/2009/WD-scxml-20091029/diff.html">diff-marked version</a>
of this document is also available for comparison purposes.
Learn more about the <a href="/Voice/">Voice Browser Activity</a>.
</p>
]]>
    </content>
</entry>

<entry>
    <title>First Draft of Emotion Markup Language (EmotionML) 1.0 Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8646" />
    <id>tag:www.w3.org,2009://4.8646</id>

    <published>2009-10-30T19:54:50Z</published>
    <updated>2009-10-30T19:54:50Z</updated>

    <summary> The Multimodal Interaction Working Group has published the First Public Working Draft of Emotion Markup Language (EmotionML) 1.0. EmotionML provides representations of emotions and related states for technological applications. The aim of this draft is to strike a balance...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Web of Devices" 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="/2002/mmi/">Multimodal Interaction
Working Group</a> has published the First Public Working Draft of <a
href="/TR/2009/WD-emotionml-20091029/"> Emotion Markup Language
(EmotionML) 1.0</a>. EmotionML provides representations of emotions and related states for technological applications. The aim of this draft is to strike a balance between practical applicability and scientific well-foundedness of emotion specification.
The language is conceived as a "plug-in" language suitable for use in
three different areas: (1) manual annotation of data, (2) automatic
recognition of emotion-related states from user behavior and (3)
generation of emotion-related system behavior.
Learn more about the <a href="/2002/mmi/">Multimodal Interaction
Activity</a>.
</p>
]]>
    </content>
</entry>

<entry>
    <title>Authoring Tool Accessibility Guidelines (ATAG) 2.0: Updated Working Draft</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8645" />
    <id>tag:www.w3.org,2009://4.8645</id>

    <published>2009-10-30T19:52:03Z</published>
    <updated>2009-10-30T19:52:03Z</updated>

    <summary>The Authoring Tool Accessibility Guidelines Working Group has published an updated Working Draft of Authoring Tool Accessibility Guidelines (ATAG) 2.0. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Browsers and Other Agents" 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="/WAI/AU/">Authoring Tool  Accessibility Guidelines Working Group</a> has published an updated Working Draft of <a href="/TR/2009/WD-ATAG20-20091029/">Authoring  Tool Accessibility Guidelines (ATAG) 2.0</a>. ATAG defines how authoring tools should help Web developers  produce Web content that is accessible and conforms to Web Content  Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make  authoring tools accessible so that people with disabilities can use  them. Read the <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2009OctDec/0046.html">invitation  to review the ATAG 2.0 Working Draft</a> and about the <a href="/WAI/">Web  Accessibility Initiative</a>.</p>]]>
    </content>
</entry>

<entry>
    <title>Last Call: Evaluation and Report Language (EARL) 1.0</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8644" />
    <id>tag:www.w3.org,2009://4.8644</id>

    <published>2009-10-30T19:49:32Z</published>
    <updated>2009-10-30T19:49:32Z</updated>

    <summary>The Evaluation and Repair Tools Working Group has published a Last Call Working Draft of the Evaluation and Report Language (EARL) 1.0 Schema, updated Working Drafts of HTTP Vocabulary in RDF 1.0, Representing Content in RDF 1.0, Pointer Methods in...</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="/WAI/ER/">Evaluation and Repair Tools Working Group</a> has published a Last Call Working Draft of the <a href="/TR/EARL10-Schema/">Evaluation and Report Language (EARL) 1.0 Schema</a>, updated Working Drafts of <a href="/TR/HTTP-in-RDF10/"><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Vocabulary in <acronym title="Resource Description Framework">RDF</acronym> 1.0</a>, <a href="/TR/Content-in-RDF10/">Representing Content in RDF 1.0</a>, <a href="/TR/Pointers-in-RDF10/">Pointer Methods in RDF 1.0</a>, <a href="/TR/EARL10-Requirements/">Evaluation and Report Language (EARL) 1.0 Requirements</a>, and a First Public Working Draft of the <a href="/TR/EARL10-Guide/">Evaluation and Report Language (EARL) 1.0 Guide</a>. EARL is a machine-readable format for expressing test results. The primary motivation for developing EARL is to facilitate the processing of test results, such as those generated by Web accessibility evaluation tools, using a vendor-neutral and platform-independent format. Read the <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2009OctDec/0045.html">invitation to review the EARL 1.0 Last Call Working Draft</a> and about the <a href="http://www.w3.org/WAI/">Web Accessibility Initiative (WAI)</a>. </p>]]>
    </content>
</entry>

<entry>
    <title>Web Services Fragment (WS-Fragment) First Draft Published</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/News/2009.html#entry-8643" />
    <id>tag:www.w3.org,2009://4.8643</id>

    <published>2009-10-30T19:44:59Z</published>
    <updated>2009-10-30T19:44:59Z</updated>

    <summary>The Web Services Resource Access Working Group has published the First Public Working Draft of Web Services Fragment (WS-Fragment). This specification extends the WS-Transfer [WS-Transfer] specification to enable clients to retrieve and manipulate parts or fragments of a WS-Transfer enabled...</summary>
    <author>
        <name>W3C Staff</name>
    </author>
    
        <category term="Publication" 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="/2002/ws/ra/">Web Services Resource Access Working Group</a> has published the First Public Working Draft of <a href="/TR/2009/WD-ws-fragment-20091027/">Web Services Fragment (WS-Fragment)</a>. This specification extends the WS-Transfer [WS-Transfer] specification to enable clients to retrieve and manipulate parts or fragments of a WS-Transfer enabled resource without needing to include the entire XML representation in a message exchange. Learn more about the <a href="/2002/ws/">Web Services Activity</a>.</p>]]>
    </content>
</entry>

</feed>
