Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] New xml2rfc release: v2.25.0

[Julian Reschke <[e-mail]>]

On 30.08.2019 11:51, Robert Moskowitz wrote:
>
>
> On 8/30/19 12:53 AM, Julian Reschke wrote:
>> On 30.08.2019 06:43, Carsten Bormann wrote:
>>> On Aug 30, 2019, at 06:21, Julian Reschke <[e-mail]> wrote:
>>>>
>>>>> I need to find where 'consensus' is explained.
>>>>> ...
>>>>
>>>> <https://greenbytes.de/tech/webdav/rfc7991.html#element.rfc.attribute.consensus>
>>>>
>>>
>>> I’m not sure whether you are serious when you say the attribute is
>>> “explained” there.
>>> Yes, there is text about this attribute.
>>> No, it is not explained.
>>> The reference to 7841 just points to more text about “consensus”
>>> there, but not about the meaning of this attribute.
>>
>> There's more text at
>> <https://greenbytes.de/tech/webdav/rfc7991.html#attribute-consensus>;
>> and the main definition should reference that:
>>
>>> A.3. The "consensus" Attribute
>>>
>>> For some of the publication streams (see Appendix A.2), the "Status
>>> of This Memo" section depends on whether there was a consensus to
>>> publish (again, see Section 3.4 of [RFC7841]).
>>>
>>> The consensus attribute can be used to supply this information. The
>>> acceptable values are "true" (the default) and "false"; "yes" and
>>> "no" from v2 are deprecated.
>>>
>>> The effect of this value for the various streams is:
>>>
>>>     "independent": none.
>>>     "IAB": mention that there was an IAB consensus.
>>>     "IETF": mention that there was an IETF consensus.
>>>     "IRTF": mention that there was a research group consensus (where
>>> the name of the research group is extracted from the <workgroup>
>>> element).
>>
>> Best regards, Julian
>
> Oh, Dear Lord, this is such a wonderful addition that captures the state
> of work.  It just calls out for an April 1 RFC!!!!!
> ...

FWIW, this is not new at all. It has been around for at least nine years.

What's new is just the (IMHO confusing) warning message.

Best regards, Julian