Re: [Tools-discuss] Specifying stream in kramdown-rfc?

[Spencer Dawkins at IETF <[e-mail]>]

Carsten,

On Thu, May 5, 2022 at 5:56 PM Carsten Bormann <[e-mail]> wrote:

> On 2022-05-06, at 00:29, Spencer Dawkins at IETF <
> [e-mail]> wrote:
> >
> > Dear All,
> >
> > I'm running make on a kramdown-rfc file that is saying
> >
> > draft-ietf-mops-streaming-opcons.xml(11): Warning: Expected a valid
> submissionType (stream) setting, one of IETF, IAB, IRTF, independent, but
> found None.  Will use 'IETF'
> >
> > My first guess was to say "stream: IETF" near the other pi fields, but I
> don't think that's working.
> >
> > What am I missing?
>
> submissiontype: IETF
>
> (And it is not a pi, just a top-level YAML entry.)
>
> In RFCXMLv3, the stream is called “submissionType” [2], the Kramdown-rfc
> deStudLiFier allows you to write submissiontype (but maybe I should add
> “stream” as an alias).  You still have to write IETF in upper case, because
> that is the actual value of the attribute [1]:
>

You're perfect!


> >> 2.49.12. "submissionType" Attribute
> >>
> >> Possible values:
> >> ( "IETF" | "IAB" | "IRTF" | "independent" )
> >> Default value:
> >> "IETF"
> >> The document stream, as described in [RFC7841]. (The RFC Series Editor
> may change the list of allowed values in the future.)
>
> I’m thinking about generating the default automatically, as xml2rfc is
> nonsensically warning about the default value being used (that’s why it’s
> the  default?  It’s not a “fallback” value…).
>

I'll never be on the tools team, but that makes perfect sense to me.
Assuming that the distribution of IDs among the streams is something like
the distribution of newly published RFCs across the streams, "IETF" is the
obvious (and non-amazing) default.

Best,

Spencer


> (I’m also planning to put in a standard set of “silence” PIs…)
>

😉


> Grüße, Carsten
>
> [1]: https://xml2rfc.tools.ietf.org/xml2rfc-doc.html#section-2.49.12
> [2]: https://datatracker.ietf.org/doc/html/rfc7991#appendix-A.2
>
>