[No hats]

My suggestion is we keep the extraction of code from documents separate from 
how/whether they are validated. A hint towards whether the examples are 
complete or not, of course, would be helpful.

BTW, there are two tools that need to be considered for this change - xym and 
rfcstrip. Both will need to recognize these new tags.

Thanks.

> On Oct 14, 2025, at 9:27 AM, Ladislav Lhotka 
> <[email protected]> wrote:
> 
> 
> 
>> 14. 10. 2025 v 18:13, Carsten Bormann <[email protected]>:
>> 
>> On Oct 14, 2025, at 16:45, Carsten Bormann <[email protected]> wrote:
>>> 
>>> type=“yang”…
>> 
>> Actually, 
>> 
>> https://www.rfc-editor.org/rpc/wiki/doku.php?id=sourcecode-types
>> 
>> has:
>> 
>>   • yang
>>   • yang-instance-data+json
>>   • yangtree
>> 
>> (and you can get additional ones of needed, and media types can also be used 
>> as source code-types.)
> 
> This is even better, but it still doesn't discriminate instance data snippets 
> or sketches from complete examples that are intended to be formally 
> validated. Instead of introducing new sourcecode/media types for this, it 
> would IMO be cleaner to introduce a new attribute, e.g. "role".
> 
> Lada
> 
>> 
>> Grüße, Carsten
>> 
>> 
> 
> --
> Ladislav Lhotka
> PGP Key ID: 0xB8F92B08A9F76C67
> 
> 
> 
> _______________________________________________
> netmod mailing list -- [email protected] <mailto:[email protected]>
> To unsubscribe send an email to [email protected] 
> <mailto:[email protected]>

Mahesh Jethanandani
[email protected]






_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to