RE: Charter for Native Apps

Another suggestion for a charter addition. 

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.

>-----Original Message-----
>From: Carr, Wayne [mailto:wayne.carr@intel.com]
>Sent: Tuesday, November 22, 2011 3:09 PM
>To: Marcos Caceres; public-native-web-apps@w3.org; Arthur Barstow
>Subject: RE: Charter for Native Apps
>
>It would be good to list the agreed upon relationship with the WebApps WG[1].
>That describes the drafts not yet at PR but doesn't describe errata and Edited
>Recommendations (so that would need to be checked on with the Web Apps
>WG).  Something like:
>
>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.
>
>
>[1] http://www.w3.org/2008/webapps/wiki/CharterChanges#Widgets

>
>
>
>>-----Original Message-----
>>From: Marcos Caceres [mailto:w3c@marcosc.com]
>>Sent: Monday, November 21, 2011 1:09 AM
>>To: Brian LeRoux
>>Cc: Carr, Wayne; public-native-web-apps@w3.org; Arthur Barstow; Brian
>>LeRoux
>>Subject: Re: Charter for Native Apps
>>
>>
>>
>>
>>On Saturday, 19 November 2011 at 07:41, Brian LeRoux wrote:
>>
>>> This is great, thank you Marcos, I'm going to quickly forward around
>>> the PhoneGap team to get some involvement there.
>>>
>>> On Fri, Nov 18, 2011 at 8:35 PM, Carr, Wayne <wayne.carr@intel.com
>>(mailto:wayne.carr@intel.com)> wrote:
>>> > With the goals of the CG, I'd think the following is also assumed.
>>> > It may be
>>better to explicitly write it in the charter if its intended.
>>> >
>>> > "It would be desirable in the future to work with a W3C WG in order
>>> > to publish
>>some Native Apps CG Specifications as W3C Recommendations. If this
>>occurs, the W3C WG would shepherd the W3C CG Specs through the W3C REC
>>path process, with change requests moving back to the CG for all technical
>work."
>>> >
>>>
>>
>>Agreed - this is a good addition. I'll wait to see if there is any
>>further feedback and then consolidate everything.
>>

Received on Wednesday, 23 November 2011 17:34:43 UTC