Re: Charter clarification: common manifest
On Mon, 30 Jan 2012 17:51:14 +0100, Robin Berjon wrote: On Jan 30, 2012, at 13:38 , Marcos Caceres wrote: On Monday, 30 January 2012 at 21:26, Robin Berjon wrote: It's not something that has happened to date, but I'm hearing indications that there could be interest in quickly aligning on a manifest for web apps (that would I presume differ from the one used in Widgets). Interesting… pointer to these indicators would be nice (or would be nice to hear from WG members). Tobie kicked up some dust here: http://blog.tobie.me/post/14262541286/app-manifests-an-anthology I can't seem to track down pointers right when I need them, but this spurred a fair amount of commentary, including from some people who work for implementers agreeing that the current situation is stupid and needs to be fixed. It would be a shame to close the door right as it looks like it might happen. Agree. However, an alternative serialisation of the Widget's metadata can be specified in the Native Web Apps CG and then a WG home can be found. Sure, I'm happy for the work on this to take place in the NWA CG since that seems like a fit home for it, but it needs a place to be properly standardised. My hope is that this place can be the WebApps WG. Given that the discussion would take place elsewhere, and that the result is pretty much in charter, I would hope that this should be agreeable to all. I'll write it that way into the charter draft. I also hope that it is seen that way by the WG. cheers Chaals -- Charles 'chaals' McCathieNevile Opera Software, Standards Group je parle français -- hablo español -- jeg kan litt norsk http://my.opera.com/chaals Try Opera: http://www.opera.com
Re: Charter clarification: common manifest
On Jan 30, 2012, at 13:38 , Marcos Caceres wrote: > On Monday, 30 January 2012 at 21:26, Robin Berjon wrote: >> It's not something that has happened to date, but I'm hearing indications >> that there could be interest in quickly aligning on a manifest for web apps >> (that would I presume differ from the one used in Widgets). > > Interesting… pointer to these indicators would be nice (or would be nice to > hear from WG members). Tobie kicked up some dust here: http://blog.tobie.me/post/14262541286/app-manifests-an-anthology I can't seem to track down pointers right when I need them, but this spurred a fair amount of commentary, including from some people who work for implementers agreeing that the current situation is stupid and needs to be fixed. >> It would be a shame to close the door right as it looks like it might happen. > > Agree. However, an alternative serialisation of the Widget's metadata can be > specified in the Native Web Apps CG and then a WG home can be found. Sure, I'm happy for the work on this to take place in the NWA CG since that seems like a fit home for it, but it needs a place to be properly standardised. My hope is that this place can be the WebApps WG. Given that the discussion would take place elsewhere, and that the result is pretty much in charter, I would hope that this should be agreeable to all. -- Robin Berjon - http://berjon.com/ - @robinberjon
Re: Charter clarification: common manifest
On Monday, 30 January 2012 at 21:26, Robin Berjon wrote: > Hi all, > > there is one aspect of the upcoming charter that I would like to see > clarified. Previously, it has been my understanding that if implementers > wanted to agree on a common manifest format for web apps, they ought to be > able to do so within the bounds of this WG given that the same idea (and > therefore the same IP) is already covered by Widgets. > > It's not something that has happened to date, but I'm hearing indications > that there could be interest in quickly aligning on a manifest for web apps > (that would I presume differ from the one used in Widgets). Interesting… pointer to these indicators would be nice (or would be nice to hear from WG members). > It would be a shame to close the door right as it looks like it might happen. Agree. However, an alternative serialisation of the Widget's metadata can be specified in the Native Web Apps CG and then a WG home can be found. > So my question is: do the changes around widgets in the charter preclude work > on such a common manifest format? I would hope not. > If so, can we simply leave the door open to that so that we don't find > ourselves locking that work out when it's most likely to happen? > Again, pointers to where this discussion is happening would be nice… :) -- Marcos Caceres http://datadriven.com.au
Charter clarification: common manifest
Hi all, there is one aspect of the upcoming charter that I would like to see clarified. Previously, it has been my understanding that if implementers wanted to agree on a common manifest format for web apps, they ought to be able to do so within the bounds of this WG given that the same idea (and therefore the same IP) is already covered by Widgets. It's not something that has happened to date, but I'm hearing indications that there could be interest in quickly aligning on a manifest for web apps (that would I presume differ from the one used in Widgets). It would be a shame to close the door right as it looks like it might happen. So my question is: do the changes around widgets in the charter preclude work on such a common manifest format? If so, can we simply leave the door open to that so that we don't find ourselves locking that work out when it's most likely to happen? -- Robin Berjon - http://berjon.com/ - @robinberjon