Re: [YANG] so many naming scopes

Balazs Lengyel <balazs.lengyel@ericsson.com> Thu, 10 January 2008 07:57 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 1JCsHl-000200-Mr; Thu, 10 Jan 2008 02:57:09 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JCsHj-0001xg-K6 for yang-confirm+ok@megatron.ietf.org; Thu, 10 Jan 2008 02:57:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCsHc-0001vM-JA for yang@ietf.org; Thu, 10 Jan 2008 02:57:00 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCsHc-0001pG-73 for yang@ietf.org; Thu, 10 Jan 2008 02:57:00 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 887E62180F for <yang@ietf.org>; Thu, 10 Jan 2008 08:56:59 +0100 (CET)
X-AuditID: c1b4fb3e-b1ea5bb00000459d-80-4785cfcb2ed0
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 6B33B217BD for <yang@ietf.org>; Thu, 10 Jan 2008 08:56:59 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 Jan 2008 08:56:59 +0100
Received: from [159.107.197.224] ([159.107.197.224]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 Jan 2008 08:56:59 +0100
Message-ID: <4785CFCA.4000506@ericsson.com>
Date: Thu, 10 Jan 2008 08:56:58 +0100
From: Balazs Lengyel <balazs.lengyel@ericsson.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: yang@ietf.org
Subject: Re: [YANG] so many naming scopes
References: <200801082230.m08MUP3O095222@idle.juniper.net> <012701c852d5$ff6ffc60$0601a8c0@pc6> <4784FD0D.6020103@andybierman.com> <20080109224627.GE5390@elstar.local>
In-Reply-To: <20080109224627.GE5390@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jan 2008 07:56:59.0140 (UTC) FILETIME=[6084B440:01C8535E]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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


Juergen Schoenwaelder wrote:
> Usage guidelines and "coding styles" are valuable. But they should not
> be part of the language itself. The example above is not ambiguous and
> easy to parse for a machine - even though it might look stupid to most
> humans.
> 
I think our yardstick should be whether the example is easy to understand for humans. "Easy for 
machine" is far from enough.

Balazs


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