Web of Devices

W3C is focusing on technologies to enable Web access anywhere, anytime, using any device. This includes Web access from mobile phones and other mobile devices as well as use of Web technology in consumer electronics, printers, interactive television, and even automobiles.

Mobile Web Header link

W3C promotes “One Web” that is available on any device. W3C’s Mobile Web Initiative helps ensure the best user experience on mobile devices, taking into account device capabilities, location, and other context information.

Voice Browsing Header link

The W3C Speech Interface Framework is a suite of specifications (e.g. VoiceXML) integrating Web technology and speech interaction. VoiceXML, PLS, SISR, SRGS, SCXML, and CCXML all contribute to the Speech Interface Framework.

Device Independence and Content Adaptation Header link

Devices come in many shapes, capabilities and sizes which define constraints on the content these devices can handle. Device descriptions, content transformation guidelines, device APIs and CC/PP help developers to optimize the user experience.

Multimodal Access Header link

Increasingly, interactions with devices doesn’t only happen with a keyboard, but also through voice, touch and gestures. The W3C Multimodal architecture and its components (EMMA, InkML) allow developers to adapt applications to new interaction modes.

Web and TV Header link

With the advent of IP-based devices, connected TVs are progressing at a fast pace and traditional TV broadcasting is quickly evolving into a more immersive experience where users can interact with rich applications that are at least partly based on Web technologies. There is strong growth in the deployment of devices that integrate regular Web technologies such as HTML, CSS, and SVG, coupled with various device APIs.

News Atom

W3C20 video

28 October 2014

from Mobile Web @ W3C - W3C

HTML5 logo The W3C HTML5Apps team is very proud to relay the good news that HTML5 reached the W3C Web standard status today!

HTML5 defines the fifth major revision of the Hypertext Markup Language (HTML), the format used to build Web pages and applications, and the cornerstone of the Open Web Platform.

Today we think nothing of watching video and audio natively in the browser, and nothing of running a browser on a phone,” said Tim Berners-Lee, W3C Director and Web inventor. “ We expect to be able to share photos, shop, read the news, and look up information anywhere, on any device. Though they remain invisible to most users, HTML5 and the Open Web Platform are driving these growing user expectations.

HTML5 brings to the Web video and audio tracks without needing plugins; programmatic access to a resolution-dependent bitmap canvas, which is useful for rendering graphs, game graphics, or other visual images on the fly; native support for scalable vector graphics (SVG) and math (MathML); annotations important for East Asian typography (Ruby); features to enable accessibility of rich applications; and much more.

W3C20 video

Web standards for the future

For news on what’s next after HTML5, see W3C CEO Jeff Jaffe’s blog post on “ Application Foundations for the Open Web Platform”.

Find out in less than 2 minutes why Web Standards for the future are important by watching the  Web standards for the futurevideo.

Filed under: HTML5 , html5apps , Standardization


15 October 2014

from Mobile Web @ W3C - W3C

HTML5Apps/W3C announced today a new Web Payments Initiativeto integrate payments seamlessly into the Open Web Platform.

W3C calls upon all industry stakeholders–banks, credit card companies, governments, mobile network operators, payment solution providers, technology companies, retailers, and content creators– to join the new Payments Interest Groupand leverage the unique ability of the Web to bridge ecosystem diversity and reach users everywhere, on any device.

The result will be new business opportunities, an improved user experience for online transactions, reduced fraud, and increased interoperability among traditional solutions and future payment innovations.

Read the full press release ( in English and in French ) including testimonials from W3C MembersBloomberg, Gemalto, GRIN Technologies, Ingenico Group, NACS, Rabobank, and Yandex.

Filed under: html5apps , Payment , Standardization

This is the 3-10 October 2014edition of a “weekly digest of W3C news and trends” that I prepare for the W3C Membership and public-w3c-digest mailing list (publicly archived). This digest aggregates information about W3C and W3C technology from online media —a snapshot of how W3C and its work is perceived in online media.

W3C and HTML5 related Twitter trends

[What was tweeted frequently, or caught my attention. Most recentfirst]

Open Web & net neutrality

W3C in the Press (or blogs)

22articles since the last Digest; a selection follows. You may read all articles in our Press Clippingspage.

The Encoding specificationhas been published as a Candidate Recommendation. This is a snapshot of the WHATWG document, as of 4 September 2014, published after discussion with the WHATWG editors. No changes have been made in the body of this document other than to align with W3C house styles. The primary reason that W3C is publishing this document is so that HTML5 and other specifications may normatively refer to a stable W3C Recommendation.

Going forward, the Internationalization Working Group expects to receive more comments in the form of implementation feedback and test cases. The Working Group
believes it will have satisfied its implementation criteria no earlier than 16 March 2015. If you would like to contribute test cases or information about implementations, please send mail to www-international@w3.org.

The utf-8 encoding is the most appropriate encoding for interchange of Unicode, the universal coded character set. Therefore for new protocols and formats, as well as existing formats deployed in new contexts, this specification requires (and defines) the utf-8 encoding.

The other (legacy) encodings have been defined to some extent in the past. However, user agents have not always implemented them in the same way, have not always used the same labels, and often differ in dealing with undefined and former proprietary areas of encodings. This specification addresses those gaps so that new user agents do not have to reverse engineer encoding implementations and existing user agents can converge.


17 September 2014

from Mobile Web @ W3C - W3C

The W3C HTML Working Group , responsible for the HTML5 specification’s progress, has published a Proposed Recommendation of HTML5(on 16 September 2014). This specification is intended to become a W3C Recommendation (or Web standard).

The W3C Membership and other interested parties are invited to review the document and send comments to public-html@w3.org ( archives) through 14 October 2014.

Learn more about the HTML Activity.

Filed under: HTML5 , html5apps

A meetingwas held in Paris on 3-4 September 2014 to bring together browser vendors and other stakeholders to discuss next steps for work on trust and permissions for the Open Web Platform, based upon insights gained from experience with native app platforms, hybrid and proprietary Web platforms.

Meeting participants included Apple, Ericsson, ETRI, Gemalto, GM, Google, Intel, Microsoft, Samsung, Sony Mobile, and Qualcomm.  We reviewed how permissions are handled in existing platforms, including current APIs in the Open Web Platform,  as well as for iOS, Android, Windows Phone, Chrome Apps, Firefox OS and GM’s Web platform for automotive.

We then looked at what can be learned from research studies. Adrienne Porter Felt introduced her work towards comprehensive and effective permission systems. This includes a diagram depicting a decision graph for determining the most effective permission grant mechanism in any given context.

Permissions mechanismsWe also heard about the role of trusted UI where user actions implicitly grant permissions in an intuitive way. We continued with discussion of which considerations are important for the Open Web Platform and a review of a draft permissions testing API from Google.

The final session considered plans for future work, identifying areas of rough consensus, and areas where further work is needed to close the gap.  We identified suggestions for existing W3C groups, and a proposal for a new Community Group to focus on best practices. For more details, see the meeting minutes and the plans for future work. We gratefully acknowledge Gemalto for hosting this meeting.

Filed under: Event , html5apps , Standardization


27 August 2014

from Mobile Web @ W3C - W3C

Earlier this year, members of the Cordovaand W3C teams started a process to better align W3C and Codova specifications.

Indeed, Cordova (from which the Phonegap framework derives) is one of the major projects used to build hybrid applications — applications written in HTML/JavaScript but run as native apps.

Hybrid applications benefit from the widespread knowledge of Web technologies, their cross-platform availabilities, while allowing developers to get inserted in the native ecosystems (including their application stores).

As a bridge between the native and the Web worlds, they are an important component in our overgoal of making it easier for developers to embrace the Web as platform on mobile.

Unfortunately, while in many areas Cordova re-use Web technologies as-is, for a number of historical reasons, device APIs as made available in the Cordova framework have not matched the ones used in Web browsers, as illustrated in the mobile Web API fragmentation report that we introduced last month.

To fix that situation, we are now looking at getting existing Cordova device APIs to converge towards W3C device APIs as much as possible, while making sure that the feedback of the Cordova developers is taken into account in the design of these APIs on the W3C side.

We have started by doing a deep dive into the Vibration API, since it has proved reasonably stable from the W3C side, and is a reasonably simple API in the first place.

We have also started incorporating Cordova’s feedback on the battery API.

These are only the first steps, and getting this convergence to happen will obviously require more time and effort; but the path towards it is now open!

Filed under: html5apps , Mobile , Standardization , Uncategorized


14 August 2014

from Mobile Web @ W3C - W3C

The HTML5Apps project is glad to announce the a new edition of the “Standards for Web Applications on Mobile: current state and roadmap” . This July 2014 edition notably features a new section on payment, which tracks the work initiated by the workshop organized by the project in March 2014.

This document summarizes the various technologies developed in W3C that increase the capabilities of Web applications, and how they apply more specifically to the mobile context.

Since the previous April edition, a number of new technologies have emerged for addition to the Web platform, opening the way for new exciting developments in the months to come. Stay tuned!

Filed under: HTML5 , Mobile , Payment , Standardization

A report summarizing the MultilingualWeb workshop in Madrid is now available from the MultilingualWeb site. It contains a summary of each session with links to presentation slides and minutes taken during the workshop in Madrid. The workshop was a huge success, with approximately 110 participants, and with the associated LIDER roadmapping workshop . The Workshop was hosted by Universidad Politécnica de Madrid , sponsored by the EU-funded LIDER project, by Verisign and by Lionbridge.
A new workshop in the MultilingualWeb series is planned for 2015.

This documentbuilds upon on the Character Model for the World Wide Web 1.0: Fundamentals to provide authors of specifications, software developers, and content developers a common reference on string matching on the World Wide Web and thereby increase interoperability. String matching is the process by which a specification or implementation defines whether two string values are the same or different from one another.

The main target audience of this specification is W3C specification developers. This specification and parts of it can be referenced from other W3C specifications and it defines conformance criteria for W3C specifications, as well as other specifications.

This version of this document represents a significant change from its previous edition. Much of the content is changed and the recommendations are significantly altered. This fact is reflected in a change to the name of the document from “Character Model: Normalization” to “Character Model for the World Wide Web: String Matching and Searching”.

Events Header link

See full list of W3C Events.