RE: Charter for Native Apps

To avoid having to dig through emails, I merged the suggestions I made with the initial suggestion from Marcos.  (not suggesting this as the actual wording, but as content that should be represented in some way)
-----

The Native Apps Community Group is chartered to specify technologies that allow packaged Web applications to be run locally, to be deployed from servers and to be transformed into other proprietary formats so that they may be run on different platforms. The members will do that by:

* Creating and maintaining specifications and test suites relevant to "packaged web apps" (e.g., the W3C Widget Family of Specifications).
* Gathering use cases and requirements from vendors relying on these technologies.
* Suggesting refinements or fixes to existing specifications to better meet the needs of these applications.  
* Evangelizing specifications to vendors and development communities.
* Documenting how to best use open web standards to build "native web apps"
* Documenting best practices and, where possible, make tools available to developers

The Native Apps Community Group will develop specifications, and thus, there will be Essential Claims under the W3C Contributor License Agreement or Final Specification Agreement.

Relationship with W3C Web Apps WG:
* For Web Apps WG widget specs currently in PR or REC, the Native Web Apps CG will handle errata and will work with the Web Apps WG on publishing any needed Edited Recommendations.  This currently applies to: 1) Widget Packaging and XML Configuration, 2) XML Digital Signatures for Widgets, 3) view-mode Media Features and 4) WARP.
* For Web Apps WG widget drafts that have not reached PR, technical work on these drafts will take place in the Native Web Application CG and will be passed to the Web Apps WG to move toward REC.  The CG will handle any technical change requests originating from the WG.  This applies to: 1) Widget Interface, 2) Widget Updates, 3) widget URI scheme. 

Relationship with W3C WGs for future, new Native Web Apps CG specifications:
For future W3C Native Web Apps CG specifications that W3C agrees to move to the REC track, the Native Apps CG will work with a related W3C WG.  The CG will provide drafts to the WG for each stage in the W3C Process and will respond to both WG and review comments.  All technical work on the spec takes place in the CG.  This could be with a new W3C WG, not necessarily the current Web Apps WG.

How to contribute to Native Web Apps Specifications:
All formal Contributions to Specifications are posted (or cc'd) to the archived public-native-web-apps-contrib@w3.org contribution list.  This is an essential element of tracking the origin and date of Contributions to Specifications.  Posts to this list should include the name of the Specification the Contribution is being made to.

Received on Wednesday, 23 November 2011 17:51:04 UTC