Re: [YANG] extension naming scope

Martin Bjorklund <mbj@tail-f.com> Sun, 10 February 2008 21:04 UTC

Return-Path: <yang-bounces@ietf.org>
X-Original-To: ietfarch-yang-archive@core3.amsl.com
Delivered-To: ietfarch-yang-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6B9E3A68F5; Sun, 10 Feb 2008 13:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.657
X-Spam-Level:
X-Spam-Status: No, score=-0.657 tagged_above=-999 required=5 tests=[AWL=-0.162, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from core3.amsl.com ([127.0.0.1]) by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IhvZiuiys1Jm; Sun, 10 Feb 2008 13:04:10 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 138253A68AE; Sun, 10 Feb 2008 13:04:10 -0800 (PST)
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 5EBEE3A6854 for <yang@core3.amsl.com>; Sun, 10 Feb 2008 13:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1]) by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l2b+tUXBkfuf for <yang@core3.amsl.com>; Sun, 10 Feb 2008 13:04:08 -0800 (PST)
Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id 8753B3A6834 for <yang@ietf.org>; Sun, 10 Feb 2008 13:04:08 -0800 (PST)
Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id 432F21B80C3; Sun, 10 Feb 2008 22:05:33 +0100 (CET)
Date: Sun, 10 Feb 2008 22:05:08 +0100 (CET)
Message-Id: <20080210.220508.149362842.mbj@tail-f.com>
To: ietf@andybierman.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <47AE266D.4070601@andybierman.com>
References: <47AE266D.4070601@andybierman.com>
X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: yang@ietf.org
Subject: Re: [YANG] extension naming scope
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: <http://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: <http://www.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: yang-bounces@ietf.org
Errors-To: yang-bounces@ietf.org

Andy Bierman <ietf@andybierman.com> wrote:
> Hi,
> 
> I think the extension naming scope needs to be removed, and extensions
> need to be in the same scope as rpc, notification, and all objects.
> When converted to YIN, an extension element is in the same XML namespace
> as the object instances defined in the same module.

I don't think this is a problem.  The same thing is done in XSD, where
e.g. simpleTypes and elements have different naming scopes.  In XSD,
there can be a simpleType named 'foo' and an element named 'foo' and a
group named 'foo' at the same time.


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