Re: [netmod] CODE BEGINS ENDS in types draft

[Ladislav Lhotka <lhotka at cesnet.cz>]

Juergen Schoenwaelder píše v Út 10. 11. 2009 v 15:37 +0100:
> On Tue, Nov 10, 2009 at 02:43:31PM +0100, Martin Bjorklund wrote:
> > Ladislav Lhotka <lhotka at cesnet.cz> wrote:
> > > > > > Perhaps if we use something like
> > > > > > 
> > > > > >   <CODE BEGINS> file "define.rng"
> > > > > >   <CODE ENDS>
> > 
> > > OK, no problem with that.
> > 
> > Ok, so we agree to use the syntax above in the next revisions of our
> > drafts then?
> 
> I do not care much which format we pick as long as we stick to _one_
> format. The above is OK for me but I am happy to use something else.
> Now that I think again about it, one could probably also go with just
> 
> <CODE BEGINS>
> <CODE ENDS>
> 
> and have a script extracting modules search for the keyword 'module'
> (or 'submodule') and the following name to derive a filename. This is
> not much different from how smistrip for example derives a file name.

But this will not be used only for YANG modules. I prefer Martin's
suggestion.

Lada

> 
> I also noted differences in the meta data section between the
> yang-types and the netconf-monitoring documents and again it would be
> nice if we would be consistent since everybody will follow these
> initial YANG modules (I am using a reference statement in a revision
> statement for example and I have different copyright boilerplate
> text). And yes, ideally this all would be documented in the yang usage
> document (but right now the template in there is yet different). But
> I am optimisitc things will eventually converge. ;-)
> 
> /js
> 
-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C