Re: [YANG] so many naming scopes

Phil Shafer <phil@juniper.net> Tue, 08 January 2008 22:40 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 1JCN7o-0004jQ-4i; Tue, 08 Jan 2008 17:40:48 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JCN7m-0004jK-GB for yang-confirm+ok@megatron.ietf.org; Tue, 08 Jan 2008 17:40:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCN7m-0004jC-6X for yang@ietf.org; Tue, 08 Jan 2008 17:40:46 -0500
Received: from exprod7og109.obsmtp.com ([64.18.2.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCN7l-0001k8-Ps for yang@ietf.org; Tue, 08 Jan 2008 17:40:46 -0500
Received: from source ([66.129.224.36]) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP; Tue, 08 Jan 2008 14:40:30 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 8 Jan 2008 14:34:25 -0800
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m08MYO907136; Tue, 8 Jan 2008 14:34:24 -0800 (PST) (envelope-from phil@idle.juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m08MUP3O095222; Tue, 8 Jan 2008 22:30:28 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801082230.m08MUP3O095222@idle.juniper.net>
To: "tom.petch" <cfinss@dial.pipex.com>
Subject: Re: [YANG] so many naming scopes
In-reply-to: <011a01c851d8$cc8652c0$0601a8c0@pc6>
Date: Tue, 08 Jan 2008 17:30:25 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 08 Jan 2008 22:34:25.0135 (UTC) FILETIME=[9F2687F0:01C85246]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: yang@ietf.org
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

"tom.petch" writes:
>There are languages where no word is reserved, where the same symbol(word) can
>be used for label, type, module etc.  XML is arguable worse with the ability to
>start a fresh namespace on alternate lines.  These belong in the bin.

That's a very strong statement, given that the motivation for
avoiding reserved words is typically future proofing.  Don't paint
it as a universally bad feature.

For example, if I use "action" as a leaf in my model and the next
version of YANG adds a feature that uses "action" as a keyword, my
model is broken and needs repair.

Many languages reserve unused keywords just on the odds they will
need them in the future, but they are seldom right.  By keeping the
namespace of user-defined stuff out of the namespace of keywords,
YANG avoids this issue entirely.  As the number of modules defined
in YANG approaches the number that are defined in SMI, this will be
an important language feature.

Thanks,
 Phil


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