W3C

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

In the last 1 1/2 years, the LIDER project has organized several roadmapping events to gather a broad community around the topic of linguistic linked data. In July this year, LIDER will engage with two selected communities. On July 6, the 5th LIDER roadmapping workshop will be held in Rome at Sapienza University of Rome . The topic will be cross-media linked data and the event will provide several high level speakers from the multimedia area. On July 13th LIDER will organize the 6th roadmappping workshopin Munich. The event will be hosted by Siemens and will focus on content analytics and linked data in healthcare and medicine.

For both workshops participation is limited. If you are interested in the Rome event please contact Tiziano Flati , for Munich please contact Philipp Cimiano.

Version 8.0 of the Unicode Standard is now available. It includes 41 new emoji characters (including five modifiers for diversity), 5,771 new ideographs for Chinese, Japanese, and Korean, the new Georgian lari currency symbol, and 86 lowercase Cherokee syllables. It also adds letters to existing scripts to support Arwi (the Tamil language written in the Arabic script), the Ik language in Uganda, Kulango in the Côte d’Ivoire, and other languages of Africa. In total, this version adds 7,716 new characters and six new scripts. For full details on Version 8.0, see Unicode 8.0.

The first version of Unicode Technical Report #51, Unicode Emoji is being released at the same time. That document describes the new emoji characters . It provides design guidelines and data for improving emoji interoperability across platforms, gives background information about emoji symbols, and describes how they are selected for inclusion in the Unicode Standard. The data is used to support emoji characters in implementations, specifying which symbols are commonly displayed as emoji, how the new skin-tone modifiers work, and how composite emoji can be formed with joiners. The Unicode website now supplies charts of emoji characters, showing vendor variations and providing other useful information.

Some of the changes in Version 8.0 and associated Unicode technical standards may require modifications in implementations. For more information, see Unicode 8.0 Migrationand the migration sections of UTS #10, UTS #39, and UTS #46.

W3C is aiming to streamline Web Payments with new standards that will provide a uniform way for merchants to integrate payments into the Web with a level playing field for payment service providers and value added services. The HTML5Apps project initiated this work in 2014 by organizing the Web Payments Workshopat the “Bourse de Paris” to discuss requirements related to usability, security, mobile payments, digital wallets, ubiquitous payments, the Internet of Things, and more.

The Web Payment Interest Group , formed as a outcome of that workshop, is meeting this week in New York, in the heart of the financial community, for a  three day meeting (June 16-18) which aims to prepare the ground for launching a W3C Working Group on Web Payments standards later this year. The HTML5Apps project is helping stakeholders to clarify the scope and technical direction for chartering the new group.

On June 18, W3C will hold a  Future of Web Payments Industry Roundtable, hosted by Bloomberg. Participants at the Roundtable includes  representatives from W3C’s Web Payments IG, including Apple, Bloomberg, Deutsche Telekom, Gemalto, Google, Mozilla, NACS, Rabobank, Ripple Labs, Target, US Federal Reserve Bank, Walmart, Yandex, and others.


Filed under: HTML5 , html5apps , Payment , Standardization

In the context of the  Big Data Value Association Madrid Summit , 17-19th June, there are two sessions of specific relevance to standards and also to multilingualism: on 18th June a  session on standardization , and on 19th June a session on  Multilingual Data Value Chains . If you want to have an active participation in both sessions or want to provide further feedback, please contact Felix Sasaki < fsasaki@w3.org > on Standardization and Asun Gomez-Perez < asun@fi.upm.es> on Multilingual Data Value Chains. Presentation will be short in order to promote a wide participation.

If you cannot be in Madrid please also provide your input – see above session links for further instructions. The BDVA Summit will be crucial in shaping upcoming funding opportunities related to Big Data. Don’t miss the chance to describe your views on opportunities, challenges and potential solutions for the Big Data Value Chain!

A deliverable of the HTML5Apps project, the May 2015 editionof the W3C Standards for Web Applications on Mobileis out!

It includes a few changes and additions since January 2015. Notably:

Published as First Public Working Draft
  • the audio ouput devices APIwhich lets orient audio streams to different output devices was published as a First Public Working Draft in February;
  • the Presentation API, a critical component in enabling second-screen experiences, was released as First Public Working Draft in February;
  • the WAI WCAG and UAAG Working Groups released their mapping of accessibility guidelines to mobileas a Fist Public Working Draft in February;
  • the credential management APIthat lets Web applications interact with browser-stored user credentials, was published as First Public Working Draft in April;
  • the Permissions APIwhich exposes what permissions the user has or has not granted to the Web app, was published as First Public Working Draft in April;
  • The Web Payments Interest Group published a First Public Working Draft of their payment use casesin April;
Published as Last Call Working Draft
  • the Media Capture and Streamsspecification that brings audio and video from cameras and microphones to Web applications was published as a Last Call Working Draft in April;
Returned to Working Draft
  • the canvas API, previously published as a Candidate Recommendation, returned to Last Call Working Draft status to reflect changes brought to its accessibility features;
Reached Candidate Recommendation
  • the Web NotificationsAPI that lets Web apps notify theirs users using the underlying OS notification system, was released as a Candidate Recommendation;
Specification merged, split or abandoned
  • the work started on an NFC API in the NFC Working Group has been abandonned, while new work on browser-compatible approach to NFC has started in the Web NFC Community Group;
Newly tracked
  • the Geolocation Working Group released an editors draft of their proposed Geofencing API.

This document is the 17th edition of this overview of mobile Web applications technologies. The previous edition was released in January 2015 . A live version of this document accepts contributions on the W3C Web and Mobile Interest Group Github repository.


Filed under: Developer , HTML5 , html5apps , Mobile , Standardization

The HTML5Apps EU project is featured in the W3C track of the 24th World Wide Web Conference,Florence, Italy. Today, Dominique Hazaël-Massieux gives a talk on Rich APIs in the morning session, formatted as a developer camp. All conference participants are invited to come suggest topics of discussion related to HTML5-based apps, current and future.


Filed under: Developer , Event , HTML5 , html5apps , Mobile

The World Wide Web Consortium (W3C) is looking for a new, full-time staff member to be located at Beihang University in Beijing, where W3C currently has its China Host, to assist, as team contact, W3C Working Groups developing technical specifications in the fields of Ubiquitous Web or Technology and Society.

This is an opportunity for a unique individual to be part of the team responsible for the design of next generation World Wide Web Technologies and to lead a variety of industry and user groups toward the development of technologies that enhance the functionality of the Web. As the recognized leader for the technical development of the World Wide Web, we are seeking an individual with both Web technology and project management experience, an excellent understanding of the Web industry, and enthusiasm for the mission and spirit of W3C.

Responsibilities

The individual will work within standard groups to edit specifications, develop change proposals, monitor progress, reach out to different stakeholders, produce tests, and to respond to clarification requests, bugs and issues.

We would welcome candidates with specific technology or business skills such as:

Generic Skills Required

  • Bachelors Degree or higher
  • Background in computer science and software engineering;
  • An understanding of the Web industry and its market, practices, and product development cycles;
  • Familiarity with up-to-date Web technologies, such as HTML, CSS, Web APIs and Scripting;
  • A Team player with good communication / interpersonal skills
  • Ability to work remotely and effectively is required;
  • Experience with the development of open information technology standards is desired;
  • Ability to travel internationally is required
  • Good written and spoken competency in the working language of the W3C, i.e., English, as well as in Chinese is required;
  • Strong writing skills required, with past experiences in editing technical specifications a plus;
  • Knowledge and practical experience of other languages and cultures is a plus

Work starts 1 August 2015

The Position is based at the School of Computer Science & Engineering of Beihang University, No.37 Xueyuan Road, Haidian District, Beijing. There will be regular international travel including to W3C Host sites, and regular remote work with the Working Groups and the W3C Global staff.

To apply, please send a motivation letter, your resume or CV and (if at all possible) copies of your Diplomas (including High School or equivalent) in electronic form to <team-beihang-position@w3.org>.

Developer Economics 9 Is HTML vs. Native still relevant? Will IoT play out in your ecosystem?Are you using AWS, Azure or Google Cloud? Which are the hottest IoT verticals? Which are your top platforms, tools, revenue models?

These are some of the questions that our friends at VisionMobileaddress through their Developer Economics research, so please:

  • Make your voice heard!It takes only 10 minutes to fill in the survey
  • … and claim cool prizessuch as an iPhone 6, an Oculus Rift Dev Kit, and many more.

Now in its 9th edition, the Developer Economics research program tracks developer sentiment across platforms, revenues, apps, tools, APIs, segments and regions. This is the most ambitious developer survey to date, spanning across mobile, IoT, desktop and Cloud.

Take the survey here: http://vmob.me/DE3Q15HTML5Apps

The key insights from the survey will be given back to the community as a free download in late July 2015.


Filed under: Developer , HTML5 , html5apps

Language Tags and Locale Identifiers for the World Wide Webdescribes the best practices for identifying or selecting the language of content as well as the the locale preferences used to process or display data values and other information on the Web. It describes how document formats, specifications, and implementations should handle language tags, as well as extensions to language tags that describe the cultural or linguistic preferences referred to in internationalization as a “locale”.

Changes in this update include the following: All references to RFC3066bis were updated to BCP 47 or to RFC5646 or RFC 4647 as appropriate.References to HTML were changed to point to HTML5. Imported and rewrote the text formerly containing in Web Services Internationalization Usage Scenarios defining internationalization, locale, and other important terms. Modified and reorganized the other sections of this document. Moved the Web services materials to an appendix.

The W3C Web Payments Interest Group has just published a set of Web Payments Use Cases(v1.0) as W3C First Public Working Draft (FPWD).

The interest group, formed in October 2014 thanks to the work initiated by the HTML5Apps project, developed these use cases to help establish a standards’ roadmap to make Web payments easier, more secure, and more interoperable across merchants, banks, platforms, and devices.

The Interest Group is now seeking wide review of this draft, by W3C groups and Members, industry standards bodies, and other stakeholders.

The Web Payments Interest Group, which goals are documented in this wiki page,is constituted by 35 organizations, including:

  • Banks: Rabobank, Groupe BPCE, US Federal Reserve Bank
  • Card association: Visa Europe
  • Payment solution providers: Worldpay, Google, Alibaba, Paygate, Yandex, Ripple Labs, Standard Treasury, SHIFTMobility, Shimply, Digital Bazaar, Verisign
  • Hardware providers: Gemalto, IBM, Intel
  • Browser makers: Opera, Google, Tencent
  • Mobile operators: Orange, Deutsche Telekom, GSMA, AT&T, SK Telekom
  • Merchants and associations: NACS, Bloomberg, Merchant Advisory Group (including Walmart), Target, FSTC

If your organization belongs to one these above categories, and is  interested by the work, please join the groupnow!


Filed under: html5apps , Payment , Standardization