Re: [OAUTH-WG] [apps-discuss] Web Finger vs. Simple Web Discovery (SWD)

Tim Bray <tbray@textuality.com> Sat, 21 April 2012 19:27 UTC

Return-Path: <tbray@textuality.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A003121F8598 for <oauth@ietfa.amsl.com>; Sat, 21 Apr 2012 12:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.066
X-Spam-Level:
X-Spam-Status: No, score=-3.066 tagged_above=-999 required=5 tests=[AWL=-0.689, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1]
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 lqz6RffIotdk for <oauth@ietfa.amsl.com>; Sat, 21 Apr 2012 12:26:59 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A246A21F857D for <oauth@ietf.org>; Sat, 21 Apr 2012 12:26:59 -0700 (PDT)
Received: by obbwd20 with SMTP id wd20so11003037obb.31 for <oauth@ietf.org>; Sat, 21 Apr 2012 12:26:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=kfvVYONDB88l0xkjDZL0SwT+s0VmIqgPhG3ydNneKD8=; b=Y7api0viv5F1mvXTutwIINM2+KME7UXzKOpaZnz5WONxnnIX1OnuN+wJMfmb7QzXug ULyjNpAU/kJE/xi8L7D/LninaOtgadpDKG7NsIkCAAb4TFjj52vJvMu/EW7/Q9rvZcJb p8WHw16JBDFwqL4mla/zWI+3SK2VbW+28juV1+lzDZ4X1cKxEyas2vQHri/vaUL/ye8N u42y2O5aEz+cLn5J+qPxCDMZ26I/ujLlad7z487diePr5Q8qeWisfUHyd9q2SN9ZWctH dDZJkFwYxyZPd5Kup/JL6gwyFHNdlAHqfgiC+n9okRNgnJY3wFBjS1jUrwARksbyO4BC jfAA==
MIME-Version: 1.0
Received: by 10.60.7.103 with SMTP id i7mr9346188oea.64.1335036419066; Sat, 21 Apr 2012 12:26:59 -0700 (PDT)
Received: by 10.182.204.71 with HTTP; Sat, 21 Apr 2012 12:26:59 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <CAA1s49UEksuH-yj2wAdRgYu--zh+hJ4_UenJaaMASK-SDFAWtg@mail.gmail.com>
References: <423611CD-8496-4F89-8994-3F837582EB21@gmx.net> <4F8852D0.4020404@cs.tcd.ie> <9452079D1A51524AA5749AD23E0039280EFE8D@exch-mbx901.corp.cloudmark.com> <sjm1unn338j.fsf@mocana.ihtfp.org> <9452079D1A51524AA5749AD23E0039280FACC3@exch-mbx901.corp.cloudmark.com> <4E1F6AAD24975D4BA5B168042967394366490B2A@TK5EX14MBXC284.redmond.corp.microsoft.com> <091401cd1ea3$e159be70$a40d3b50$@packetizer.com> <CAHBU6it3ZmTdK-mTwydXSRvGvZAYuv0FFR2EWLwdfTxQh4XV5g@mail.gmail.com> <091901cd1eb0$167a8ce0$436fa6a0$@packetizer.com> <sjmbommzdv4.fsf@mocana.ihtfp.org> <4F917545.5080103@mtcc.com> <4F921E53.8030109@cs.tcd.ie> <CAA1s49UEksuH-yj2wAdRgYu--zh+hJ4_UenJaaMASK-SDFAWtg@mail.gmail.com>
Date: Sat, 21 Apr 2012 12:26:59 -0700
Message-ID: <CAHBU6itqu3BeZJEynMLJ=z2V-fwsnEVtdBo9u9vBkXyC2A8OeA@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Bob Wyman <bob@wyman.us>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmp/AjaHgL3NpPq613tgMT8Lft6LUXnCeR3BTWkmY7kv+uhN2ClzmlhJMhXhyQ/NW7apgLQ
Cc: Derek Atkins <derek@ihtfp.com>, oauth@ietf.org, Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [OAUTH-WG] [apps-discuss] Web Finger vs. Simple Web Discovery (SWD)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2012 19:27:03 -0000

That might have happened had there been some free high-quality ASN.1
software, instead of slow buggy parsers that cost $50K to license.
It’s always seemed to me that one reason XML took off so fast is that
there were fast robust open-source parsers in C and Java before the
spec was even finalized.

But we digress... -T

On Sat, Apr 21, 2012 at 10:14 AM, Bob Wyman <bob@wyman.us> wrote:
>
>
> On Fri, Apr 20, 2012 at 10:41 PM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
>>
>>
>>
>> On 04/20/2012 03:40 PM, Michael Thomas wrote:
>> >
>> > Why not MUST ASN.1 while you're at it? JSON has won in case
>> > you'all haven't noticed it.
>>
>> Well, I also remember when XML won over ASN.1, or
>> was that some RPC thing?
>
> Of course, long before "XML won over ASN.1" ASN.1 won over XML's
> predecessor; SGML. Back in the early to mid-80's, when we were defining the
> ISO X.4xx and X.5xx standards, the IBM and Unix crowds were pushing SGML as
> the alternative to the binary encodings of ASN.1. But, Digital and the
> Telcos pushed for the binary encodings and won.
>
> These days, XML is just another encoding for ASN.1 since ASN.1 finally
> defined the XML Encoding Rules (XER) a few years back.
>
> If we had agreed on ASN.1 years ago, we wouldn't be having these encoding
> format debates every few years. ASN.1 is an "Abstract Syntax Notation" that
> can be mapped to a large number of encoding rules. If we were using ASN.1,
> what we would do is define the "schema" or syntax for data abstractly and
> then specify the actual encoding as a secondary issue. Given that one
> encoding can be translated to another, implementations would be free to use
> whatever encoding was most convenient or appropriate for them. But, that
> would be a different universe than the one we live in today.
>
>> Seems like a new format wins
>> about every five years or so, once the last winner
>> gets enough crap added. (JSON pointer seems like the
>> start of a nice slippery slope to me.)
>>
>> I've no opinion as to what should be MTI here however,
>> just a side comment.
>>
>> S
>>
>> >
>> > Mike
>> > _______________________________________________
>> > apps-discuss mailing list
>> > apps-discuss@ietf.org
>> > https://www.ietf.org/mailman/listinfo/apps-discuss
>> >
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>