Re: [NGO] external module properties
Wes Hardaker <wjhns1@hardakers.net> Wed, 30 April 2008 13:43 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 C3BA13A6DE9; Wed, 30 Apr 2008 06:43:46 -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 5BE183A6D30 for <ngo@core3.amsl.com>; Wed, 30 Apr 2008 06:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.473
X-Spam-Level:
X-Spam-Status: No, score=-0.473 tagged_above=-999 required=5 tests=[AWL=-0.651, BAYES_00=-2.599, FF_IHOPE_YOU_SINK=2.166, 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 RQNEw8LDwTt4 for <ngo@core3.amsl.com>; Wed, 30 Apr 2008 06:43:45 -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 097A73A6B86 for <ngo@ietf.org>; Wed, 30 Apr 2008 06:43:45 -0700 (PDT)
Received: from wes.hardakers.net (wlap.dyn.hardakers.net [127.0.0.1]) by wes.hardakers.net (Postfix) with ESMTP id 5323739A26C; Wed, 30 Apr 2008 06:42:24 -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=a77jrpIOBL9RBzQ6htVovRrc3bw=; b=Pk/izmidlyGo+GztN79V0Mf/yOSdY98+/SLrwDojuigNd+ZyhN3dsYuqKahTDl7ujIB/JKmW0c2Sw1AjL4xnOJaZfcdLXuFAelr6kPLRaMhPsYaEe6XXY0Xazr6XQ0t+EXEGYQu/z5r18gny3WokgO8a0WArJf0GMMalKhxOuik=
Received: by wes.hardakers.net (Postfix, from userid 274) id 068B139A26D; Wed, 30 Apr 2008 06:42:23 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Phil Shafer <phil@juniper.net>
Organization: Sparta
References: <200804291905.m3TJ5ewb090087@idle.juniper.net>
Date: Wed, 30 Apr 2008 06:42:23 -0700
In-Reply-To: <200804291905.m3TJ5ewb090087@idle.juniper.net> (Phil Shafer's message of "Tue, 29 Apr 2008 15:05:39 -0400")
Message-ID: <sdskx3e9xc.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 15:05:39 -0400, Phil Shafer <phil@juniper.net> said: PS> Then I'm lost. You wanted: PS> (a) required formatting PS> (b) sortability PS> Which requirement doesn't YANG satisfy? I actually said that I didn't (ideally) want (a). The requirement on formatting I suggested was a simple sortable number (either integer or floating point) who's value could be left to the module writer as long as it was either an integer or float. I'm fine with a date and time too, though. This is not an argument that I think is crucial, mind you, but I don't see the point in restricting modules to only be released once per day. That's imposing an arbitrary rule that isn't needed. And letting the version spec be either a integer or float without additional imposed semantics means you can use a date-based number or you don't have to. Flexibility all around. >> revision 20070609 { >> revision 200706090001 { >> revision 42 { >> As long as future > past, the tools should be happy. PS> This breaks (a) above. Which I never said I wanted. You extrapolated that from my desire for an sortable format. It's easy to see how you could have thought that and I'm sorry if I didn't explain it well enough. PS> There's a lot to be gained by using dates What? PS> Being able to look at the revision history and see when what PS> happened, how stable a module is, and how likely folks are to be PS> up-to-date with the latest version is important. So you want to compare the frequency of releases based on the date to decide whether to use it or not? PS> And it avoids tons of discussion about whether we need two or three PS> decimal numbers and when the major or minor version should change. PS> It's simple, obvious, sortable, well-defined, and will last for PS> thousands of years. How about 2008-01-01-0000? Or better (IMHO) 200801010000 which is instantly machine parse-able without special code? Or how about an XML defined date/time string that leaves the time stamp as optional? Wouldn't that provide the most reuse and flexibility? -- Wes Hardaker Sparta, Inc. _______________________________________________ NGO mailing list NGO@ietf.org https://www.ietf.org/mailman/listinfo/ngo
- [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Jon Saperia
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Ladislav Lhotka
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Balazs Lengyel
- Re: [NGO] external module properties Balazs Lengyel
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Randy Presuhn
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Ladislav Lhotka
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Balazs Lengyel
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties Ladislav Lhotka
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Ladislav Lhotka
- Re: [NGO] external module properties Randy Presuhn
- Re: [NGO] external module properties Randy Presuhn
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties David Harrington
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Juergen Schoenwaelder
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Wes Hardaker
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Randy Presuhn
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Randy Presuhn
- Re: [NGO] external module properties Randy Presuhn
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Andy Bierman
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Phil Shafer
- Re: [NGO] external module properties Martin Bjorklund
- Re: [NGO] external module properties Martin Bjorklund