| |1. Postponed: W3C Workshop on Web & Machine LearningЧт, 13 фев[−]
2020-02-13 Update: Given the current challenges and restrictions around international travel, the Program Committee has made the decision to postpone the workshop to a later date.
W3C announced today a Workshop on Web & Machine Learning, 24-25 March 2020, in Berlin, Germany. The event is hosted by Microsoft.
The primary goal of the workshop is to bring together providers of Machine Learning tools and frameworks with Web platform practitioners to enrich the Open Web Platform with better foundations for machine learning.
The secondary goals of the workshop are as follows:
- Understand how machine learning fits into the Web technology stack,
- Understand how browser-based machine learning fits into the machine learning ecosystem,
- Explore the impact of machine learning technologies on Web browsers and Web applications,
- Evaluate the opportunities for standardization around machine learning APIs and formats.
Expected topics of discussion include:
- Dedicated machine learning APIs for browsers as explored by the Machine Learning for the Web Community Group
- Integration of browser-provided data sources in machine learning workflows
- Layering and interoperability of machine learning APIs with other computing APIs (e.g. WebGPU, WebAssembly)
- Domain-specific machine learning APIs
- Interchange format for machine learning models on the Web
- Client- and cloud-based machine learning interactions
- On-device machine learning training in browsers
- Risks and benefits of browser-based machine learning on privacy, security, accessibility
- Using machine learning primitives to help improve accessibility of Web pages and applications
- Machine learning frameworks for the Web
- Machine learning hardware accelerators
Attendance is free for all invited participants and is open to the public, whether or not W3C members. For more information on the workshop, please see the workshop details and submission instructions.
Registration is available online due by 21 February 2020.
|↑|3. Call for Review: Web of Things Architecture and Thing Description are W3C Proposed RecommendationsЧт, 13 фев[−]
The Web of Things Working Group has published two Proposed Recommendations:
WoT Architecture describes a formal model and a common representation for a WoT Thing Description. A Thing Description describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical or virtual entity that provides interactions to and participates in the Web of Things. Thing Descriptions provide a set of interactions based on a small vocabulary that makes it possible both to integrate diverse devices and to allow diverse applications to interoperate.
Comments are welcome through 27 February 2020.
|↑|6. Updated Candidate Recommendation: Timed Text Markup Language 2 (TTML2) (2nd Edition)Вт, 11 фев[−]
The Timed Text (TT) Working Group invites implementation of its updated Candidate Recommendation of Timed Text Markup Language 2 (TTML2) (2nd Edition). This document specifies the Second Edition of the Timed Text Markup Language (TTML), Version 2, also known as TTML2 (2e), in terms of a vocabulary and semantics thereof. The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information. It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy distribution content formats presently in use for subtitling and captioning functions.
Comments are welcome by 25 February 2020.
|↑|8. Trace Context is a W3C RecommendationЧт, 06 фев[−]
The Distributed Tracing Working Group has published Trace Context as a W3C Recommendation. This specification defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios. The specification standardizes how context information is sent and modified between services. Context information uniquely identifies individual requests in a distributed system and also defines a means to add and propagate provider-specific context information.
|↑|9. W3C Workshop Report: Inclusive Design for Immersive Web StandardsЧт, 06 фев[−]
W3C is pleased to announce a report from the W3C Workshop on Inclusive Design for Immersive Web Standards, held on 5-6 November 2019 in Seattle, WA, USA.
This report contains a brief summary and collects highlights from the
individual sessions, with links to the presentation slides. Workshop participants learned from existing approaches that have been
taken in making XR experiences (on and off the Web) accessible before
looking at what lessons could be derived from these existing research
and experiments in the context of the Immersive Web architecture.
These lessons brought forward four aspects of accessible XR experiences:
visual interactions, motricity considerations, audio aspects and
assistive technologies adaptation.
The relevant follow-up work in W3C spans across at least 6
standardization Working Groups and 6 pre-standardization and incubation
Community Groups, and also intersects with at least 3 Khronos Working
Groups – pointing toward the need for a strong coordination effort to
ensure systematic and consistent progress for the Web platform. We
propose to host this coordination in the Inclusive Design for the
Immersive Web Community Group via a dedicated github repository.
We thank our host, Pluto VR, Maveron, We Make Reality, Virtual World
Society and Seattle Immersive Technology Association, our sponsors,
Google, Twitch and Samsung Internet, the Program Committee, and all
participants for making this event possible.
|↑|12. W3C Advisory Committee Elects Technical Architecture GroupСр, 05 фев[−]
The W3C Advisory Committee has elected the following people to the W3C Technical Architecture Group (TAG): Rossen Atanassov (Microsoft Corporation), David Baron (Mozilla Foundation) and Kenneth Rohde Christiansen (Intel Corporation). They join co-Chair Tim Berners-Lee and continuing participants, Daniel Appelquist (Samsung Electronics; co-Chair), Hadley Beeman (W3C Invited Expert), Alice Boxhall (Google), Peter Linss (W3C Invited Expert; co-Chair), Sangwhan Moon (Odd Concepts), and Theresa O’Connor (Apple, Inc.). Yves Lafon continues as staff contact. Many thanks to Lukasz Olejnik (W3C Invited Expert) whose term ends at the end of this month.
The TAG is a special group within the W3C, chartered under the W3C Process Document, with stewardship of the Web architecture. 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. The elected Members of the TAG participate as individual contributors and not representatives of their organizations. TAG participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user. Learn more about the TAG.
|↑|14. First Public Working Drafts: Media Capabilities, Picture-in-Picture, Media Session StandardПт, 31 янв[−]
The Media Working Group has published First Public Working Drafts of three specifications that enhance media user experiences on the Web:
- Media Capabilities defines APIs to allow websites to make an optimal decision for decoding, encoding, and rendering when picking media content for the user.
- Picture-in-Picture allows websites to create a floating video window always on top of other windows so that users may continue consuming media while they interact with other content sites or applications on their device.
- The Media Session Standard enables web developers to show customized media metadata on platform UI, customize available platform media controls, and access platform media keys such as hardware keys found on keyboards, headsets, remote controls, and software keys found in notification areas and on lock screens of mobile devices.
|↑|15. W3C Recommends CSS Writing Modes to support International writing modesЧт, 23 янв[−]
The CSS Working Group has published CSS Writing Modes Level 3 as a W3C Recommendation.
This CSS module defines CSS support for various international writing modes and their combinations, including left-to-right and right-to-left text ordering as well as horizontal and vertical orientations. These new CSS features allow a mixture of horizontal and vertical text regions on the same page. The specification also adds support for such things as isolation in bidirectional text, glyph orientation controls, and short, inline horizontal runs in lines of vertical text.
Please, read our press release for additional information and acknowledgements.
|↑|16. W3C Recommends WebAssembly to push the limits for speed, efficiency and responsivenessЧт, 23 янв[−]
The WebAssembly Working Group has published today the three WebAssembly specifications as W3C Recommendations, marking the arrival of a new language for the Web which allows code to run in the browser.
- WebAssembly Core Specification defines a low-level virtual machine which closely mimicks the functionality of many microprocessors upon which it is run. Either through Just-In-Time compilation or interpretation, the WebAssembly engine can perform at nearly the speed of code compiled for a native platform. A .wasm resource is analogous to a Java .class file in that it contains static data and code segments which operate over that static data. Unlike Java, WebAssembly is typically produced as a compilation target from other programming languages like C/C++ and Rust.
- WebAssembly Web API defines a Promise-based interface for requesting and executing a .wasm resource. The structure of a .wasm resource is optimized to allow execution to begin before the entire resource has been retrieved, which further enhances responsiveness of WebAssembly applications.
WebAssembly provides a safe, portable, low-level code format designed for efficient execution and compact representation. This technology enables the Web platform to perform more efficient execution of computationally-intensive algorithms, which in turn makes it practical to deliver whole new classes of user experience on the Web and elsewhere. Because WebAssembly is a platform-independent execution environment, it can also be used on any other computer platform. Please, read our press release for additional information and acknowledgements.
|↑|17. W3Cx Introduction to Web Accessibility – New Online CourseЧт, 23 янв[−]
On the International Day of Persons with Disabilities, W3C and the UNESCO Institute for Information Technologies in Education (UNESCO IITE) launched a new W3Cx course: “ Introduction to Web Accessibility“.
The course is designed for technical and non-technical audiences, including developers, designers, content authors, project managers, people with disabilities, and others. The course will start on 28 January 2020 and is self-paced.
Please, read our press release and blog post, and watch our short teaser video for more information about the course. Enroll now, and encourage others to, too.
|↑|18. W3C Invites Implementations of JSON-LD 1.1Вт, 14 янв[−]
The JSON-LD Working Group invites implementations of three Candidate Recommendations:
- JSON-LD 1.1 defines a JSON-based expression of Linked Data graphs. The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD. It enables the creation of more easily interoperable Web services, the ability to store Linked Data in JSON-based storage engines, and brings more meaningful data to Web services and APIs.
- JSON-LD 1.1 Processing Algorithms and API defines an Application Programming Interface (API) for developers implementing a set of algorithms for programmatic transformations of JSON-LD documents.
- JSON-LD 1.1 Framing allows developers to query a JSON-LD document’s contained graph, by example, and reshape output into a specific JSON tree layout.
Candidate Recommendation means that the Working Group considers the technical design to be complete and is seeking implementation feedback on the documents. The group is keen to get comments and implementation experiences on these specifications as issues raised in the documents’ respective GitHub repositories (see the document headers for the exact references).
The group expects to satisfy the implementation goals (i.e., at least two, independent implementations for each of the test cases) by 17 February 2020.
|↑|19. W3C Invites Implementations of the Sensor APIsВт, 14 янв[−]
The Devices and Sensors Working Group invites implementations of four Candidate Recommendations:
- Generic Sensor API defines a framework for exposing sensor data to the Open Web Platform in a consistent way. It does so by defining a blueprint for writing specifications of concrete sensors along with an abstract Sensor interface that can be extended to accommodate different sensor types.
- Accelerometer defines
GravitySensor interfaces for obtaining information about acceleration applied to the X, Y and Z axis of a device that hosts the sensor.
- Gyroscope defines a concrete sensor interface to monitor the rate of rotation around the device’s local three primary axes.
- Orientation Sensor defines a base orientation sensor interface and concrete sensor subclasses to monitor the device’s physical orientation in relation to a stationary three dimensional Cartesian coordinate system.
Comments are welcome by 8 January 2020.
|↑|21. Updated Candidate Recommendation for the Web Real-Time Communication 1.0 APIВт, 14 янв[−]
The WebRTC Working
Group invites implementation of its updated Candidate Recommendation
of WebRTC 1.0: Real-time Communication Between Browsers specification.
The WebRTC API enables browsers to establish real-time audio, video
and data transmission between browsers and other peers.
Since its previous publication as a Candidate Recommendation, the
Working Group has resolved all its substantive issues, ensuring better
alignment between the specification and its implementations, improving
and clarifying support for “simulcast” transmission and built better
support against possible race conditions when peers set up their
Comments are welcome by January 12 2020.
|↑|22. Happy holidays from the World Wide Web Consortium!Пн, 13 янв[−]
Many thanks for all the ways you have made the Web work for everyone in 2019,
and for all the work we will accomplish together in 2020.
W3C wishes you a happy holiday season
and all the best for the new year!
From all of us at the World Wide Web Consortium.
|↑|23. First Public Working Draft: Pointer Events Level 3Вт, 17 дек 2019[−]
The Pointer Events Working Group has published a First Public Working Draft of Pointer Events Level 3. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware agnostic pointer input from devices including a mouse, pen, touchscreen, etc. For compatibility with existing mouse based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.
|↑|24. W3C Invites Implementations of Publication Manifest and AudiobooksПн, 16 дек 2019[−]
The Publishing Working Group has just published a Candidate Recommendation for two documents, namely:
- Publication Manifest – This specification defines a general manifest format for expressing information about a digital publication. It uses schema.org metadata augmented to include various structural properties about publications, serialized in JSON-LD, to enable interoperability between publishing formats while accommodating variances in the information that needs to be expressed.
- Audiobooks – This specification describes the requirements for the creation of audiobooks, using a profile of the Publication Manifest specification.
The Group has also published an accompanying Working Group Note of Lightweight Packaging Format (LPF). This specification defines a file format and processing model for packaging into a single-file container the set of related resources and associated metadata that comprise a digital publication.
Candidate Recommendation means that the Working Group considers the technical design to be complete, and is seeking implementation feedback on the documents. The group is keen to get comments and implementation experiences on these specifications as issues raised in the the documents’ respective GitHub repositories (see the document headers for the exact references).
The group expects to satisfy the implementation goals (i.e., at least two, independent implementations for each of the test cases) by 31 March 2020.