On 2011-12-13 14:50, Cameron Heavon-Jones wrote:
Yes, but that's for the format. An Accept header of
Accept: text/html
doesn't tell the server *what* kind of HTML content you want (a status message
vs something that could be used as a next page in a user interaction).
I think that is quite definitely Out Of Scope. If there needs to be different
content for the same format this should be a different URI.
I disagree. If you need separate URIs to make this work, something is wrong.
Working towards a concrete proposal is the aim here. Since the bug has been
closed by the editor twice before i hesitate reopening it as it seems unable to
progress through this channel. Also as a substantial piece of specification i
think it will require full wg attention.
That we're half way through last call is fine, this has been raised as an issue
for a long time and it is in response to both wg and public feedback that it
has progressed to its current state. While there is work still to do, it is
limited in scope and i feel we are progressing well towards the solution.
I don't think browser adoption will be an issue here, chrome had some support
for PUT and DELETE however since its removal from the specification i'm unsure
on any current implementation. As HTML is not due for recommendation for years
it seems that browser vendors will still have plenty of time to implement
re-speced features.
Do you suggest any other means for this to progress other than escalation to an
issue?
...
We should try to come up with a complete proposal; as you see we aren't
there yet. Once we have that, we can either try to get it into HTML5 or
HTML.next, or write a separate delta spec.
Best regards, Julian
