W3C News

Web Payments Workshop Participants Urge W3C to Form Steering Committee

Today W3C published its report from the March Workshop on Web and Payments. More than 100 people from the banking industry, payment service providers, virtual currencies providers, financial institutions, mobile industry, browser vendors, payment regulators, and payment standardization bodies met to discuss Web payment use cases, business requirements, and standardization priorities.

During their two-day agenda they addressed questions such as how can both legacy business models and new business models involving payment be better enabled on the Web? What are the main obstacles to seamless payments on the Web? on Mobile devices? What can we do to facilitate global transactions while still respecting local laws, regulation and both existing and new business models?

Participants recorded key outputs from the meeting, including a recommendation that W3C establish a “steering group” (a W3C Interest Group) to formulate a strategy and roadmap of Web Payments, including existing work at W3C and potential new work. W3C invites expressions of interest in the development of this steering group. For more information, contact Stéphane Boyera.

Requirements for IndieUI: Events 1.0 and IndieUI: User Context 1.0 First Public Working Draft Published

The Independent User Interface (Indie UI) Working Group today published the First Public Working Draft of Requirements for IndieUI: Events 1.0 and IndieUI: User Context 1.0. The document introduces use cases related to the IndieUI specifications and the technical requirements for meeting the use cases. IndieUI: Events defines a way for different user interactions to be translated into simple events and communicated to web applications. With IndieUI, web application developers will have a uniform way to design applications that work for multiple devices and contexts. It is introduced in the IndieUI Overview. One focus of IndieUI is enabling better user interaction in the mobile environment. This Requirements document provides an opportunity for early review of user needs to be addressed by the IndieUI specifications. Learn more about the Web Accessibility Initiative (WAI).

SVG Integration Draft Published

The SVG Working Group has published a Working Draft of SVG Integration. This specification details requirements on how SVG documents must be processed when used in various contexts, such as CSS background images, HTML ‘iframe’ elements, and so on. These requirements include which features are restricted or disabled, such as scripting and animation. A number of referencing modes are defined, which other specifications that allow the embedding or referencing of SVG documents can normatively reference. Learn more about the Graphics Activity.

XQuery 3.0, XPath 3.0, XQueryX 3.0, XDM 3.0, Serialization 3.0, Functions and Operators 3.0 are now W3C Recommendations

The XML Query Working Group published XQuery 3.0: An XML Query Language, along with XQueryX, an XML representation for XQuery, both as W3C Recommendations, as well as the XQuery 3.0 Use Cases and Requirements as final Working Group Notes. XQuery extends the XPath language to provide efficient search and manipulation of information represented as trees from a variety of sources.

The XML Query Working Group and XSLT Working Group also jointly published W3C Recommendations of XML Path Language (XPath) 3.0, a widely-used language for searching and pointing into tree-based structures, together with XQuery and XPath Data Model 3.0 which defines those structures, XPath and XQuery Functions and Operators 3.0 which provides facilities for use in XPath, XQuery, XSLT and a number of other languages, and finally the XSLT and XQuery Serialization 3.0 specification giving a way to turn values and XDM instances into text, HTML or XML.

Read about the XML Activity.

XML Entity Definitions for Characters (2nd Edition), and Mathematical Markup Language (MathML) Version 3.0 2nd Edition are W3C Recommendations

The Math Working Group has published two W3C Recommendations today:

  • XML Entity Definitions for Characters (2nd Edition). This document defines several sets of names, so that to each name is assigned a Unicode character or sequence of characters. Each of these sets is expressed as a file of XML entity declarations.
  • Mathematical Markup Language (MathML) Version 3.0 2nd Edition. This specification defines the Mathematical Markup Language, or MathML. MathML is a markup language for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text.

Learn more about the Math Activity.

W3C Track at WWW2014 in Seoul

WWW2014 logoAt this year’s 23rd International World Wide Web Conference (WWW2014), W3C organizes W3C tutorial and W3C tracks where conference participants are invited to learn from, meet and discuss with our team of experts. With the conference located in Korea, the W3C track sessions also cater specifically for the Korean industry. The presentations and discussions are about Web Cryptography, Web Publishing, Web & TV, and Web accessibility. W3C and Tim Berners-Lee will dedicate the last W3C track session to the Web 25th birthday; ideas for the Web came and are still coming from the WWW conference series, thus we will give the floor to the audience and ask conference participants how they see the Web evolving in the next 25 years. So, come and discuss!

MBUI: Abstract User Interface Models, and Task Models Notes Published

The Model-Based User Interfaces Working Group has published two Group Notes today:

  • MBUI – Abstract User Interface Models. Model-Based User Interface Design facilitates interchange of designs through a layered approach that separates out different levels of abstraction in user interface design. This document covers the specification of Abstract User Interface Models, by defining its semantics through a meta-model, and an interchange syntax (expressed as XML Schema) for exchanging Abstract User Interface Models between different user interface development environments.
  • MBUI – Task Models. Task models are useful when designing and developing interactive systems. They describe the logical activities that have to be carried out in order to reach the user’s goals. This document covers the specification of Task Models, with a meta-model expressed in UML, and an XML Schema that can be used as the basis for interchange of Task Models between different user interface development tools.

Learn more about the Ubiquitous Web Applications Activity.

CSS Line Grid Module Level 1, and CSS Scoping Module Level 1 Drafts Published

The Cascading Style Sheets (CSS) Working Group has published two Working Drafts today:

  • CSS Line Grid Module Level 1. This module contains CSS features for aligning content to a baseline grid.
  • CSS Scoping Module Level 1. This specification defines various scoping/encapsulation mechanisms for CSS, including scoped styles and the @scope rule, Shadow DOM selectors, and page/region-based styling.

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

Review of apps that use network information Note Published

The Web and Mobile Interest Group has published a Group Note of Review of apps that use network information. The web platform currently lacks a means of exposing network-related information to web applications. Network information includes, but is not limited to, the type of network connection currently in use by a device (e.g., cellular, Wi-Fi, etc.). It can also include information such as the system notifying the application when the type of connection changes from one type to another (e.g., from cellular to Wi-Fi). Learn more about the Mobile Web Initiative Activity.

Vocabularies for EmotionML Note Published

The Multimodal Interaction Working Group has published a Group Note of Vocabularies for EmotionML. This document provides a list of emotion vocabularies that can be used with EmotionML to represent emotions and related states. EmotionML provides mechanisms to represent emotions in terms of scientifically valid descriptors: categories, dimensions, appraisals, and action tendencies. Given the lack of agreement in the community, EmotionML does not provide a single vocabulary of emotion terms, but gives users a choice to select the most suitable emotion vocabulary in their annotations. In order to promote interoperability, publicly defined vocabularies should be used where possible and reasonable from the point of view of the target application. The present document provides a number of emotion vocabularies that can be used for this purpose. Learn more about the Multimodal Interaction Activity.