W3C News

First Public Working Draft: Intersection Observer

The Web Platform Working Group has published a First Public Working Draft of Intersection Observer. This specification describes an API that can be used to understand the visibility and position of DOM elements (“targets”) relative to a containing element or to the top-level viewport (“root”). The position is delivered asynchronously and is useful for understanding the visibility of elements and implementing pre-loading and deferred loading of DOM content.

Accessibility Conformance Testing (ACT) Rules Format 1.0 Working Draft Updated

An updated Working Draft of Accessibility Conformance Testing (ACT) Rules Format 1.0 was published today by the Accessibility Guidelines Working Group (AG WG). This draft addresses all comments received on the previous draft, and is accompanied by fully- and semi-automated sample ACT Rules that implement this rules format. Learn more from the ACT Rules Format call for review email and read about the the Web Accessibility Initiative (WAI).

Update to the Candidate Recommendation: ActivityPub

The Social Web Working Group invites implementations of an updated Candidate Recommendation of ActivityPub. The ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content. The two normative changes are to improve compatibility with the Mastodon federated social network implementation, in response to feedback from Mastodon developers.

First Public Working Drafts: Paint Timing 1; Long Tasks API 1

The Web Performance Working Group has published two First Public Working Drafts today:

Paint Timing 1: This document defines an API that can be used to capture a series of key moments (First Paint, First Contentful Paint) during pageload which developers care about.

Long Tasks API 1: This document defines an API that web page authors can use to detect presence of “long tasks” that monopolize the UI thread for extended periods of time and block other critical tasks from being executed – e.g. reacting to user input.

Call for Review: Semantic Sensor Network Ontology Proposed Recommendation Published

Relationship between SOSA and SSN ontologies and their vertical and horizontal modulesThe Spatial Data on the Web Working Group has published a Proposed Recommendation of the Semantic Sensor Network Ontology specification. The specification defines an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators.

SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Comments are welcome through 5 October 2017.

Call for Review: Time Ontology in OWL Proposed Recommendation Published

Thirteen elementary possible relations between time periodsThe Spatial Data on the Web Working Group has published a Proposed Recommendation of the Time Ontology in OWL specification. 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. Comments are welcome through 5 October 2017.

W3C Invites Implementations of Media Queries Level 4

The CSS Working Group invites implementations of Media Queries Level 4 Candidate Recommendation. Media Queries allow authors to test and query values or features of the user agent or display device, independent of the document being rendered. They are used in the CSS @media rule to conditionally apply styles to a document, and in various other contexts and languages, such as HTML and Javascript.

Media Queries Level 4 describes the mechanism and syntax of media queries, media types, and media features. It extends and supersedes the features defined in Media Queries Level 3.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc.

Update to the Candidate Recommendation ‘CSS Scroll Snap Module Level 1’

The CSS Working Group invites implementations of an updated Candidate Recommendation of CSS Scroll Snap Module Level 1. The CSS Scroll Snap Module contains features to control panning and scrolling behavior with ‘snap positions’. After feedback on the specification that was published in February, the CSS Working Group decided to update the document. The normative change is small (the group had forgotten to forbid negative values for one of the properties), but the update is also an opportunity to clarify some text and improve the examples.

Proposal to Republish Previous Versions of HTML and XHTML as Obsolete Recommendations

HTML5 logoW3C Advisory Committee Representatives received today a proposal to republish a series of HTML and XHTML W3C Recommendations as Obsolete Recommendations, in response to a request from the Web Platform Working Group as these specifications are superseded by new versions and are no longer recommended for implementation on the Web platform.

This has been made possible by the addition this year to the W3C Process Document of a process to mark a Recommendation as Obsolete. An obsolete specification is one that the W3C community has decided should no longer be used. For example, it may no longer represent best practices, or it may not have received wide adoption and is not apparently likely to be adopted in the future. The status of an obsolete specification remains active under the W3C Patent Policy, but it is not recommended for future implementation. In this case, “obsolete” states that each of these specifications has been superseded by more recent specifications.

For example, as part of our commitment to the platform’s future, we recommend that all implementers use the latest HTML5 –where HTML5 is the term to refer to the family of specifications. We are proposing to obsolete the particular 28 October 2014 W3C Recommendation which henceforth shall be called HTML 5.0, which has been superseded by HTML 5.1, a W3C Recommendation since 1 November 2016. This aims at clarifying the status of the document and point developers and implementers to the latest version of HTML5.