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

"Paul E. Jones" <paulej@packetizer.com> Sun, 13 October 2013 00:35 UTC

Return-Path: <paulej@packetizer.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 B734C21E8098 for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 17:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level:
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=0.294, BAYES_00=-2.599, HTML_MESSAGE=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 6JAwsP6gdz5e for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 17:35:25 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id B3F8C11E8171 for <webfinger@ietf.org>; Sat, 12 Oct 2013 17:35:24 -0700 (PDT)
Received: from [192.168.1.20] (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r9D0ZNHv021707 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <webfinger@ietf.org>; Sat, 12 Oct 2013 20:35:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1381624523; bh=41vvSa03ifm4qfYzfTSxI//YaLi7miYTEfLzMXbP+xs=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type; b=QgSFAO1H0SbYPfw3Ph3vwiv7Ja+IFQq8YN05ojf7JEfutmR4Lq/lLGTRh5u+qLR0k 5hQy+rMn2NWrVhqfSUOKpN3Eg7Y55Ge56n8y8NnyUAXoBwXa1nxFkefocjVqbbJEI9 kav61AzxyVpoL8sSgwKmj9L9tOdpB13IU53jL9oE=
Message-ID: <5259EADA.1050601@packetizer.com>
Date: Sat, 12 Oct 2013 20:35:38 -0400
From: "Paul E. Jones" <paulej@packetizer.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: webfinger@ietf.org
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>
In-Reply-To: <CAJqAn3y4i3dph=3q-O_CRT6TD=r7pceLGkG4n+JptBqGuxBrjQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080406040006040403070402"
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 00:35:29 -0000

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 
> <mailto: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 <mailto:melvincarvalho@gmail.com>> wrote:
>
>
>
>
>         On 13 October 2013 00:28, Eric Mill <eric@konklone.com
>         <mailto: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 <http://konklone.com> | @konklone
>             <https://twitter.com/konklone>
>
>             _______________________________________________
>             webfinger mailing list
>             webfinger@ietf.org <mailto: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
>         <mailto:webfinger%2Bunsubscribe@googlegroups.com>.
>         For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>     -- 
>     konklone.com <http://konklone.com> | @konklone
>     <https://twitter.com/konklone>
>
>     _______________________________________________
>     webfinger mailing list
>     webfinger@ietf.org <mailto:webfinger@ietf.org>
>     https://www.ietf.org/mailman/listinfo/webfinger
>
>
>
>
> _______________________________________________
> webfinger mailing list
> webfinger@ietf.org
> https://www.ietf.org/mailman/listinfo/webfinger