The Spatial Data on the Web Working Group has published a Group Note of Spatial Data on the Web Use Cases & Requirements. This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC.

The XML Query Working Group and the XSLT Working Group invite implementation of the following Candidate Recommendations:

• XML Path Language (XPath) 3.1: XPath 3.1 is an expression language that allows the processing of values conforming to the data model defined in XQuery and XPath Data Model (XDM) 3.1. The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values.
• XSLT and XQuery Serialization 3.1: This document defines serialization of an instance of the data model as defined in XQuery and XPath Data Model (XDM) 3.1 into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as XSL Transformations (XSLT) Version 3.0 or XQuery 3.1: An XML Query Language.

The XML Query Working Group invites implementation of the Candidate Recommendation of XQuery 3.1: An XML Query Language. XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources.

The Data on the Web Best Practices Working Group has published two Working Drafts:

• Data on the Web Best Practices: Data Quality Vocabulary: This document provides a framework in which the quality of a dataset can be described, whether by the dataset publisher or by a broader community of users. It does not provide a formal, complete definition of quality, rather, it sets out a consistent means by which information can be provided such that a potential user of a dataset can make his/her own judgment about its fitness for purpose.
• Data on the Web Best Practices: This document provides best practices related to the publication and usage of data on the Web designed to help support a self-sustaining ecosystem. Data should be discoverable and understandable by humans and machines. Where data is used in some way, whether by the originator of the data or by an external party, such usage should also be discoverable and the efforts of the data publisher recognized. In short, following these best practices will facilitate interaction between publishers and consumers.

The User Agent Accessibility Guidelines Working Group (UAWG) has published User Agent Accessibility Guidelines (UAAG 2.0) and UAAG 2.0 Reference as W3C Working Group Notes. UAAG 2.0 defines how browsers, extensions, media players, and other “user agents” should support accessibility for people with disabilities and work with assistive technologies. UAAG 2.0 is complete, and provides practical guidance for browsers and user agents. Implementations for UAAG 2.0 features have been identified, but not formally tested. Although W3C does not have plans at this time to advance UAAG 2.0 to Recommendation, the need and opportunity to improve accessibility in user agents still exists. UAAG 2.0 provides specific accessibility guidance for user agent developers who want to build a better user experience for all.

The Web Application Security Working Group has published two Working Drafts:

• Content Security Policy: Cookie Controls: This document defines mechanisms by which web developers can limit the ways in which cookies may be set in the context of their sites and applications.
• Content Security Policy: Embedded Enforcement: This document defines a mechanism by which a web page can embed a nested browsing context if and only if it agrees to enforce a particular set of restrictions upon itself.

The Cascading Style Sheets (CSS) Working Group invites implementation of the Candidate Recommendation of CSS Writing Modes Level 3. CSS Writing Modes Level 3 defines CSS features to support for various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts).