Re: #186: Document HTTP's error-handling philosophy

On 24/05/2011, at 4:39 PM, Julian Reschke wrote:

>>>> 
>>>> Note that this removes the "conditionally compliant" level of conformance; i.e., SHOULD is no longer overloaded, and returns to is original RFC2119 semantic of identifying requirements that can be violated for reasonable reasons (see also<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/271>, which proposes that we try to enumerate those reasons wherever possible).
>>>> 
>>>> That's a fairly big change. I'd argue that "conditional compliance" doesn't promote interop and should be dropped. Thoughts?
>>> 
>>> It *is* a big change, and getting all the changes done right will be quite some work.
>> 
>> 
>> Yes, but I think it's worth doing. I'm willing to do the bulk of the review and suggestions, if people are willing to review them.
> 
> Will do :-)

Also, I think the tasks are separable -- i.e., we can change the "conditional compliance" language and then do a separate audit of the SHOULDs to make sure they're sensible / contextualised.

Regards,


--
Mark Nottingham   http://www.mnot.net/

Received on Friday, 27 May 2011 05:16:54 UTC