Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt

James M Snell <jasnell@gmail.com> Sun, 23 December 2012 16:43 UTC

Return-Path: <jasnell@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 1C13621F8AA3 for <webfinger@ietfa.amsl.com>; Sun, 23 Dec 2012 08:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.287
X-Spam-Level:
X-Spam-Status: No, score=-2.287 tagged_above=-999 required=5 tests=[AWL=-1.438, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81-Kp3pitO1F for <webfinger@ietfa.amsl.com>; Sun, 23 Dec 2012 08:43:02 -0800 (PST)
Received: from mail-ia0-f177.google.com (mail-ia0-f177.google.com [209.85.210.177]) by ietfa.amsl.com (Postfix) with ESMTP id 0017421F8A8C for <webfinger@ietf.org>; Sun, 23 Dec 2012 08:43:01 -0800 (PST)
Received: by mail-ia0-f177.google.com with SMTP id u21so5426907ial.36 for <webfinger@ietf.org>; Sun, 23 Dec 2012 08:43:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0IB6I7xRDZRDokjNDzIt/Bv6ScZ9PHDPTO0+NOK+zgk=; b=peW0pjcCS5LyWy0eU1BvyCiwwI+nwfEA7pwOM+s0NSAfMvHHqlAGq5it+ATqquXhoM d6OGfqnYv3NL5vjEo0h93k+T31gwIqpeWwPrQomTRIjgat1EEQo/ZI4FR3N899KrVXUh 1Q7LVNVChYAkLNP0WX3RiS3TEIBnd0jf2SmCP5Mi75GiPq2ssuOQk+Ox3Mf0TdR4jOaS F1bvQFzthjFsClTWrsOaRXc5WJToLVBsrY8iTz0wykkjCeMflyje4zcy3mmKjwUV2asV FILH7BrNQTz5Bj1gpeB0SHuwjnLtlOtZPbW/nirhAGlcljs4j+smbU57uW9rpkgl5cJa aMNg==
Received: by 10.42.51.142 with SMTP id e14mr16045398icg.2.1356280980437; Sun, 23 Dec 2012 08:43:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Sun, 23 Dec 2012 08:42:40 -0800 (PST)
In-Reply-To: <alpine.OSX.2.00.1212231542050.68565@crank.local>
References: <20121221172032.28253.90788.idtracker@ietfa.amsl.com> <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com> <CAKaEYh+E6WBkw=HBVOb7H-kHNYTabY-GS3pmdRyMAJkeSOv1hg@mail.gmail.com> <CAHBU6iupJ9hc==wj8XVO5MUL6gnr57BgSbaLmrcTGds-6iYfkg@mail.gmail.com> <alpine.OSX.2.00.1212231542050.68565@crank.local>
From: James M Snell <jasnell@gmail.com>
Date: Sun, 23 Dec 2012 08:42:40 -0800
Message-ID: <CABP7RbfETkUBKvXeoHoffGFFjGV1+h2Hkg=0Xaig-YXmKD-YPA@mail.gmail.com>
To: chris.dent@gmail.com
Content-Type: multipart/alternative; boundary=20cf302239990df8c604d187c69c
Cc: "webfinger@ietf.org" <webfinger@ietf.org>
Subject: Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt
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, 23 Dec 2012 16:43:03 -0000

When it comes to JSON, because we don't have anything similar to a
namespace to key off of when parsing, a specific media type really does
help to determine if the server returned the right kind of JSON-based thing
in response to the query. I don't see a specific media type as being
critical in any way for WebFinger but it can be helpful if provided.


On Sun, Dec 23, 2012 at 7:54 AM, <chris.dent@gmail.com> wrote:

> On Sat, 22 Dec 2012, Tim Bray wrote:
>
>  I've also wondered why we don't have application/webfinger+json; seems to
>> me that having your own media-type is a strong Web best practice.  Has
>> this
>> been discussed?  -T
>>
>
> Can you point me to references to _why_ that is "best practice"?
>
> It's something I find quite annoying. It's application/json, being
> used in a webfinger context. In some other context it could be used
> for something else.
>
> In both contexts it is a JSON representation, you use JSON tools to
> process it.
>
> Having another media-type seems to just make things more noisy. Is the
> point to have some little agent sitting around being all smart because
> it can trigger imporant decision based merely on the media-type of its
> input? If that's so, I'm not sure I buy it: We wouldn't have gone to
> this resource in the first place if we weren't hoping to get webfinger
> info back.
>
> Help me understand.
>
> Thanks.
>
> --
> Chris Dent                                   http://burningchrome.com/
>                                 [...]
>
> ______________________________**_________________
> webfinger mailing list
> webfinger@ietf.org
> https://www.ietf.org/mailman/**listinfo/webfinger<https://www.ietf.org/mailman/listinfo/webfinger>
>