W3C home > Mailing lists > Public > public-most-important-priorities@w3.org > January 2015

Re: Proceeding with [Core] via email discussion (Was Re: Postponed beginning for [Education], agenda for [Core])

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Tue, 06 Jan 2015 11:34:00 +0100
Message-ID: <54ABBA18.5040306@w3.org>
To: Jeff Jaffe <jeff@w3.org>, Arthur Barstow <art.barstow@gmail.com>, public-most-important-priorities@w3.org
On 05/01/2015 20:18, Jeff Jaffe wrote:
>> * Section 3. Mapping to native platforms - since Dom and the Web
>> Mobile IG have done quite a bit of work in this area (f.ex. gap
>> analysis <https://github.com/w3c-webmob/web-api-gap>), this document
>> should clarify what this effort is going to do vis--vis related work
>> in the IG.
> In fact, Dom told me he plans to utilize the Application Foundations
> taxonomy for the Mobile Web roadmap.  Dom, what is the best way to
> reflect that, or should we wait until the next time you publish a roadmap?

The next edition of the roadmap is scheduled for the end of this month, 
and I'm planning to integrate the application foundations taxonomy in 
that one.

But the work Art is referring to is distinct from the roadmap: 
https://github.com/w3c-webmob/web-api-gap is a fairly broad (although by 
no means exhaustive) review of what APIs/features are available in 
various native mobile platforms (with links to their respective 
documentation), and are or are not available in Web-based platforms.

As Art, I'm hoping that work can help when diving into each of the 
foundation to determine what already exists, and how it compares to what 
we're working on, or not working on yet.

Received on Tuesday, 6 January 2015 10:34:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:30:58 UTC