Re: [webfinger] Is application/json an acceptable content type for JRDs?

Eric Mill <eric@konklone.com> Sun, 13 October 2013 03:34 UTC

Return-Path: <konklone@gmail.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C55FC21F9193 for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 20:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srRarKkB0dSZ for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 20:34:17 -0700 (PDT)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id ABC3621E80AB for <webfinger@ietf.org>; Sat, 12 Oct 2013 20:34:15 -0700 (PDT)
Received: by mail-ea0-f177.google.com with SMTP id f15so2627999eak.22 for <webfinger@ietf.org>; Sat, 12 Oct 2013 20:34:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=nNNR9LpUGGwNqesjieBWfNYJA23E1gIQFyJI/UlcpOg=; b=bgFrIiTu86d2R3VOAfZU8/OPjwbw0rXW9haOq94cmnTiynWV2RsgbpasTm2TG8eFNk JkAtwkVSL7sAsngsJIrnpF08UxWpki+mZWZUlPUVgvWjNdjxHYpcXlRNVkBoXufTKQHP llMBxnswlTZYrUb9U+G9/y53+uTGitEiJFq/GCCTH+J0q7Hp6Ml+N4vTkIjB9m4eJBsP UnLyQkZ6B6HGEjeEM++EIZY2v6PqSuJRohgbUHW+0LgMbG5VmO02cPesovRFBdycVUge 0DYSSC8iRj6VSndi6VuwRyHGSxSpoVh67q+2nDeVsB8Xue6Hcr0+gogw5ozLKcsq71tY 8M1w==
X-Received: by 10.14.210.8 with SMTP id t8mr43066181eeo.39.1381635254704; Sat, 12 Oct 2013 20:34:14 -0700 (PDT)
MIME-Version: 1.0
Sender: konklone@gmail.com
Received: by 10.223.167.69 with HTTP; Sat, 12 Oct 2013 20:33:34 -0700 (PDT)
In-Reply-To: <5259EADA.1050601@packetizer.com>
References: <CANBOYLU4q_BFZEAB21AQ-s6HZaDDY4trRY97pkVWoyrYNBfMfA@mail.gmail.com> <CAKaEYhLH=EgD8KuGL7OJOu_NygP+9qX29i+Bcz6dODWv_rMmOg@mail.gmail.com> <CANBOYLVeYj92uqThONmh9VD+NWZp1qMk6J4S+B9HyK51erTkxA@mail.gmail.com> <CAJqAn3y4i3dph=3q-O_CRT6TD=r7pceLGkG4n+JptBqGuxBrjQ@mail.gmail.com> <5259EADA.1050601@packetizer.com>
From: Eric Mill <eric@konklone.com>
Date: Sat, 12 Oct 2013 23:33:34 -0400
X-Google-Sender-Auth: CAHrkXH0sw97ZUPka2wBaZPWNkw
Message-ID: <CANBOYLUyHumt74eX2XZ1wF=gpGANTFZ9Oa-u4ONqvse22zZ7ww@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: multipart/alternative; boundary=047d7b603fe290dfc304e897063b
Cc: "webfinger@ietf.org" <webfinger@ietf.org>
Subject: Re: [webfinger] Is application/json an acceptable content type for JRDs?
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Oct 2013 03:34:18 -0000

Good points/ideas. I opened a
ticket<https://github.com/bhollis/jsonview/issues/45>on the Firefox
JSONView issue tracker to handle *+json, and +1'd the pre-existing
thread<https://github.com/gildas-lormeau/JSONView-for-Chrome/issues/12#issuecomment-26210833>on
the Chrome JSONView tracker.


On Sat, Oct 12, 2013 at 8:35 PM, Paul E. Jones <paulej@packetizer.com>wrote;wrote:

>  Yeah, I think the "be conservative with what you send and liberal with
> what you accept" comes to play here, as with most protocols.  Servers are
> required to use application/jrd+json, but it's probably best if clients did
> not rely on that media type being returned.  Just try to parse it.  It
> either will or will not parse correctly.
>
> Paul
>
>
> On 10/12/2013 7:56 PM, Will Norris wrote:
>
> reading through some of the list archive (such as
> http://www.ietf.org/mail-archive/web/webfinger/current/msg00395.html and
> the rest of that thread), leads me to say that you *really* should use the
> correct mime type.  I agree that for clients they probably should not fail
> on application/json, but I certainly wouldn't rely on that behavior as a
> publisher.  I wonder how hard it would be to get JSONView updated to accept
> application/*+json in addition to application/json?
>
>
> On Sat, Oct 12, 2013 at 3:58 PM, Eric Mill <eric@konklone.com> wrote:
>
>> So if I'm writing a client, and I get an application/json Content Type,
>> it should fail? Since the spec doesn't seem to explicitly mandate this, and
>> the content *is* valid JSON, this seems a bit restrictive to me.
>>
>>
>> On Sat, Oct 12, 2013 at 6:40 PM, Melvin Carvalho <
>> melvincarvalho@gmail.com> wrote:
>>
>>>
>>>
>>>
>>>  On 13 October 2013 00:28, Eric Mill <eric@konklone.com> wrote:
>>>
>>>> I've been reading through the Webfinger spec, and it uses
>>>> application/jrd+json in all the examples, and describes the media type it's
>>>> registering -- but it never says whether or not a server using
>>>> application/json as a content type should fail or not.
>>>>
>>>>  I could potentially see some servers wishing to use application/json,
>>>> so that applications that are used for all kinds of JSON manipulation, like
>>>> JSONView, could properly pick up on it.
>>>>
>>>
>>>  My interpretation is that the server must set Mime Type
>>> application/jrd+json if it's serving JRD, which is the only mandatory
>>> serialization.  Previously there was an XML format (XRD) which is still in
>>> use in some places.
>>>
>>>
>>>>
>>>>  -- Eric
>>>>
>>>>  --
>>>>  konklone.com | @konklone <https://twitter.com/konklone>
>>>>
>>>>  _______________________________________________
>>>> webfinger mailing list
>>>> webfinger@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/webfinger
>>>>
>>>>
>>>   --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "WebFinger" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to webfinger+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>>   --
>>  konklone.com | @konklone <https://twitter.com/konklone>
>>
>> _______________________________________________
>> webfinger mailing list
>> webfinger@ietf.org
>> https://www.ietf.org/mailman/listinfo/webfinger
>>
>>
>
>
> _______________________________________________
> webfinger mailing listwebfinger@ietf.orghttps://www.ietf.org/mailman/listinfo/webfinger
>
>
>
> _______________________________________________
> webfinger mailing list
> webfinger@ietf.org
> https://www.ietf.org/mailman/listinfo/webfinger
>
>


-- 
konklone.com | @konklone <https://twitter.com/konklone>