Subscribe: W3C News
http://www.w3.org/2000/08/w3c-synd/home.rss
Preview: W3C News

W3C News



Leading the Web to its Full Potential



Updated: 2017-10-19T13:36:18Z

 



Time Ontology in OWL is a W3C Recommendation

2017-10-19T13:07:36Z

The Spatial Data on the Web Working Group has published a W3C 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 […]

(image) The Spatial Data on the Web Working Group has published a W3C 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.




Semantic Sensor Network Ontology is a W3C Recommendation

2017-10-19T13:04:56Z

The Spatial Data on the Web Working Group has published a W3C Recommendation of the Semantic Sensor Network Ontology. 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 […]

(image) The Spatial Data on the Web Working Group has published a W3C Recommendation of the Semantic Sensor Network Ontology. 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.




W3C Invites Implementations of Remote Playback API

2017-10-19T13:12:40Z

The Second Screen Working Group invites implementations of the Remote Playback API Candidate Recommendation. The specification defines an API extending the HTMLMediaElement interface of HTML that enables controlling remote playback of media from a web page.

(image) The Second Screen Working Group invites implementations of the Remote Playback API Candidate Recommendation. The specification defines an API extending the HTMLMediaElement interface of HTML that enables controlling remote playback of media from a web page.




W3C Invites Implementations of Tracking Preference Expression (DNT)

2017-10-19T12:56:27Z

The Tracking Protection Working Group invites implementations of an updated Candidate Recommendation of Tracking Preference Expression (DNT). This specification defines the DNT request header field as an HTTP mechanism for expressing a user’s preference regarding tracking, an HTML DOM property to make that expression readable by scripts, and APIs that allow scripts to register exceptions granted […]

The Tracking Protection Working Group invites implementations of an updated Candidate Recommendation of Tracking Preference Expression (DNT). This specification defines the DNT request header field as an HTTP mechanism for expressing a user’s preference regarding tracking, an HTML DOM property to make that expression readable by scripts, and APIs that allow scripts to register exceptions granted by the user. It also defines mechanisms for sites to communicate whether and how they honor a received preference, including well-known resources for retrieving preflight tracking status, a media type for representing tracking status information, and the Tk response header field for confirming tracking status.




W3C Invites Implementations of CSS Flexible Box Layout Module Level 1

2017-10-19T12:44:40Z

The CSS Working Group invites implementations of an updated Candidate Recommendation of CSS Flexible Box Layout Module Level 1. The specification describes a CSS box model optimized for user interface design. In the flex layout model, the children of a flex container can be laid out in any direction, and can “flex” their sizes, either growing […]

The CSS Working Group invites implementations of an updated Candidate Recommendation of CSS Flexible Box Layout Module Level 1. The specification describes a CSS box model optimized for user interface design. In the flex layout model, the children of a flex container can be laid out in any direction, and can “flex” their sizes, either growing to fill unused space or shrinking to avoid overflowing the parent. Both horizontal and vertical alignment of the children can be easily manipulated. Nesting of these boxes (horizontal inside vertical, or vertical inside horizontal) can be used to build layouts in two dimensions.

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




Call for Review: Page Visibility Level 2 is a W3C Proposed Recommendation

2017-10-19T13:34:34Z

The Web Performance Working Group has published a Proposed Recommendation of Page Visibility Level 2. This specification defines a means to programmatically determine the visibility state of a document. This can aid in the development of resource efficient web applications. Page Visibility Level 2 replaces the first version of Page Visibility and includes a few […]

The Web Performance Working Group has published a Proposed Recommendation of Page Visibility Level 2. This specification defines a means to programmatically determine the visibility state of a document. This can aid in the development of resource efficient web applications. Page Visibility Level 2 replaces the first version of Page Visibility and includes a few Processing and IDL clarifications, as well as some new features. Comments are welcome through 14 November 2017.




W3C Invites Implementations of CSS Backgrounds and Borders Module Level 3

2017-10-19T13:36:18Z

The CSS Working Group invites implementations of an updated Candidate Recommendation of CSS Backgrounds and Borders Module Level 3. This draft contains the features of CSS relating to borders and backgrounds. The main extensions compared to level 2 are borders consisting of images, boxes with multiple backgrounds, boxes with rounded corners and boxes with shadows. […]

The CSS Working Group invites implementations of an updated Candidate Recommendation of CSS Backgrounds and Borders Module Level 3. This draft contains the features of CSS relating to borders and backgrounds. The main extensions compared to level 2 are borders consisting of images, boxes with multiple backgrounds, boxes with rounded corners and boxes with shadows.

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




First Public Working Draft: TTML Profiles for Internet Media Subtitles and Captions 1.1

2017-10-17T08:07:34Z

The Timed Text Working Group has published a First Public Working Draft of TTML Profiles for Internet Media Subtitles and Captions 1.1. This specification defines two profiles of [TTML2]: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering […]

The Timed Text Working Group has published a First Public Working Draft of TTML Profiles for Internet Media Subtitles and Captions 1.1. This specification defines two profiles of [TTML2]: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.




Call for Review: Cooperative Scheduling of Background Tasks is a W3C Proposed Recommendation

2017-10-19T13:31:09Z

The Web Performance Working Group has published a Proposed Recommendation of Cooperative Scheduling of Background Tasks. This document defines an API that web page authors can use to cooperatively schedule background tasks such that they do not introduce delays to other high priority tasks that share the same event loop, such as input processing, animations […]

The Web Performance Working Group has published a Proposed Recommendation of Cooperative Scheduling of Background Tasks. This document defines an API that web page authors can use to cooperatively schedule background tasks such that they do not introduce delays to other high priority tasks that share the same event loop, such as input processing, animations and frame compositing. The user agent is in a better position to determine when background tasks can be run without introducing user-perceptible delays or jank in animations and input response, based on its knowledge of currently scheduled tasks, vsync deadlines, user-interaction and so on. Using this API should therefore result in more appropriate scheduling of background tasks during times when the browser would otherwise be idle. Comments are welcome through 7 November 2017.




Call for Review: WebSub is a W3C Proposed Recommendation

2017-10-19T13:16:35Z

The Social Web Working Group has published a Proposed Recommendation of WebSub. This document provides a common mechanism for communication between publishers of any kind of Web content and their subscribers, based on HTTP web hooks. Subscription requests are relayed through hubs, which validate and verify the request. Hubs then distribute new and updated content […]

The Social Web Working Group has published a Proposed Recommendation of WebSub. This document provides a common mechanism for communication between publishers of any kind of Web content and their subscribers, based on HTTP web hooks. Subscription requests are relayed through hubs, which validate and verify the request. Hubs then distribute new and updated content to subscribers when it becomes available. WebSub was previously known as PubSubHubbub. Comments are welcome through 3 November 2017.




HTML 5.1 2nd Edition is a W3C Recommendation

2017-10-19T13:17:46Z

The Web Platform Working Group has published a W3C Recommendation of HTML 5.1 2nd Edition. This specification defines the 2nd edition of the 5th major version, first minor revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, a significant error with HTML 5.1 has been rectified, […]

(image) The Web Platform Working Group has published a W3C Recommendation of HTML 5.1 2nd Edition. This specification defines the 2nd edition of the 5th major version, first minor revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, a significant error with HTML 5.1 has been rectified, as noted in the Errata corrected section. Meanwhile, new features continue to be introduced to help Web application authors, new elements continue to be introduced based on research into prevailing authoring practices, and special attention continues to be given to defining clear conformance criteria for user agents in an effort to improve interoperability in the development of HTML 5.2.




W3C Invites Implementations of Audio Output Devices API; Capture and Streams

2017-10-19T13:14:40Z

The Web Real-Time Communications Working Group invites implementations of the following Candidate Recommendations: Audio Output Devices API, which defines a set of JavaScript APIs that let a Web application manage how audio is rendered on the user audio output devices. Media Capture and Streams (revised Candidate Recommendation), which defines a set of JavaScript APIs that […]

The Web Real-Time Communications Working Group invites implementations of the following Candidate Recommendations:




Industry Experts to Share Business Insights at W3C’s First Executive Forum, 8 November in San Francisco

2017-09-26T12:10:32Z

Executives from Alipay, American Express, Bloomberg, HARMAN, Google, Intel, Mozilla, Samsung, Southern Nevada Regional Transportation Agency, University of Sydney, Worldpay and Yubico, together with Web Inventor and W3C Director Sir Tim Berners-Lee, will address emerging tech trends and the impact of the Web on business and industry at the World Wide Web Consortium’s (W3C) inaugural […]

(image) Executives from Alipay, American Express, Bloomberg, HARMAN, Google, Intel, Mozilla, Samsung, Southern Nevada Regional Transportation Agency, University of Sydney, Worldpay and Yubico, together with Web Inventor and W3C Director Sir Tim Berners-Lee, will address emerging tech trends and the impact of the Web on business and industry at the World Wide Web Consortium’s (W3C) inaugural Web Executive Forum.

Web application areas are revolutionizing many business models in Digital Publishing, FinTech, Automotive, Telco, Smart Manufacturing and Entertainment. W3C has created an event designed to provide value and insight to executives across a wide range of industries with a goal of providing rich content and some food for thought,” said J. Alan Bird, W3C Global Business Development Leader.

Registration for the W3C Executive Forum is open to the public. More information is available in the media advisory.




W3C Invites Implementations of ODRL Information Model; ODRL Vocabulary & Expression

2017-10-17T08:18:25Z

The Permissions & Obligations Expression Working Group has just published two Candidate Recommendations, namely: ODRL Information Model—The Open Digital Rights Language (ODRL) is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. The ODRL Information Model describes the […]

The Permissions & Obligations Expression Working Group has just published two Candidate Recommendations, namely:

  • ODRL Information Model—The Open Digital Rights Language (ODRL) is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. The ODRL Information Model describes the underlying concepts, entities, and relationships that form the foundational basis for the semantics of the ODRL policies. Policies are used to represent permitted and prohibited actions over a certain asset, as well as the obligations required to be meet by stakeholders. In addition, policies may be limited by constraints (e.g., temporal or spatial constraints) and duties (e.g. payments) may be imposed on permissions.
  • ODRL Vocabulary & Expression—The ODRL Vocabulary and Expression describes the terms used in ODRL policies and how to encode them.

Candidate Recommendation means that the Working Group considers the technical design to be complete, and is seeking implementation feedbacks on the documents. There is a separate document how to use them and report on implementation results. The group welcomes feedback by email to its public mailing list public-poe-comments@w3.org or as issues raised in the issues on the Group’s GitHub repository

The group expects to satisfy the implementation goals (i.e., at least two, independent implementation for each of the test cases) by November 14, 2017.




Upcoming Workshop: WebVR Authoring: Opportunities and Challenges

2017-09-26T11:36:21Z

W3C announced today WebVR Authoring: Opportunities and Challenges Workshop, 5-7 December 2017, in Brussels, Belgium. The event is hosted by DigitYser. The primary goal of the workshop is to bring together WebVR stakeholders to identify unexploited opportunities as well as technical gaps in WebVR authoring. Participants in the workshop will: Share good practices and novel […]

W3C announced today WebVR Authoring: Opportunities and Challenges Workshop, 5-7 December 2017, in Brussels, Belgium. The event is hosted by DigitYser.

The primary goal of the workshop is to bring together WebVR stakeholders to identify unexploited opportunities as well as technical gaps in WebVR authoring.

Participants in the workshop will:

  • Share good practices and novel techniques in creating WebVR-based content
  • Discuss existing and foreseen challenges in using WebVR to deploy content and services in specific usages
  • Contribute to the unification of efforts for documenting and advocating the development of WebVR content

Attendance is free for all invited participants and is open to the public, whether or not W3C members. Our aim is to get a diversity of attendees from a variety of industries and communities, including:

  • 360° video and VR content producers and distributors
  • VR experience designers and artists
  • 3D, VR and WebVR authoring tools and platforms
  • authors of WebVR content
  • experts in challenges and opportunities of VR for people with disabilities
  • browser vendors

Expected topics of discussion include:

  • Landscape of WebVR authoring tools
  • Creating and packaging 3D assets for WebVR
  • Managing assets for practical progressive enhancement
  • Progressive enhancement applied to the variety of user input in WebVR
  • Understanding and documenting WebVR constraints for 3D artists
  • Optimizing delivery of 360° videos to VR headsets on the Web
  • Practical approaches to building accessible WebVR experiences
  • Mapping the impact of ongoing evolutions of the Web Platform (Web Assembly, WebGPU, streams) on WebVR authoring
  • Impact of performance factors on authoring WebVR content
  • Creating convergence on WebVR advocacy platforms

For more on the workshop, please see the workshop details and submission instructions.

Registration is available online due by 10 November 2017.




W3C Invites Implementations of Core Accessibility API Mappings 1.1

2017-10-10T09:20:20Z

Core Accessibility API Mappings (Core-AAM) 1.1 has been published by Accessible Rich Internet Applications (ARIA) Working Group as a Candidate Recommendation and is now undergoing implementation finalization and testing. Core-AAM describes how roles, states, and properties in Accessible Rich Internet Applications (WAI-ARIA) 1.1 should be exposed to accessibility APIs. Implementation of this specification makes it […]

Core Accessibility API Mappings (Core-AAM) 1.1 has been published by Accessible Rich Internet Applications (ARIA) Working Group as a Candidate Recommendation and is now undergoing implementation finalization and testing. Core-AAM describes how roles, states, and properties in Accessible Rich Internet Applications (WAI-ARIA) 1.1 should be exposed to accessibility APIs. Implementation of this specification makes it possible for users with disabilities to obtain and interact with information using assistive technologies. These mappings will also be used in part for verifying implementation success of WAI-ARIA 1.1 which is already a Candidate Recommendation. The draft implementation report shows the progress of testing. Please send implementation information or comments by 19 October 2017. Read about the Web Accessibility Initiative (WAI).




Encrypted Media Extensions (EME) is a W3C Recommendation

2017-10-03T08:01:07Z

The HTML Media Extensions Working Group published Encrypted Media Extensions (EME) as a W3C Recommendation today. Encrypted Media Extensions (EME), which extends the ‘HTMLMediaElement’ element of the HTML specification, is an Application Programming Interface (API) that allows playback of protected content in Web browsers. Combined with W3C’s Recommendation Media Source Extensions (MSE) which provides the […]

(image) The HTML Media Extensions Working Group published Encrypted Media Extensions (EME) as a W3C Recommendation today. Encrypted Media Extensions (EME), which extends the ‘HTMLMediaElement’ element of the HTML specification, is an Application Programming Interface (API) that allows playback of protected content in Web browsers. Combined with W3C’s Recommendation Media Source Extensions (MSE) which provides the API for streaming video, EME is the most common practice today that allows Web developers to stop using plugins to deliver commercial quality video over the Web. Please read more in our Press Release.




Web Commerce Interest Group Rechartered with New Mission

2017-10-10T09:20:09Z

W3C has just rechartered the Web Commerce Interest Group to improve Commerce on the Web for users, merchants, and other stakeholders. This charter represents the next iteration of the Web Payments Interest Group. Changes to the charter reflect the broader scope of Interest Group discussions that have been taking place over the past year, including […]

W3C has just rechartered the Web Commerce Interest Group to improve Commerce on the Web for users, merchants, and other stakeholders. This charter represents the next iteration of the Web Payments Interest Group. Changes to the charter reflect the broader scope of Interest Group discussions that have been taking place over the past year, including topics such as:

  • digital offers (coupons, loyalty, etc.)
  • payments from a variety of devices, including mobile devices, automobiles (in-car payments), televisions, virtual reality, and Internet of Things devices
  • various aspects of payment flow, including initiation of payment, recurring payments, receipts, and refunds
  • emerging regulations
  • fraud reduction
  • harmonization with other standards

Learn more about Web Commerce at W3C.




First Public Working Drafts: WoT Architecture; WoT Thing Description; WoT Scripting API

2017-10-10T09:20:03Z

The Web of Things (WoT) Working Group has published the following three First Public Working Drafts: Web of Things (WoT) Architecture: This document describes the abstract architecture for the W3C Web of Things, which consists of three initial building blocks, i.e., (1) WoT Thing Description, (2) WoT Scripting API and (3) WoT Binding Templates. Web […]

The Web of Things (WoT) Working Group has published the following three First Public Working Drafts:

Web of Things (WoT) Architecture: This document describes the abstract architecture for the W3C Web of Things, which consists of three initial building blocks, i.e., (1) WoT Thing Description, (2) WoT Scripting API and (3) WoT Binding Templates.

Web of Things (WoT) Thing Description: This document describes a formal model and common representation for a Web of Things Thing Description. A Thing Description describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical entity that provides interactions to and participates in the Web of Things.

Web of Things (WoT) Scripting API: This document describes a programming interface representing the WoT Interface that allows scripts run on a Thing to discover and consume (retrieve) other Things and to expose Things characterized by Properties, Actions and Events.

The group is planning to publish the third building block, WoT Binding Templates, as a First Public Working Draft shortly.




W3C Invites Implementations of Payment Request API; Payment Method Identifiers

2017-10-03T08:27:00Z

The World Wide Web Consortium (W3C) today called for broad implementation and testing of Web technologies to make online checkout easier for users and improve conversions and security for merchants. All major browser makers are now implementing Payment Request API and Payment Method Identifiers, which today advanced to Candidate Recommendation Status. The Web Payments Working Group encourages […]

The World Wide Web Consortium (W3C) today called for broad implementation and testing of Web technologies to make online checkout easier for users and improve conversions and security for merchants. All major browser makers are now implementing Payment Request API and Payment Method Identifiers, which today advanced to Candidate Recommendation Status. The Web Payments Working Group encourages merchants, Web developers, and users to experiment with these early implementations and provide feedback to the group. In parallel, the Working Group will be expanding its test suite for the API to help ensure browser interoperability. Read more in the W3C Media Advisory and blog post.




First Public Working Draft: Intersection Observer

2017-10-03T07:56:22Z

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 […]

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

2017-09-26T07:27:21Z

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 […]

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

2017-09-21T13:44:40Z

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 […]

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

2017-09-18T13:12:30Z

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 […]

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

2017-09-18T13:12:14Z

The 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 […]

(image) The 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.