The W3C Advisory Committee has elected the following people to the W3C Technical Architecture Group (TAG): David Baron (Mozilla) and Andrew Betts (Financial Times / Nikkei). They join co-Chair Tim Berners-Lee and continuing participants Travis Leithead (Microsoft), Mark Nottingham (Akamai), Alex Russell (Google), Hadley Beeman (W3C Invited Expert), Daniel Appelquist (W3C Invited Expert; co-Chair), Peter Linss (HP; co-Chair) –both re-appointed by the Director. Yves Lafon continues as staff contact. W3C thanks to Yan Zhu (formerly of Yahoo!) whose term ends this month, for her contributions. The mission 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. Learn more about the TAG.
We are pleased to announce that we upgraded today our servers to support both HTTP and HTTPS access to public resources. W3C advocates that the Web platform “actively prefer secure communication.” Thanks to recent work in the Web Application Security Working Group and supporting client implementations, and the deployment work of the W3C Systems Team, we are now able to provide HTTPS access to all W3C resources. All W3C documents, including Recommendations, DTDs, and vocabularies will be available with the authentication,
integrity-protection, and confidentiality HTTPS supports.
Read about what the change involves, the challenges and some side-effects in the detailed post on the W3C Blog.
W3C is delighted to be the recipient of a 2016 Technology & Engineering Emmy ® Award from the National Academy of Television Arts & Sciences for its work on the Timed Text Mark-up Language standard that makes video content more accessible with text captioning and subtitles. Representatives from W3C staff and the Timed Text Working Group will attend the awards ceremony on 8 January at the Bellagio Hotel in Las Vegas during the Consumer Electronics Show (CES).
“W3C is thrilled to receive a 2016 Emmy ® Award in recognition of technologies that support an important part of our mission to bring the full potential of the World Wide Web to everyone, whatever their disability, culture, language, device or network infrastructure,” said W3C CEO Dr. Jeff Jaffe. “I would like to thank the National Academy of Television Arts & Sciences for their recognition of W3C, and I congratulate the members of the W3C Timed Text Working Group and the W3C Web Accessibility Initiative on this outstanding achievement.”
For more information about the Emmy ® Award and TTML, see the press release.
The Web Content Accessibility Guidelines Working Group has published a First Public Working Draft of Requirements for WCAG 2.0 Extensions. This document describes the requirements that the WCAG WG is setting for the development of WCAG 2.0 extensions. Extensions are optional standards modules that build on the existing requirements for WCAG 2.0, and are designed to work in harmony with the WCAG 2.0 standard. Learn more from the call for review e-mail and “Shaping the WCAG 2.0 extensions” blog post and read about the Web Accessibility Initiative (WAI).
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 CSV on the Web Working Group has published four Recommendations:
The group plans to publish a Primer at a later time to help users using these technologies.
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.