Re: Straw-man charter

Anne van Kesteren schrieb:
>> I think I strongly disagree. Requiring that things are indeed 
>> completely implemented will either result in lots of stuff being taken 
>> out, or the spec never be done.
> 
> If that's indeed the result something is clearly wrong with the current 
> specification. What's the use of a specification which authors and 
> implementors can't actually rely on?

That's the debate about whether to spec what people *should* do as 
opposed to what they do today. I disagree that it's useless to specify 
things even though existing implementations may get it wrong.

There's a problem if the spec defines something as mandatory, and nobody 
does it. Or if the spec says something that can't be implemented. Things 
like these should be discussed, agreed.

>> So what *are* the real issues, then? Have they been raised over here?
> 
> I raised one (which was quickly rejected even though multiple people 
> indicated it could not be implemented...), but there are others. Such as 

That would be 
<http://lists.w3.org/Archives/Public/ietf-http-wg/2006OctDec/thread.html#msg224>, 
right? I wouldn't say it was rejected altogether, it's just that there 
was no agreement that Content-Location can be removed completely.

> redirection of a POST as a GET etc. I'm not aware of a full list though, 
> but such a list would probably become apparent once you start doing 
> actual testing.

Is that about status 302 vs 303? Is there an open issue around here?

Best regards, Julian