Re: [YANG] so many naming scopes

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 09 January 2008 23:24 UTC

Return-path: <yang-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCkHl-0004cX-2J; Wed, 09 Jan 2008 18:24:37 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JCkHk-0004cR-J0 for yang-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 18:24:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCkHk-0004cJ-90 for yang@ietf.org; Wed, 09 Jan 2008 18:24:36 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCkHj-0004BI-QK for yang@ietf.org; Wed, 09 Jan 2008 18:24:36 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4CA568A3A5; Thu, 10 Jan 2008 00:24:35 +0100 (CET)
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 14600-02; Thu, 10 Jan 2008 00:24:30 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 00BFB8A390; Thu, 10 Jan 2008 00:24:28 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id D6552460278; Thu, 10 Jan 2008 00:24:27 +0100 (CET)
Date: Thu, 10 Jan 2008 00:24:27 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [YANG] so many naming scopes
Message-ID: <20080109232427.GA5551@elstar.local>
Mail-Followup-To: Andy Bierman <ietf@andybierman.com>, "tom.petch" <cfinss@dial.pipex.com>, yang@ietf.org
References: <200801082230.m08MUP3O095222@idle.juniper.net> <012701c852d5$ff6ffc60$0601a8c0@pc6> <4784FD0D.6020103@andybierman.com> <20080109224627.GE5390@elstar.local> <4785530E.3080007@andybierman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4785530E.3080007@andybierman.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: yang@ietf.org
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Errors-To: yang-bounces@ietf.org

On Wed, Jan 09, 2008 at 03:04:46PM -0800, Andy Bierman wrote:

> Except that YANG has embedded coding style text already,
> such as the sentence about SHOULD NOT differ only in case.
> Names such as foo and Foo and perfectly valid.  There is
> no reason whatsoever to have this text, same as a CLR
> about not having grouping foo and typedef foo, other than
> to enforce a coding style.  (My suggestion was SHOULD, not MUST.)

So lets remove this "SHOULD NOT differ only in case" rule from the
language specification and lets start a guidelines document (or an
appendix for simplicity) where we collect such guidelines.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang