[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openid-general
Subject:    [OpenID] Fwd:  Content-Type for Key-Value Form response from OP
From:       "Andrew Arnott" <andrewarnott () gmail ! com>
Date:       2008-06-11 23:59:49
Message-ID: 216e54900806111659l5c9688ffv88e4bc1f185c2e28 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


(Forwarding to entire list since I hit Reply instead of Reply All).

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"?

Andrew Arnott

On Wed, Jun 11, 2008 at 1:48 PM, Martin Atkins <mart@degeneration.co.uk>
wrote:

> Andrew Arnott wrote:
> > In that case, I move that we adopt text/kvf as the official Content-Type
> > for Key-Value Form encoding response messages.
> >
>
> Hi Andrew,
>
> Sorry I didn't see your messages until now.
>
> I believe the convention for unregistered MIME types is to prefix the
> subtype part with "x-", giving something like text/x-kvf.
>
> However, since the spec mandates UTF-8 for this message format, it may
> be more appropriate to use an "application/" type; text types generally
> support a "charset" attribute allowing the content to be in an arbitrary
> character encoding, which is not appropriate here.
>
> _______________________________________________
> general mailing list
> general@openid.net
> http://openid.net/mailman/listinfo/general
>

[Attachment #5 (text/html)]

(Forwarding to entire list since I hit Reply instead of Reply All).<br><div \
class="gmail_quote"><br>Thanks, Martin.&nbsp; It sounds like application/x-kvf is \
better than text/kvf then.&nbsp; Perhaps we can also be more descriptive then as say \
&quot;application/x-openid-kvf&quot;?<br clear="all"> <font \
color="#888888"><br>Andrew Arnott <br></font><div><div></div><div \
class="Wj3C7c"><br><div class="gmail_quote">On Wed, Jun 11, 2008 at 1:48 PM, Martin \
Atkins &lt;<a href="mailto:mart@degeneration.co.uk" \
target="_blank">mart@degeneration.co.uk</a>&gt; wrote:<br> <blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div>Andrew Arnott wrote:<br>
&gt; In that case, I move that we adopt text/kvf as the official Content-Type<br>
&gt; for Key-Value Form encoding response messages.<br>
&gt;<br>
<br>
</div>Hi Andrew,<br>
<br>
Sorry I didn&#39;t see your messages until now.<br>
<br>
I believe the convention for unregistered MIME types is to prefix the<br>
subtype part with &quot;x-&quot;, 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 &quot;application/&quot; type; text types generally<br>
support a &quot;charset&quot; attribute allowing the content to be in an \
arbitrary<br> character encoding, which is not appropriate here.<br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net" target="_blank">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" \
target="_blank">http://openid.net/mailman/listinfo/general</a><br> \
</blockquote></div><br> </div></div></div><br>



_______________________________________________
general mailing list
general@openid.net
http://openid.net/mailman/listinfo/general


[prev in list] [next in list] [prev in thread] [next in thread]