Re: [YANG] keyref

Phil Shafer <phil@juniper.net> Wed, 23 January 2008 05:21 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 1JHY3f-0002jH-Ky; Wed, 23 Jan 2008 00:21:55 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHY3d-0002er-OS for yang-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 00:21:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHY3d-0002ej-EU for yang@ietf.org; Wed, 23 Jan 2008 00:21:53 -0500
Received: from exprod7og108.obsmtp.com ([64.18.2.169]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHY3d-0002MX-1k for yang@ietf.org; Wed, 23 Jan 2008 00:21:53 -0500
Received: from source ([66.129.224.36]) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP; Tue, 22 Jan 2008 21:21:07 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 22 Jan 2008 21:21:18 -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 m0N5LH996232; Tue, 22 Jan 2008 21:21:17 -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 m0N5LFGR019757; Wed, 23 Jan 2008 05:21:15 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801230521.m0N5LFGR019757@idle.juniper.net>
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [YANG] keyref
In-reply-to: <4796C299.7010706@andybierman.com>
Date: Wed, 23 Jan 2008 00:21:15 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 23 Jan 2008 05:21:18.0097 (UTC) FILETIME=[C8316810:01C85D7F]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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:
>Phil Shafer wrote:
>> Andy Bierman writes:
>>> IMO, leafref as a documentation clause does the same thing
>>> but way simpler.  The DM reader should not have to be an expert
>>> in Xpath, and need to hunt down the relevant documentation,
>>> just to find out a leaf's data type.
>> 
>> Are you saying you prefer this relationship to be defined in English
>> words instead of a formal language?  The "description" statement
>> for the leaf can provide the words, but we hope to provide something
>> that a generic manager implementation can use to process module
>> contents.
>
>I already made a proposal -- instead of a builtin type called keyref
>there would be an optional clause for a leaf of leaf-list called
>leafref that has the path-stmt from the keyref as its argument.

Your proposal called this a "documentation clause", which implies
something targeted to humans and not usable by software.  This
would be bad, but I would live with a distinct statement for the
ref target that is a formal target.

Thanks,
 Phil


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