Re: [yang-doctors] CODE BEGINS to mentions that CODE BEGINS is not used

[Benoit Claise <[e-mail]>]

Working out of xml source is on my todo list.
In the IESG meeting right now. From the RFC-editor discussion, "about 
17% of docs do not have any XML source file".
We will be checking how many YANG module-related docs don't have a XML 
source file.

Regards, Benoit

>
> why do we still extract from the txt instead of the xml, now that xml 
> is mandatory?
>
> using the xml would also resolve the line-spacing issue mentioned by 
> Martin recently.
>
> additionally, xml would allow us to stash (appinfo?) processing 
> instructions, such as the command line needed to generate a tree 
> diagram or to validate an instance document.
>
> regarding generating the tree diagram, i think we’d have to accept a 
> 95% solution, as sometimes tree diagrams are hand-tweaked.
>
> if xml we’re used, presumably this error would not have occurred, as 
> the processing instruction would’ve been missing.
>
> K.
>
> Sent from my iPhone
>
> On Mar 17, 2018, at 6:34 PM, Benoit Claise <[e-mail] 
> <mailto:[e-mail]>> wrote:
>
>> Dear all,
>>
>> Here are the hackathon with Joe Clarke, dealing with the 
>> yangcatalog.org <http://yangcatalog.org> toolchain.
>>
>> Excerpt from RFC8346.
>>
>>
>>             B.1.2
>>             <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc8346-23appendix-2DB.1.2&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=MlJYZiSsWLnPWhl2UBCt0gRS9tWPXId42ZKwR1Noteo&s=M_puwPZ3Ev02hfC4ET-K-BLXytxd8gMFtWdybmT8UsY&e=>.
>>             OSPF Topology YANG Module
>>
>>         The OSPF Topology YANG module is specified below.  As mentioned, the
>>         module is intended as an example for how the Layer 3 Unicast topology
>>         model can be extended to cover OSPF topologies, but it is not
>>         normative.  Accordingly, the module is not delimited with
>>         <CODE BEGINS> and <CODE ENDS> tags.
>>
>>        file"[e-mail]"
>>        module example-ospf-topology {
>>            yang-version 1.1;
>>            namespace "urn:example:example-ospf-topology";
>>            prefix "ex-ospft";
>>            import ietf-yang-types {
>>                prefix "yang";
>>            }
>>
>> Guess what?
>> The <CODE BEGINS>, which is supposed to say that <CODE BEGINS> is not 
>> used, actually triggers the extraction
>>
>> $ xym --strict True  --debug 1 rfc8346.txt
>>
>> Extracting '[e-mail]'
>>    Removed 0 empty lines
>>
>> Extracting '[e-mail]'
>>    Removed 0 empty lines
>>    ERROR: 'rfc8346.txt', Line 1425 - YANG file not specified in <CODE 
>> BEGINS>
>>    ERROR: 'rfc8346.txt', Line 1428 - YANG module 
>> 'example-ospf-topology' with <CODE BEGINS> and starting with 'example-'
>>
>> Extracting 'example-ospf-topology'
>>    Getting YANG file name from module name: example-ospf-topology.yang
>>    Removed 0 empty lines
>>    ERROR: 'rfc8346.txt', Line 1963 - Missing <CODE ENDS>
>> Created the following models that conform to the strict guidelines:
>> [e-mail]
>> [e-mail]
>> example-ospf-topology.yang
>>
>> Mainly FYI.
>>
>> Regards, Benoit
>>
>> _______________________________________________
>> yang-doctors mailing list
>> [e-mail] <mailto:[e-mail]>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_yang-2Ddoctors&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=MlJYZiSsWLnPWhl2UBCt0gRS9tWPXId42ZKwR1Noteo&s=575Ltmds2wkiPt2cxV2vQbhisuj0BkFsDB13cDIXeDM&e=