System Applications Working Group

On this page:

Mission | Roadmap | Phase 2 | Participate | Meetings | Communications

Nearby:

SysApps Wiki | Device APIs WG | WebApps WG | HTML WG

Administrative:

"My Actions" | "My Questionnaires" | Participants | Patent Policy Status | Open Issues | Open Actions | Public email list | Member email list | LC Tracker

Mission

As defined in its charter, the mission of the System Applications Working Group is to define a runtime environment, security model, and associated APIs for building Web applications with comparable capabilities to native applications.

Roadmap

The Working Group's deliverables are divided into two phases. In phase 1, the Working Group will focus on the execution and security models, and validating them through work on a small set of specific APIs. This will be used to establish the patterns and conventions that will be used for the remaining deliverables. The Working Group does not need to complete work on all the phase 1 deliverables before starting work on deliverables in phase 2. However, the Working Group should make substantial progress on some of the phase 1 deliverables before working on phase 2 deliverables, at which point it should be possible to do more work in parallel.

Below is the schedule for phase 1 as detailed in the initial Working Group charter.

Specification	Internal draft	Public Working draft	Stable draft (Last Call)	Implementors feedback (CR)	Standard (Rec)	Test Suite	Notes
Active work
Execution & Security Models	9 Mar 2013	21 Mar 2013	Q2 2013	Q2 2013
Alarm	7 Mar 2013	5 Feb 2013	Q2 2013	Q2 2014
Contacts	11 Mar 2013	7 Mar 2013	Q2 2013	Q2 2014
Messaging	22 Mar 2013	Q1 2013	Q2 2013	Q2 2014
Telephony	28 Mar 2013	Q1 2013	Q2 2013	Q2 2014
Raw Sockets	18 Mar 2013	Q1 2013	Q2 2013	Q2 2014

See also the list of the System Applications published Technical Reports.

Phase 2

The following are the Working Group's phase 2 deliverables. The Working Group intends to make significant progress on some of the phase 1 deliverables before working on phase 2.

Bluetooth API

A low-level API to interact with the Bluetooth hardware available on some devices. Examples: Tizen Bluetooth, B2G Web Bluetooth.

Browser API

An API that provides all the necessary items to build a Web browser that aren't otherwise available. Most notably, this provides all that is needed in order to safely instantiate a viewport onto the open Web, pretend that such a viewport is the top level window even if the browser's chrome is itself written using Web technology, etc. Example: B2G BrowserAPI.

Calendar API

An API that enables complete management of the device's calendars. Examples: B2G Calendar, Tizen Calendar.

Device Capabilities API

An API that exposes the capabilities available to the device. Example: Tizen System Info.

Idle API

An API to be notified when the user is idle. Example: B2G Idle.

Media Storage API

An API to manage the device's storage of specific content types (e.g. pictures). Examples: Tizen Media Content, B2G Device Storage.

Network Interface API

An API to manipulate network interfaces (mobile, WiFi, etc.), such as listing available networks, current strength, etc., as well as configuring and enabling them. It may build atop the simpler network information API that Device APIs is working on. Potential uses include offloading connections from mobile networks to WiFi, enabling high priority mobile data connections and control of other network features. Examples: B2G Mobile Connection, B2G WiFi Information.

Secure Elements API

An API enabling the discovery, introspection, and interaction with hardware tokens (Secure Elements) that offer secure services such as tamper-proof storage, cryptographic operations, etc. Example: Gemalto Secure Elements.

System Settings API

An API to manage the system's settings (e.g. time/clock settings, and personal preferences including privacy preferences). Example: B2G Settings.

Participate

If you are employed by a W3C Member and want to join this group, please ask your Advisory Committee Representative to nominate you to the group as explained in the relevant instructions.

If you are not employed by W3C Member and have specific expertise to bring to this group, the said instructions explain how to get Invited Expert status.

See the list of current participants.

Meetings

We are currently working via email, the wiki and github. If the need arises teleconferences will be arranged on the Zakim teleconference bridge: +1.617.761.6200 (VoIP: sip:zakim@voip.w3.org) code TBD IRC channel #sysapps on irc.w3.org port 6665 (Web IRC client).

Please note that attendance of System Applications WG teleconferences is restricted to registered WG participants and persons invited by the chairs.

On each call please register attendance in IRC using

Present+ firstName_lastName

and please update the information on which caller you are. For example, if you are noted as +1-781-555-aaaa, use

zakim, aaaa is yourHandle

if you are ??P5 then use

zakim, ??P5 is yourHandle

You can obtain agenda and bridge information with /Topic at any time from within IRC.

We're tracking issues and action items using Tracker. You may see your actions using MyTracker.

Face to face meetings

The first F2F meeting will be held 9-11 April 2013 in Madrid and hosted by Telefonica. Please look at the logistics and agenda, and remember to register.

Minutes

There are no minutes recorded yet.

Communications

The main communication channel for this group is the publicly archived mailing list <public-sysapps@w3.org>.

Member-confidential messages and logistical discussions can be addressed to the member-only archived mailing list <member-sysapps@w3.org>

Patent Policy

This group operates under the W3C Patent Policy - see its Patent Policy status for more details.