The RDF Data Shapes Working Group has published a Proposed Recommendation of Shapes Constraint Language (SHACL). This document defines the SHACL Shapes Constraint Language, a language for validating RDF graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph. RDF graphs that are used in this manner are called “shapes graphs” in SHACL and the RDF graphs that are validated against a shapes graph are called “data graphs”. Such descriptions may be used for a variety of purposes beside validation, including user interface building, code generation and data integration. Comments are welcome through 6 July 2017.
The Education and Outreach Working Group (EOWG) has updated the Web Accessibility Laws and Policies list. It now includes an overview table with sort-able columns and filters, such as for W3C’s Web Content Accessibility Guidelines (WCAG). Additional information is available in the Web Accessibility Laws and Policies Listing Updated e-mail. Learn more about the Web Accessibility Initiative (WAI).
W3C made public its W3C Strategic Highlights – Spring 2017, a comprehensive survey of select recent work. The Web has grown to be the technical infrastructure of Society –the universal connectivity platform. It continues to change business and society, and just as business and society evolve, new needs arise, new opportunities for more captivating experiences need addressing. The Web needs scaling to the opportunity and an organization focused on addressing opportunities. From everyday needs of Web users, to Industry impact, W3C’s vision has four areas of excellence: Strengthening the core of the Web, exciting with the next level experiences, extending the reach of the Web, and meeting Industry needs. This report, was prepared for discussion during the Spring W3C Advisory Committee Meeting. Read W3C CEO Jeff Jaffe’s perspectives on this meeting and W3C’s Vision on our Blog.
The W3C Advisory Committee has filled four open seats on the W3C Advisory Board. Created in 1998, the Advisory Board provides guidance to the Team on issues of strategy, management, legal matters, process, and conflict resolution. Beginning 1 July 2017, the nine Advisory Board participants are Tantek Çelik (Mozilla), Michael Champion (Microsoft), Virginie Galindo (Gemalto), Jay (Junichi) Kishigami (NTT), Charles McCathie Nevile (Yandex), Natasha Rooney (GSMA), David Singer (Apple), Léonie Watson (The Paciello Group) and Judy Zhu (Alibaba). Many thanks to Chris Wilson (Google), whose term ends this month. Read more about the Advisory Board.
Digital Publishing Accessibility API Mappings (DPub-AAM) has been published as a Candidate Recommendation by Accessible Rich Internet Applications (ARIA) Working Group and is now undergoing implementation finalization and testing. DPub-AAM describes how roles in the Digital Publishing WAI-ARIA Module 1.0 should be exposed to accessibility APIs. Implementation of this specification makes it possible for assistive technologies to provide enhanced navigation among landmarks unique to digitally-published documents, and to identify document-specific features which should be presented to the user, such as crossing a page boundary. These mappings will also be used in part for verifying implementation success of Digital Publishing WAI-ARIA Module 1.0 which is already a Candidate Recommendation. The draft implementation report shows the progress of testing. Please send implementation information or comments by 7 July 2017. Read about the Web Accessibility Initiative (WAI).
The Accessible Rich Internet Applications (ARIA) Working Group has published a First Public Working Draft of Personalization Semantics 1.0. Personalization involves tailoring aspects of the user experience to meet the needs and prefences of the user. The introduction of standardized semantics allows web applications to customize the exposure of that content to one that is familiar to individuals based on their needs and preferences. This specification was initially developed in a task force to provide technology features needed to meet needs of users with cognitive or learning disabilities, but is intended to support a wide variety of personalization use cases. Please comment by filing GitHub issues in the personalization semantics repository or, if this is not feasible, by email to firstname.lastname@example.org, by 30 June 2017. Read about the Accessible Rich Internet Applications Working Group and the Web Accessibility Initiative (WAI).
The Spatial Data on the Web Working Group invites implementations of Time Ontology in OWL Candidate Recommendation. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars.
The Second Screen Working Group has published a revised Candidate Recommendation of the Presentation API. That specification defines an API to enable Web content to access presentation displays and use them for presenting Web content.
Since publication as Candidate Recommendation in July 2016, the Working Group updated algorithms in the specification to fix issues identified through testing and implementation feedback. The actual interfaces did not change. The API was also restricted to secure contexts. A complete list of changes is available.
The Web Platform Working Group invites implementation of UI Events KeyboardEvent code and key Values:
- UI Events KeyboardEvent code Values: This document provides an overview of the various keyboard layouts and specifies the KeyboardEvent.code values that should be used for each of the keys. Unlike the key values described in UIEvents-key, the code values are based only on the key’s physical location on the keyboard and do not vary based on the user’s current locale. This specification was formerly titled DOM Level 3 KeyboardEvent code Values.
- UI Events KeyboardEvent key Values: This document specifies the set of valid key attribute values that must be used in the KeyboardEvent.key attribute to encode the key’s meaning. The key value for a particular key will differ based on the user’s current locale setting.
The Social Web Working Group has published a W3C Recommendation of Micropub. Micropub is a client-to-server protocol used to create, update and delete social networking content. Web and native apps can use Micropub to post notes, photos, events, and many others to servers that support the protocol. Users can choose to create content in a variety of client posting interfaces, while maintaining control of where the data is stored.
Prior to being adopted by the W3C Social Web Working Group for standardization, Micropub already had over a dozen independent implementations in the IndieWeb community. There are now over a dozen independent client and server implementations across a wide variety of languages and platforms.