Re: [xml2rfc-dev] RFC 7991 issue #36: Schema Issue, RFC 7991, In Section 2.5.5, "name" Attribute

[Julian Reschke <[e-mail]>]

On 10/1/2018 1:36 PM, Henrik Levkowetz wrote:
> ...
> 
>        "A filename suitable for the contents (such as for extraction to a
>        local file)."
> 
>     Given the existing use of "name" on <seriesInfo>, this attribute name
>     has a semantic dissonance.
> 
>     Recommendation:  Deprecate "name" for use on <artwork> and <sourcecode>,
>                      and instead use "file", which for <sourcecode> will be
>                      explicitly rendered, as established as best current
>                      practice for YANG modules (see for instance RFC 6087
>                      [RFC6087])
> 
>     Implementation:  The current version of xml2rfc uses "name".
> ---
> ...

I would avoid making changes that aren't strictly necessary, thus keep 
the name as-is.

I also disagree with coupling the sourcecode tagging to the presence of 
a (file)name. This violates the principle of least surprise. There are 
good reasons for providing names, such as for automatic extraction 
during build time (for instance for running check scripts), which have 
absolutely nothing to do with the presentation in text or other formats.

Best regards, Julian