Re: [YANG] import statement

Ladislav Lhotka <lhotka@cesnet.cz> Sat, 03 May 2008 18:44 UTC

Return-Path: <yang-bounces@ietf.org>
X-Original-To: yang-archive@optimus.ietf.org
Delivered-To: ietfarch-yang-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45E683A6982; Sat, 3 May 2008 11:44:48 -0700 (PDT)
X-Original-To: yang@core3.amsl.com
Delivered-To: yang@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A1E93A693C for <yang@core3.amsl.com>; Sat, 3 May 2008 11:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level:
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id futwlRRXQyd4 for <yang@core3.amsl.com>; Sat, 3 May 2008 11:44:40 -0700 (PDT)
Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244]) by core3.amsl.com (Postfix) with ESMTP id AAC733A67F5 for <yang@ietf.org>; Sat, 3 May 2008 11:44:40 -0700 (PDT)
Received: from [172.29.2.201] (asus-gx.lhotka.cesnet.cz [195.113.161.161]) by office2.cesnet.cz (Postfix) with ESMTP id 6A815D800C5 for <yang@ietf.org>; Sat, 3 May 2008 20:44:41 +0200 (CEST)
From: Ladislav Lhotka <lhotka@cesnet.cz>
To: yang@ietf.org
In-Reply-To: <481C9D3E.1050602@andybierman.com>
References: <1209812833.14759.12.camel@missotis> <20080503120217.GA24899@elstar.local> <1209823237.14759.24.camel@missotis> <20080503143205.GA24972@elstar.local> <1209828663.14759.40.camel@missotis> <481C9D3E.1050602@andybierman.com>
Organization: CESNET
Date: Sat, 03 May 2008 20:44:41 +0200
Message-Id: <1209840281.14759.57.camel@missotis>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.1
Subject: Re: [YANG] import statement
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: yang-bounces@ietf.org
Errors-To: yang-bounces@ietf.org

Andy Bierman píše v So 03. 05. 2008 v 10:13 -0700:
> Ladislav Lhotka wrote:
> > Juergen Schoenwaelder píše v So 03. 05. 2008 v 16:32 +0200:
> > 
> >> There are also examples. An augment of foo-cont simply sticks nodes
> >> into the foo-cont container; there is no new instantiation of
> >> foo-cont.
> >>
> > 
> > Example on pages 82 and 83 contradicts what you are saying: the augment
> > statement in namespace http://example.com/schema/ds0 takes the schema
> > subtree defined by "container interfaces" in namespace
> > http://example.com/schema/interfaces, augments it and effectively places
> > the result at the spot of the augment statement in the
> > http://example.com/schema/ds0 namespace.
> > 
> 
> It's a bit tricky.
> Augment puts nodes from the augmenting namespace and
> puts it 'someplace else', which could be the same namespace.
> 
> The uses-stmt takes nodes from 'somewhere else' and puts them 'here',
> in the namespace for 'here'.

That's all right, but I still think one can imagine the augment
statement to be replaced by the content of its target node (augmented as
specified) and said content keeps its original namespace. If it is not
so, then I am seriously confused and don't really know why augment can
appear in different places in the schema tree (under module, container
and list).

Lada

> 
> 
> > Lada
> > 
> 
> Andy
> 
> _______________________________________________
> YANG mailing list
> YANG@ietf.org
> https://www.ietf.org/mailman/listinfo/yang
-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C

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