Re: [YANG] new pyang errors

Phil Shafer <phil@juniper.net> Sun, 20 January 2008 17:39 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 1JGe93-0003fG-U3; Sun, 20 Jan 2008 12:39:45 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JGe93-0003fB-5W for yang-confirm+ok@megatron.ietf.org; Sun, 20 Jan 2008 12:39:45 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JGe92-0003f2-RC for yang@ietf.org; Sun, 20 Jan 2008 12:39:44 -0500
Received: from exprod7og104.obsmtp.com ([64.18.2.161]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JGe92-0004wy-BH for yang@ietf.org; Sun, 20 Jan 2008 12:39:44 -0500
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP; Sun, 20 Jan 2008 09:39:40 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Sun, 20 Jan 2008 09:38:48 -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 m0KHcl941739; Sun, 20 Jan 2008 09:38:47 -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 m0KHcXNw001798; Sun, 20 Jan 2008 17:38:33 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801201738.m0KHcXNw001798@idle.juniper.net>
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [YANG] new pyang errors
In-reply-to: <479243FA.1010008@andybierman.com>
Date: Sun, 20 Jan 2008 12:38:33 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 20 Jan 2008 17:38:48.0122 (UTC) FILETIME=[500621A0:01C85B8B]
X-Spam-Score: 0.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

Andy Bierman writes:
>Q1: Is the leaf mandatory?
>  Yes:  Q2: Is there a default-stmt for the leaf, or if not, is there
>            a default-stmt for the typedef used by the leaf?
>          No: missing mandatory data error
>         Yes: use the default value to instantiate the leaf node

If there's a reasonable default for the node, why would you mark it
as mandatory?  If there's a default, no one needs to create the
statement and is doesn't need to exist in the database.

What you are doing here is trying to make the meaning of mandatory
conditional based on the presence of a default.  This is confusing.

If something is mandatory, it must exist.  If there's a default,
it need not exist, since the default gives the value.  Making
the agent/manager/user/implementor ask your Q1 and Q2 is unnecessary.
The question is simply "does it exist?".  If it's mandatory and it
doesn't exist, it's an error.

Thanks,
 Phil


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