Re: [apps-discuss] APPSDIR review of draft-gregorio-uritemplate-07

Mark Nottingham <mnot@mnot.net> Sat, 10 December 2011 22:39 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029D521F8B3B for <apps-discuss@ietfa.amsl.com>; Sat, 10 Dec 2011 14:39:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.099
X-Spam-Level:
X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 mVrklvlMmASJ for <apps-discuss@ietfa.amsl.com>; Sat, 10 Dec 2011 14:39:52 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 4677921F8AF8 for <apps-discuss@ietf.org>; Sat, 10 Dec 2011 14:39:52 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.121.109]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4D1F150A64; Sat, 10 Dec 2011 17:39:50 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4EE3DD12.6000001@stpeter.im>
Date: Sun, 11 Dec 2011 09:39:41 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3C3FDC2-7ED5-4D72-91FD-A2BEDB09D8E3@mnot.net>
References: <89527141FD764100A4B43FEDBC6E027F@LENOVO47E041CF> <A253E377-4588-4A50-B837-8FE2E5082F15@mnot.net> <583806B95F08410DBEFE3E04E79D28A4@LENOVO47E041CF> <39251BD7-21FD-48C4-A128-B578AD39D83D@mnot.net> <4EE263C9.6060003@stpeter.im> <157FF90B-4A31-467B-BA78-05D123F73763@mnot.net> <4EE3DD12.6000001@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1251.1)
Cc: IETF Apps Discuss <apps-discuss@ietf.org>, draft-gregorio-uritemplate.all@tools.ietf.org
Subject: Re: [apps-discuss] APPSDIR review of draft-gregorio-uritemplate-07
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Dec 2011 22:39:53 -0000

Yes. I ended up splitting it into two paragraphs, with the new sentence as the first (due to the combined length).

Cheers,


On 11/12/2011, at 9:28 AM, Peter Saint-Andre wrote:

> On 12/10/11 3:15 PM, Mark Nottingham wrote:
>> 
>> On 10/12/2011, at 6:38 AM, Peter Saint-Andre wrote:
>> 
>>>  URI Templates provide a mechanism for abstracting a space of resource
>>>  identifiers such that the variable parts can be easily identified and
>>>  described.  URI templates can have many uses, including discovery of
>>>  available services, configuring resource mappings, defining computed
>>>  links, specifying interfaces, and other forms of programmatic
>>>  interaction with resources.  For example, the above resources could
>>>  be described by the following URI templates:
>> 
>> Seems workable to me.
> 
> To be clear, I suggested:
> 
>   A URI Template is a compact sequence of characters for describing a
>   range of Uniform Resource Identifiers through variable expansion.
>   URI Templates provide a mechanism for abstracting a space of resource
>   identifiers such that the variable parts can be easily identified and
>   described.  URI templates can have many uses, including discovery of
>   available services, configuring resource mappings, defining computed
>   links, specifying interfaces, and other forms of programmatic
>   interaction with resources.  For example, the above resources could
>   be described by the following URI templates:
> 
> (where the first sentence is copied from the Abstract...)
> 
> 

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