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

Eric Mill <eric@konklone.com> Sat, 12 October 2013 22:59 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 BD69721F9998 for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 15:59:12 -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 1RLjPK3YwAgR for <webfinger@ietfa.amsl.com>; Sat, 12 Oct 2013 15:59:12 -0700 (PDT)
Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id BBCB021F9A40 for <webfinger@ietf.org>; Sat, 12 Oct 2013 15:59:09 -0700 (PDT)
Received: by mail-ee0-f54.google.com with SMTP id e53so2640654eek.13 for <webfinger@ietf.org>; Sat, 12 Oct 2013 15:59:08 -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=gRMApspyp/tWEp6mvuY2d1C06yE9RjDJ4rbXZfqDsZk=; b=bYbhWFiaUefdDqtiplz86yDc02pQvZ+x/RMhCiyXTZcY/SJcSLdoG/2jfz+8UwxUYX JZkq1tfsV83los8YjH+klt2wO/9afeQYfjHEvkJitBiJ7dJOLtn3xCKOL7cCdahmpW8y CykF7Rx+iD2Zm1vl2nRdyQF/LXtFLsn3LO61b/9pEyWu0alkplsyvqpzYvX1HwfRC2ed qPLHx0nHE8xINzUBqEBuhlxduAHOBJAkLq2NjOF0Xz1AcQ747CyiF2p9zxUH1cToWmlD 4e4wZqA9KhB8oydYbORY0fzINs2OpbLWyznrCyQFp2WqRgHEAwPqpvWNq4xMeXiYxOI0 9NWA==
X-Received: by 10.14.107.68 with SMTP id n44mr42321300eeg.26.1381618748845; Sat, 12 Oct 2013 15:59:08 -0700 (PDT)
MIME-Version: 1.0
Sender: konklone@gmail.com
Received: by 10.223.167.69 with HTTP; Sat, 12 Oct 2013 15:58:28 -0700 (PDT)
In-Reply-To: <CAKaEYhLH=EgD8KuGL7OJOu_NygP+9qX29i+Bcz6dODWv_rMmOg@mail.gmail.com>
References: <CANBOYLU4q_BFZEAB21AQ-s6HZaDDY4trRY97pkVWoyrYNBfMfA@mail.gmail.com> <CAKaEYhLH=EgD8KuGL7OJOu_NygP+9qX29i+Bcz6dODWv_rMmOg@mail.gmail.com>
From: Eric Mill <eric@konklone.com>
Date: Sat, 12 Oct 2013 18:58:28 -0400
X-Google-Sender-Auth: PZiVxLqTIjzYHpSyQDyE5aq-P38
Message-ID: <CANBOYLVeYj92uqThONmh9VD+NWZp1qMk6J4S+B9HyK51erTkxA@mail.gmail.com>
To: webfinger@googlegroups.com
Content-Type: multipart/alternative; boundary=001a11c29ad2bd74ca04e8932e3e
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: Sat, 12 Oct 2013 22:59:12 -0000

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