On Jan 4, 2008, at 2:37 PM, ext David Orchard wrote:

> I'll ask the Mark Nottingham question, where is the requirements doc
> that the WG has agreed to?  Such a document would help answer these
> kinds of issues quickly, and if there isn't documented agreement then
> these kinds of questions are bound to continue happening.
> I looked at the charter
> ( to see if I  
> could
> find any guidance there but didn't even find the work listed in the
> deliverables.  Which surprised me somewhat.

You're right David, this doc was not included in the WG's original  
Charter. [Work on this spec started in a Task Force of the WAF WG as  
a joint effort between the Voice Browser WG, the Web API WG and the  
WAF WG and was Chaired by Brad Porter. Formal work began after the  
W3C Team completed a "Project Review" [Project-Review] (sorry but  
Member-only access) in April '06. After Brad left Tellme in the  
spring of '07, the TF was dissolved and the WAF WG "proper" took over  
the work.]

Anyhow, as is now documented as ISSUE-19, there is a need for  
explicit requirements, etc. and I agree that without such  
documentation there will continue to be questions and confusion about  
the specs requirements, etc.

Regards, AB

[Project-Review] <>

> <snip/>
>> One of our requirements is that you can simply put a file on
>> the server and have it work. Also in the case where you can't
>> configure HTTP headers.
>> The protocol should also work consistently which is why GET
>> is also used for the authorization request so the entity body
>> is taken into account there as well. Given that servers
>> opt-in to all of this and sites are unlikely to just make
>> random cross-site requests it is unlikely you get a very
>> large response.
> <snip/>
>> --
>> Anne van Kesteren
>> <>
>> <>
> Cheers,
> Dave

Received on Friday, 4 January 2008 19:54:48 UTC