I don't know how to make editorial changes to the spec. So here's the thread from a year or so ago, suggesting that OP responses containing Key-Value Form encoding include a content-type header of application/x-openid-kvf rather than text/plain or whatever else OPs might arbitrarily choose.<div>
<br clear="all">--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
<br><br><div class="gmail_quote">On Fri, Jun 13, 2008 at 5:48 PM, Peter Williams <span dir="ltr"><<a href="mailto:pwilliams@rapattoni.com">pwilliams@rapattoni.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Make an editorial change to a spec, and submit for formal consideration to the spec list. Need be only 2 lines long, and the std iana declaration. Nobody recalls emails.<br>
<br>
________________________________<br>
From: Andrew Arnott <<a href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a>><br>
Sent: Friday, June 13, 2008 5:45 PM<br>
<div class="im">To: OpenID List <<a href="mailto:general@openid.net">general@openid.net</a>><br>
</div>Subject: Re: [OpenID] Content-Type for Key-Value Form response from OP<br>
<div class="im"><br>
Unless I hear any objection then, I'm going to code up my library to respond with application/x-openid-kvf as the content-type for Key-Value Form encoded messages.<br>
<br>
Thanks for the help coming up with this, Martin.<br>
<br>
Andrew Arnott<br>
<br>
</div><div class="im">On Wed, Jun 11, 2008 at 4:59 PM, Andrew Arnott <<a href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a><mailto:<a href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a>>> wrote:<br>
(Forwarding to entire list since I hit Reply instead of Reply All).<br>
<br>
<br>
Thanks, Martin. It sounds like application/x-kvf is better than text/kvf then. Perhaps we can also be more descriptive then as say "application/x-openid-kvf"?<br>
<br>
Andrew Arnott<br>
<br>
</div><div class="im">On Wed, Jun 11, 2008 at 1:48 PM, Martin Atkins <<a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</a><mailto:<a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</a>>> wrote:<br>
Andrew Arnott wrote:<br>
> In that case, I move that we adopt text/kvf as the official Content-Type<br>
> for Key-Value Form encoding response messages.<br>
><br>
<br>
Hi Andrew,<br>
<br>
Sorry I didn't see your messages until now.<br>
<br>
I believe the convention for unregistered MIME types is to prefix the<br>
subtype part with "x-", giving something like text/x-kvf.<br>
<br>
However, since the spec mandates UTF-8 for this message format, it may<br>
be more appropriate to use an "application/" type; text types generally<br>
support a "charset" attribute allowing the content to be in an arbitrary<br>
character encoding, which is not appropriate here.<br>
<br>
_______________________________________________<br>
general mailing list<br>
</div><a href="mailto:general@openid.net">general@openid.net</a><mailto:<a href="mailto:general@openid.net">general@openid.net</a>><br>
<div><div></div><div class="h5"><a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>