Re: [NGO] external module properties

Martin Bjorklund <mbj@tail-f.com> Mon, 28 April 2008 19:18 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 744C128C25E; Mon, 28 Apr 2008 12:18:15 -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 138E128C246 for <ngo@core3.amsl.com>; Mon, 28 Apr 2008 12:18:15 -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=[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 IQs6mO144DLA for <ngo@core3.amsl.com>; Mon, 28 Apr 2008 12:18:14 -0700 (PDT)
Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id 3DD7228C14F for <ngo@ietf.org>; Mon, 28 Apr 2008 12:18:14 -0700 (PDT)
Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id B7B7C1B80D2; Mon, 28 Apr 2008 21:18:16 +0200 (CEST)
Date: Mon, 28 Apr 2008 21:18:16 +0200
Message-Id: <20080428.211816.17535040.mbj@tail-f.com>
To: ietf@andybierman.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <4815EA5E.60607@andybierman.com>
References: <48137444.6070802@andybierman.com> <sdr6cq83d2.fsf@wes.hardakers.net> <4815EA5E.60607@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

Hi,

While I agree with Juergen about the general idea that YANG should not
try to enforce arbitrary rules on the user, in the case of 'revision'
I think it falls into the same category as 'namespace' and 'prefix'.
Neither is strictly speaking not required in all cases - a namespace
is not needed if the module is a type library such as yang-types; a
prefix is not needed if there are no local references in the module.

And I also agree that the revision might be needed for proper schema
discovery.

I think I'd rather see all three mandatory than all three optional.


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