W3C published today the report of the W3C Workshop on Web5G: Aligning evolutions of network and Web technologies, which was held on 10-11 May 2018, in London.
The report contains a summary of each session with links to the
presentation slides. More detailed meeting minutes are also available.
Network Operators, vendors, application developers, content provider and
standard makers participated in this event which was designed to explore
how the Open Web Platform could help drive the adoption of 5G
innovations from the applications layer to the network level.
During the two days, participants reviewed opportunities that new
emerging innovations and capabilities at the application layers can
bring to the 5G network. The workshop concluded with the proposed creation of a task force of participants to explore how the 5G and Web communities might work in a productive and cohesive manner.
In particular, there was wide agreement on the benefit of developing
compelling business and technical reasons and objectives to incentivize
and drive a close collaboration among the W3C, 5G standard organizations
(e.g. 3GPP), browser vendors, developers, equipment vendors and network
operators. The goal is to create an environment conducive to the
development and deployment of technologies that are supported by all the
stakeholders in the ecosystem.
We thank our host, GSMA, and the Program Committee for making this event
W3C announced today a W3C Workshop on Permissions and User Consent, September 18-19, 2018, in San Diego, California, USA. The event is hosted by Qualcomm.
The primary goal of the workshop is to bring together security and privacy experts, UI/UX researchers, browser vendors, mobile OS developers, API authors, Web publishers and users to address the privacy, security and usability challenges presented by a complex and overlapping variety of permissions and consent systems available for hardware sensors, device capabilities and applications on the Web.
The scope includes:
- user consent;
- bundling of permissions;
- lifetime/duration of permissions;
- permission inheritance to iframes and other embedded elements;
- relation to same origin policy;
- UIs and controls;
- interaction with private browsing modes;
- implicit permission grants;
- progressive permission grants;
- cross-stack permissions: how OS, browser, and web app permissions interact;
- permission transparency;
- relation to regulatory requirements;
- special considerations for systems that use the browser as a pass-through
- permissions/transparency/UI as it relates to display-less devices that connect to the Internet.
For more information on the workshop, please see the workshop details and submission instructions. Expression of Interest and position statements are due by August 17, 2018.
The Web Payments Working Group invites implementations of an updated Candidate Recommendation of Payment Request API. This specification standardizes an API to allow merchants (i.e. web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. User agents (e.g., browsers) facilitate the payment flow between merchant and user.
The Web Performance Working Group invites implementations of User Timing Level 2 Candidate Recommendation. This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
The World Wide Web Consortium today launched the Internationalization Initiative to expand core work in further internationalizing the Web. “Supporting the W3C Internationalization Initiative with funding or expertise is a vital way that our Web community creates the future of the global Web,” said Jeff Jaffe, W3C CEO. W3C thanks Alibaba, Apple, Advanced Publishing Lab (Keio University), Monotype, and The Paciello Group who have stepped up as Founding Sponsors. Read about W3C Internationalization and its Sponsorship Program and the press release and testimonials.
A wide review Working Draft of Accessibility Conformance Testing (ACT) Rules Format was published today by the Accessibility Guidelines Working Group (AG WG). This draft addresses all comments received on the previous drafts. Most importantly, “Composed Rules” was introduced, in addition to “Atomic Rules”, to replace “Rule Groups”. This draft is accompanied by sample ACT Rules that implement this rules format. Read about the the Web Accessibility Initiative (WAI).
The Accessible Platform Architectures Working Group has published a Working Draft of a revision to Inaccessibility of CAPTCHA. Since the last publication, the abilities of robots to defeat CAPTCHAs has increased, and new technologies to authenticate human users have come available. This update brings the document up to date with these new realities. For more information, see the blog post Updated and extensively revised “Inaccessibility of CAPTCHA” Published. Read about the Accessible Platform Architectures Working Group and the Web Accessibility Initiative (WAI).
The Web Real-Time Communications Working Group invites implementations of Identifiers for WebRTC’s Statistics API Candidate Recommendation. This document defines a set of WebIDL objects that allow access to the statistical information about a RTCPeerConnection. These objects are returned from the getStats API that is specified in [WEBRTC].
The CSS Working Group invites implementations of an updated Candidate Recommendation of CSS Text Decoration Module Level 3. This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.
CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc.
The Web Real-Time Communications Working Group has published two First Public Working Drafts:
- WebRTC DSCP Control API: This API defines a control surface for manipulating the network control bits (DSCP bits) of outgoing WebRTC packets.
- MediaStreamTrack Content Hints: This specification extends
MediaStreamTrack to provide a
media-content hint attribute. This optional hint permits
MediaStreamTrack consumers such as PeerConnection (defined in [webrtc]) or MediaRecorder (defined in
[mediastream-recording]) to encode or process track media with methods more appropriate to the type of content that is being consumed. Adding a media-content hint provides a way for a web application to help track consumers make more informed decision of what encoder parameters and processing algorithms to use on the consumed content.