Re: [YANG] so many naming scopes

Phil Shafer <phil@juniper.net> Wed, 09 January 2008 17:33 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 1JCenU-0002OD-Ay; Wed, 09 Jan 2008 12:33:00 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JCenT-0002O5-35 for yang-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 12:32:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCenS-0002Nx-Pf for yang@ietf.org; Wed, 09 Jan 2008 12:32:58 -0500
Received: from exprod7og105.obsmtp.com ([64.18.2.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCenQ-0006gd-EZ for yang@ietf.org; Wed, 09 Jan 2008 12:32:58 -0500
Received: from source ([66.129.224.36]) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP; Wed, 09 Jan 2008 09:32:47 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jan 2008 09:32:34 -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 m09HWY980610; Wed, 9 Jan 2008 09:32:34 -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 m09HSgCF000847; Wed, 9 Jan 2008 17:28:42 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801091728.m09HSgCF000847@idle.juniper.net>
To: "tom.petch" <cfinss@dial.pipex.com>
Subject: Re: [YANG] so many naming scopes
In-reply-to: <012701c852d5$ff6ffc60$0601a8c0@pc6>
Date: Wed, 09 Jan 2008 12:28:41 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 09 Jan 2008 17:32:34.0833 (UTC) FILETIME=[9EFB8010:01C852E5]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
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:
>Yes, I expressed myself strongly, perhaps as a result of spending time in 2007
>with XML documents where there was widespread use of an element named <element>
>as well as one named <attribute>; I wish that XML had reserved those words:-(  I

That might sounds wise up until the moment when you need to define
XML for chemical elements (<element>helium</>) or character attributes
(<attribute>fluffy</>).  Forcing folks to choose non-obvious words
because the DML uses them is bad.  key and index are two examples
where the modeler should be able to use them if they are exactly
the term they need.

Thanks,
 Phil


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