Re: [NGO] external module properties

Martin Bjorklund <mbj@tail-f.com> Sun, 27 April 2008 16:53 UTC

Return-Path: <ngo-bounces@ietf.org>
X-Original-To: ngo-archive@optimus.ietf.org
Delivered-To: ietfarch-ngo-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54F7428C170; Sun, 27 Apr 2008 09:53:57 -0700 (PDT)
X-Original-To: ngo@core3.amsl.com
Delivered-To: ngo@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28A8A28C102 for <ngo@core3.amsl.com>; Sun, 27 Apr 2008 09:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 TNa-m6p25X3H for <ngo@core3.amsl.com>; Sun, 27 Apr 2008 09:53:55 -0700 (PDT)
Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id 5C3E628C151 for <ngo@ietf.org>; Sun, 27 Apr 2008 09:53:55 -0700 (PDT)
Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id DFC6A1B80C7; Sun, 27 Apr 2008 18:53:58 +0200 (CEST)
Date: Sun, 27 Apr 2008 18:53:07 +0200
Message-Id: <20080427.185307.02650885.mbj@tail-f.com>
To: ietf@andybierman.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <48147DDD.9060203@andybierman.com>
References: <48145349.2030602@andybierman.com> <20080427.131919.130156558.mbj@tail-f.com> <48147DDD.9060203@andybierman.com>
X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: ngo@ietf.org
Subject: Re: [NGO] external module properties
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

Andy Bierman <ietf@andybierman.com> wrote:
> Martin Bjorklund wrote:
> > Andy Bierman <ietf@andybierman.com> wrote:
> >>> Namespace information is needed for parsers to work properly in case
> >>> of identifier clashes. And I am sure the IETF will require that
> >>> revision clauses are present in YANG modules. But this is not a
> >>> technical requirement of the language itself; it is a usage guideline
> >>> requirement. I believe this distinction is worthwhile to make.
> >>
> >> no -- the prefix is needed for the language parser.
> >> The namespace URI string isn't used anywhere in YANG.
> > It is needed in the NETCONF data that YANG defines.  Thus it is an
> > essential property in a YANG module.
> > 
> 
> not really.  I don't think RFC 4741 says so.

It is needed to avoid name clashes in the XML, e.g. if two modules have
the same top-level element name.


/martin
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo