The Web Applications Working Group has published a Working Draft of File API. Web applications should have the ability to manipulate as wide as possible a range of user input, including files that a user may wish to upload to a remote server or manipulate inside a rich web application. This specification defines the basic representations for files, lists of files, errors raised by access to files, and programmatic ways to read files. Additionally, this specification also defines an interface that represents "raw data" which can be asynchronously processed on the main thread of conforming user agents. The interfaces and API defined in this specification can be used with other interfaces and APIs exposed to the Open Web Platform. Learn more about the Rich Web Client Activity.

JSON has proven to be a highly useful object serialization and messaging format. JSON-LD harmonizes the representation of Linked Data in JSON by outlining a common JSON representation format for expressing directed graphs; mixing both Linked Data and non-Linked Data in a single document. The RDF Working Group has published two related First Public Working Drafts:

• JSON-LD API 1.0 outlines an API and a set of algorithms for transforming JSON-LD documents in order to make them easier to work with in programming environments like JavaScript, Python, and Ruby.
• JSON-LD Syntax 1.0 outlines a common JSON representation format for expressing directed graphs; mixing both Linked Data and non-Linked Data in a single document.

Learn more about the Semantic Web Activity.

The Protocols and Formats Working Group (PFWG) invites implementations of the Candidate Recommendation Role Attribute, an XML attribute that allows the author to add semantic information to documents. Role Attribute supports WAI-ARIA, the Accessible Rich Internet Applications technical specification for making dynamic, interactive web content accessible to people with disabilities. Read the Role Attribute Candidate Recommendation e-mail announcement for more information, and about the Web Accessibility Initiative (WAI).

The XSLT Working Group has published a Working Draft of XSL Transformations (XSLT) Version 3.0. This specification defines the syntax and semantics of XSLT 3.0, a language for transforming XML documents into other XML documents. Learn more about the Extensible Markup Language (XML) Activity.

The XML Security Working Group has published a Group Note of XML Signature Best Practices. This document collects best practices for implementers and users of the XML Signature specification. Most of these best practices are related to improving security and mitigating attacks, yet others are for best practices in the practical use of XML Signature, such as signing XML that doesn't use namespaces, for example. Learn more about the Security Activity.

The Browser Testing and Tools Working Group has published the First Public Working Draft of WebDriver. This specification defines the WebDriver API, a platform-and language-neutral interface that allows programs or scripts to introspect into, and control the behaviour of, a web browser. The WebDriver API is primarily intended to allow developers to write tests that automate a browser from a separate controlling process, but may also be implemented in such a way as to allow in-browser scripts to control a browser. Learn more about the Web Testing Activity.

The RDF Working Group has published a Last Call Working Draft of Turtle. The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. Comments are welcome through 15 September. This document defines a textual syntax for RDF called Turtle that allows an RDF graph to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Learn more about the Semantic Web Activity.

The Internationalization Core Working Group has published the First Public Working Draft of Use Cases and Exploratory Approaches for Ruby Markup. This document looks at a number of use cases involving ruby, and examines the pros and cons of a number of alternative approaches for meeting those use cases using the current HTML5 model, the XHTML Ruby Annotation model, and two other models. The aim is to clarify which use cases are supported by the existing markup models (HTML5 or XHTML), and where they are not, provide suggestions about how the markup model could be adapted to support those use cases. Learn more about the Internationalization Activity.

The Web Application Security Working Group has published a Last Call Working Draft of Content Security Policy 1.0. This document defines Content Security Policy, a mechanism web applications can use to mitigate a broad class of content injection vulnerabilities, such as cross-site scripting (XSS). Content Security Policy is a declarative policy that lets the authors (or server administrators) of a web application restrict from where the application can load resources. Comments are welcome through 24 August. Learn more about the Security Activity.