w3c-webmob / web-api-gap Goto Github PK

BlackBerry10 is more appropriate than only BlackBerry, since we are referring to the platform instead of the brand.

send to dom an example of what i imagine the accelerometer data to look like in the document so he can adapt the script for this

do we need to add beacon apis?

do we keep, change or remove sysapp from data? recommendation is to remove

Hi all! For each API we will need to list / show qualities related to information the readers will want to see, are people happy to show these pieces of information for each API?:

• Feature: what feature the api has
• Description: of the api functions
• API / Platforms: list native platforms which use this api and the names they give it
• Related Web API: does a related web api exist?
• Working Group: which w3c working group is/should look after this?
• Current implementations: do any browsers do this already?
• Plugins: do any plugins do this already?
• Security Concern: short sentence on possible security concern of api
• Dependancies: what would the web need to have to support this?

For notes: here are the related APIs for each section:

• Core Web Design and Development: SVG, Canvas, WebGL, CSS Transforms, CSS Animations, Web Animations, Flexbox, Fonts (CSS Font Loading, WOFF), Full Screen, Screen Orientation, 3D graphic API for HTML5

(phonegap is the commercial name of a specific product)

In https://github.com/w3c-webmob/web-api-gap/blob/gh-pages/document_text.md add some comments as to how healthy the development of web versions of the apis are.

Last time we spoke we were thinking of making it similar to Dom’s "Standards for Web Applications on Mobile: current state and roadmap" document (http://www.w3.org/Mobile/mobile-web-app-state).

What I want to figure out now is how we should structure the API Document. Effectively we'll be listing Native APIs and the platforms that support them, then we'll be stating somewhere whether they have been implemented on the web yet or not. So, we could group APIs by categories, as in the "Standards for Web Applications on Mobile: current state and roadmap" document.

If you guys agree with this - can we copy the structure from the "Standards for Web Applications on Mobile: current state and roadmap" document for our document? Or do you think we need to add or remove some categories. The categories currently are:

• Core Web Design and Development
  • Graphics and Layout
  • Device Adaptation
  • Forms
• Data storage
• Media and Real-Time Communications
• Usability and Accessibility
• Device Interaction
• Network Integration
• Application Lifecyle
• Payment and Services
• Performance & Tuning
• Security & Privacy

based on #11