Re: [Rfcplusplus] (no subject)

["Heather Flanagan (RFC Series Editor)" <[e-mail]>]

On 6/21/18 11:40 AM, Bob Hinden wrote:
> Brian,
>
>> On Jun 20, 2018, at 4:40 PM, Brian E Carpenter <[e-mail]> wrote:
>>
>>
>> I don't know Sue's answer, but mine (as noted in my draft) is that it
>> doesn't really matter how large and bright we make the labels on the
>> documents, because the underlying problem (if there is one) is human
>> nature. That said, I strongly support using the new RFC format to make
>> the labels larger and brighter.
>>
> I think that’s an excellent suggestion.  We will soon be able to use the new formatting tools to make the status of the document much clearer.   I think that much better than attempting to start new number series for each type of RFC, which I think will only cause more confusion to the community of people us use the RFC series.
>
> Once we decide how to do this using the new formats to do this, I suspect we could change the tools that create html and PDF from the existing base of txt RFCs to make them similarly make the status much clearer.  This approach will do something with the existing RFCs, nothing in the current BOF proposal does that.
>
>

That has been one of my expectations, that after we had a bit of 
experience with the new format that we could discuss if and how to use 
the new CSS to modify the look of different statuses and/or streams. The 
W3C has some experience with this, though they go as far as to have 
different CSS for everything from drafts to Recommendations and every 
possible point in between.

There are several ways we could approach solving for the confusion 
problem(s). I'd rather make sure we're clear on the problem(s) before 
diving into any particular solution.

-Heather