Re: [NGO] external module properties

[Phil Shafer <[e-mail]>]

Wes Hardaker writes:
>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 >).

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

    *** The revision Statement @revision@
    
    The "revision" statement specifies the editorial revision history of
    the module, including the initial revision.  A series of revisions
    statements detail the changes in the module's definition.  The
    argument is a date string in the format "YYYY-MM-DD", followed by a
    block of substatements that holds detailed revision information.  A
    module SHOULD have at least one initial "revision" statement.  For
    every editorial change, a new one SHOULD be added in front of the
    revisions sequence, so that all revisions are in reverse chronological
    order.

The revision statement looks like:

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

Thanks,
 Phil
_______________________________________________
NGO mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ngo