Re: [ietf-outcomes] Apps area

Mark Nottingham <mnot@mnot.net> Wed, 10 February 2010 04:42 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: ietf-outcomes@core3.amsl.com
Delivered-To: ietf-outcomes@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B89B3A7513 for <ietf-outcomes@core3.amsl.com>; Tue, 9 Feb 2010 20:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.985
X-Spam-Level:
X-Spam-Status: No, score=-3.985 tagged_above=-999 required=5 tests=[AWL=-1.386, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id soc88CnIu+JY for <ietf-outcomes@core3.amsl.com>; Tue, 9 Feb 2010 20:42:04 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 60C723A6DBE for <ietf-outcomes@ietf.org>; Tue, 9 Feb 2010 20:42:04 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.89.188]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B29AF509B4; Tue, 9 Feb 2010 23:43:05 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4B6DB3B1.9080806@dcrocker.net>
Date: Wed, 10 Feb 2010 15:43:01 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FAF699B-2810-4B9E-B210-68C6C4C276FA@mnot.net>
References: <67F17703-EAFC-425B-BBFE-79ED2ED212AC@mnot.net> <4B6DB3B1.9080806@dcrocker.net>
To: dcrocker@bbiw.net, Dave CROCKER <dhc@dcrocker.net>
X-Mailer: Apple Mail (2.1077)
Cc: ietf-outcomes@ietf.org
Subject: Re: [ietf-outcomes] Apps area
X-BeenThere: ietf-outcomes@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Outcomes Wiki discussion list <ietf-outcomes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-outcomes>, <mailto:ietf-outcomes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-outcomes>
List-Post: <mailto:ietf-outcomes@ietf.org>
List-Help: <mailto:ietf-outcomes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-outcomes>, <mailto:ietf-outcomes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 04:42:05 -0000

I made one round of edits; I'm sure others will jump in and adjust my adjustments ;)

WRT URLs/URIs -- the common view in the Web world is that the terms are practically interchangeable. Perhaps this is because URNs really haven't caught on there (indeed, they're considered bad practice).

Cheers,


On 07/02/2010, at 5:23 AM, Dave CROCKER wrote:

> On 2/4/2010 4:29 PM, Mark Nottingham wrote:
>> A couple of thoughts on looking at the APPs area page:
>> 
>>  - URI is listed as '+'; surely that's '++>' (considering that people are now building URI-based protocols?)
> 
> I have to admit to my having a contnuing confusion about URL vs. URI, which makes it difficult for me to see whether the massive adoption is for URLs or is in fact for URIs.
> 
> 
>>  - HTTP is defined by RFC2616, not RFC2068
>> 
>> Anyone mind if I fix these and fill in a few other bits (e.g., for Atom)? I'm assuming the usual wiki terms of engagement apply, but wanted to make sure...
> 
> fix away, please!
> 
> d/
> 
> -- 
> 
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net


--
Mark Nottingham     http://www.mnot.net/