Re: [YANG] keyref

Phil Shafer <phil@juniper.net> Wed, 23 January 2008 04:00 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 1JHWma-00032s-00; Tue, 22 Jan 2008 23:00:12 -0500
Received: from yang by megatron.ietf.org with local (Exim 4.43) id 1JHWmY-00032j-91 for yang-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 23:00:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHWmX-00031h-TG for yang@ietf.org; Tue, 22 Jan 2008 23:00:09 -0500
Received: from exprod7og105.obsmtp.com ([64.18.2.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHWmV-0000aH-Fa for yang@ietf.org; Tue, 22 Jan 2008 23:00:09 -0500
Received: from source ([66.129.224.36]) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP; Tue, 22 Jan 2008 19:59:59 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Jan 2008 19:59:02 -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 m0N3wu975957; Tue, 22 Jan 2008 19:59:02 -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 m0N3wsub017849; Wed, 23 Jan 2008 03:58:54 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801230358.m0N3wsub017849@idle.juniper.net>
To: Andy Bierman <ietf@andybierman.com>
Subject: Re: [YANG] keyref
In-reply-to: <479607AD.2040205@andybierman.com>
Date: Tue, 22 Jan 2008 22:58:54 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 23 Jan 2008 03:59:02.0684 (UTC) FILETIME=[4A7525C0:01C85D74]
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

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.

>IMO, the whole issue of relationships between config database nodes is larger
>than this keyref clause.  The requirements for machine readable
>object constraint languages and object/entity relationships needs to
>be documented in detail and agreed upon.

So you want this issue pushed onto the Requirements Team?  Or do
you want a distinct requirements effort for this?

Thanks,
 Phil


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