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

Will Norris <will@willnorris.com> Sat, 12 October 2013 23:57 UTC

Return-Path: <wnorris@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 D935A21F9926 for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 16:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Level:
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[AWL=0.100, 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 Bo-6+jxdLjsz for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 16:57:16 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id CAC9321E805D for <webfinger@ietf.org>; Sat, 12 Oct 2013 16:57:15 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id x13so12115564ief.29 for <webfinger@ietf.org>; Sat, 12 Oct 2013 16:57:15 -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=wBhse0p3cnTgwNMZC4zCPsFWhVaMubUiIc1oncm1I40=; b=SqRCMNS3kSSufB8BN6IYs82yNwNpXBhYx3EodDQacjU5W+swnsK8ecM3ijhHLP+vb8 2G1YHyd+R9TTuRdxvdaBVfFuIxHlCiktkaqlBKrGOqaqWNgaL2Ao5p1DbWTITNp8A24u uCk/A3HbOvML26q699WJXFtO/h06sS/i08JpeCP4FaFOnetYplBHbqJo19xN3Pbc8zqB EYRPx6eb5MrAcI9CTbXKVHsKbRLir3gzr0RY94zmTyRf2tdZpV+dnls5CeFM52SmMV0s JYoYvFk+HEuw2Cgv/9eDfr0XvVirY1fc8v1JPWRCf3BbIzz4rAb8RC9XYLPPG7n+XWa3 vYlA==
X-Received: by 10.43.73.197 with SMTP id yt5mr16156804icb.0.1381622235065; Sat, 12 Oct 2013 16:57:15 -0700 (PDT)
MIME-Version: 1.0
Sender: wnorris@gmail.com
Received: by 10.64.7.50 with HTTP; Sat, 12 Oct 2013 16:56:44 -0700 (PDT)
In-Reply-To: <CANBOYLVeYj92uqThONmh9VD+NWZp1qMk6J4S+B9HyK51erTkxA@mail.gmail.com>
References: <CANBOYLU4q_BFZEAB21AQ-s6HZaDDY4trRY97pkVWoyrYNBfMfA@mail.gmail.com> <CAKaEYhLH=EgD8KuGL7OJOu_NygP+9qX29i+Bcz6dODWv_rMmOg@mail.gmail.com> <CANBOYLVeYj92uqThONmh9VD+NWZp1qMk6J4S+B9HyK51erTkxA@mail.gmail.com>
From: Will Norris <will@willnorris.com>
Date: Sat, 12 Oct 2013 16:56:44 -0700
X-Google-Sender-Auth: iFsYMJb6PFRufJjcwfZR4vH_msA
Message-ID: <CAJqAn3y4i3dph=3q-O_CRT6TD=r7pceLGkG4n+JptBqGuxBrjQ@mail.gmail.com>
To: Eric Mill <eric@konklone.com>
Content-Type: multipart/alternative; boundary=001a11c2190a88f79004e893fedf
Cc: "webfinger@ietf.org" <webfinger@ietf.org>, webfinger@googlegroups.com
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: Sat, 12 Oct 2013 23:57:17 -0000

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