Re: [rrg] belated msg: further description of the recommendation process

Lixia Zhang <lixia@cs.ucla.edu> Tue, 15 December 2009 06:31 UTC

Return-Path: <lixia@cs.ucla.edu>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 721193A67AE for <rrg@core3.amsl.com>; Mon, 14 Dec 2009 22:31:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level:
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085, 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 cBFGx7n4SY95 for <rrg@core3.amsl.com>; Mon, 14 Dec 2009 22:31:35 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 976D93A6950 for <rrg@irtf.org>; Mon, 14 Dec 2009 22:31:05 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id B6A4639E80D9; Mon, 14 Dec 2009 22:30:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NybWX6iBWLSZ; Mon, 14 Dec 2009 22:30:52 -0800 (PST)
Received: from [10.0.1.3] (cpe-98-151-23-234.socal.res.rr.com [98.151.23.234]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 52CD839E807B; Mon, 14 Dec 2009 22:30:52 -0800 (PST)
Message-Id: <038E0D74-27E8-480C-8CD8-664487B52CCE@cs.ucla.edu>
From: Lixia Zhang <lixia@cs.ucla.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4B26FB62.9020903@gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 14 Dec 2009 22:30:51 -0800
References: <20091214214323.93DE66BE562@mercury.lcs.mit.edu> <4B26FB62.9020903@gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: rrg@irtf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [rrg] belated msg: further description of the recommendation process
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2009 06:31:36 -0000

On Dec 14, 2009, at 6:58 PM, Brian E Carpenter wrote:
> ......
>
>>
>> Or, at least, that's my theory - and I'm sticking to it! :-)
>>
>>> Also I feel it should support hierarchy, even if we don't need a
>>> hierarchy from the start.
>>
>> Hierarchy in the names in the namespaces, or a hierarchy _of_  
>> namespaces?
>> Sorry, wasn't quite clear from your brief comment.
>
> I was thinking about a hierarchy of namespaces, but in fact we  
> probably
> need the generality to support hierarchical names too. I don't think  
> that
> needs to make the simple case inefficient. Just make a couple of the  
> basic
> data definitions recursive, and you've got both hierarchies.
>
>   Brian

a clarification question: wonder what is the "name space" referred to  
in the above?

Lixia