Re: [NGO] external module properties

Wes Hardaker <wjhns1@hardakers.net> Tue, 29 April 2008 18:52 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 8483628C25A; Tue, 29 Apr 2008 11:52:12 -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 3184B3A6AA3 for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 11:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.438
X-Spam-Level:
X-Spam-Status: No, score=-1.438 tagged_above=-999 required=5 tests=[AWL=0.550, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611]
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 Wl7sqsHowNv2 for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 11:52:03 -0700 (PDT)
Received: from wes.hardakers.net (dcn236-43.dcn.davis.ca.us [168.150.236.43]) by core3.amsl.com (Postfix) with ESMTP id 579E03A6D25 for <ngo@ietf.org>; Tue, 29 Apr 2008 11:51:17 -0700 (PDT)
Received: from wes.hardakers.net (wlap.dyn.hardakers.net [127.0.0.1]) by wes.hardakers.net (Postfix) with ESMTP id 2848E399A86; Tue, 29 Apr 2008 11:50:06 -0700 (PDT)
DKIM-Signature: v=0.5; a=rsa-sha1; c=relaxed; d=hardakers.net; h=received:from:to:cc:subject:organization:references:date:in-reply-to:message-id:user-agent:mime-version:content-type; q=dns/txt; s=wesmail; bh=RXVqRdOCZ1L8/RrQPtmshvV0F2c=; b=cqYnUG/fo/JFgZMeboG32ePmcSa44bIg7OaO7BoSbpoeOdKFk/xXd/mRvx8RRQQvc1JSO2e5fQNYMFRJOS3LLeFDjR1HJjE4PnpVnKu0CKjD18hnxXAJvgrpPIJHUMT0OVLVyOAhNcxJ3f7S7QButA95jlit9SmGHuIVSSxNHgA=
Received: by wes.hardakers.net (Postfix, from userid 274) id 0983D399B9B; Tue, 29 Apr 2008 11:50:06 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Phil Shafer <phil@juniper.net>
Organization: Sparta
References: <200804291543.m3TFhgrW088122@idle.juniper.net>
Date: Tue, 29 Apr 2008 11:50:05 -0700
In-Reply-To: <200804291543.m3TFhgrW088122@idle.juniper.net> (Phil Shafer's message of "Tue, 29 Apr 2008 11:43:42 -0400")
Message-ID: <sdve20sdgi.fsf@wes.hardakers.net>
User-Agent: Gnus/5.110007 (No Gnus v0.7) XEmacs/21.4.21 (linux, no MULE)
MIME-Version: 1.0
Cc: NETCONF Goes On <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

>>>>> On Tue, 29 Apr 2008 11:43:42 -0400, Phil Shafer <phil@juniper.net> said:

>> I'd be tempted not to even define the required formatting of the version
>> number.  Simply say it must be sortable using a standard comparison
>> function (strcmp or >).

PS> Funny, but that's exactly what we did in YANG ;^)

Good start, but I'm going to take issues with only using a date.  And
YANG doesn't do what I said.  It specifies the revision number format as
a date.

PS> The revision statement looks like:

PS> revision 2007-06-09 {
PS>    description "Initial revision.";
PS> }

I wanted to be able to pick what was right for me, as an author, from
any of these (for only I know what is good from my authoring
perspective):

  revision 20070609 {
  
  revision 200706090001 {

  revision 42 {

As long as future > past, the tools should be happy.

-- 
Wes Hardaker
Sparta, Inc.
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo