Re: New draft of Widgets: Access Requests Policy
Hi Mohamed, On Jun 6, 2009, at 09:52 , mozer wrote: Sorry for disturbing Don't pretend you're sorry :) there is a bunch of space problem in the spec You expect space problems from a spec called WARP. probably it is only depending on your build process No, it's faulty cut and paste followed by failure to completely correct it. For example : * ASTERISK (*)character * Path Language (XPath)Version 1.0 * Steve DeRoseW3C Recommendation Fixed, thanks. Reference * probably you should consider referencing "RFC 2818: HTTP Over TLS" for HTTPS Added (and both moved to informative since they're not normatively referenced). * [Widgets-Reqs] is now dated from 30 april 2009 instead of september 2008 Fixed. * The same applies for [Widgets-DigSig] Fixed. * [Widgets-Updates] is now dated from 14 April 2008 Actually it isn't, it's just that the link pointed to Widgets Landscape :) Process question : since your making refrence to HTML5 normatively, do you expect HTML5 to become a REC before Widgets 1.0: Access Requests Policy Unless you can cite the part of process that says one can't reference drafts n steps behind, this is not a process issue. That being said, it's an issue irrespective of what Process says. I've addressed it by revisiting the way in which HTML5 is introduced. Since it is optional to support HTML, and since the rules that should apply are those of whichever language is used, we now: 1) defer to the host language, and therefore 2) make HTML5 informative again. Some precision : Please add at the top of section 3 The access element, that the access element in the namespace "http://www.w3.org/ns/widgets"; Done. Thanks a lot for your review! -- Robin Berjon - http://berjon.com/ Feel like hiring me? Go to http://robineko.com/
Re: New draft of Widgets: Access Requests Policy
Hi Robin, Sorry for disturbing : there is a bunch of space problem in the spec : probably it is only depending on your build process For example : * ASTERISK (*)character * Path Language (XPath)Version 1.0 * Steve DeRoseW3C Recommendation Reference * probably you should consider referencing "RFC 2818: HTTP Over TLS" for HTTPS * [Widgets-Reqs] is now dated from 30 april 2009 instead of september 2008 * The same applies for [Widgets-DigSig] * [Widgets-Updates] is now dated from 14 April 2008 Process question : since your making refrence to HTML5 normatively, do you expect HTML5 to become a REC before Widgets 1.0: Access Requests Policy Some precision : Please add at the top of section 3 The access element, that the access element in the namespace "http://www.w3.org/ns/widgets"; Regards Xmlizer On Fri, Jun 5, 2009 at 6:44 PM, Robin Berjon wrote: > > Hi, > > a new ED of WARP is up, including the following changes based upon prior > discussion: > > - a new, nicer name > - better definitions > - more fleshed ou requirements > - more detailed policy > - fixes to the element definition > - fixes to the processing model > - better acknowledgements > > Share and Enjoy at http://dev.w3.org/2006/waf/widgets-access/ > > -- > Robin Berjon - http://berjon.com/ > Feel like hiring me? Go to http://robineko.com/ > > > > > >
New draft of Widgets: Access Requests Policy
Hi, a new ED of WARP is up, including the following changes based upon prior discussion: - a new, nicer name - better definitions - more fleshed ou requirements - more detailed policy - fixes to the element definition - fixes to the processing model - better acknowledgements Share and Enjoy at http://dev.w3.org/2006/waf/widgets-access/ -- Robin Berjon - http://berjon.com/ Feel like hiring me? Go to http://robineko.com/
