[rfc-i] Request for feedback: the new CSS

Brian E Carpenter brian.e.carpenter at gmail.com
Fri Dec 2 11:34:42 PST 2016

On 03/12/2016 06:09, Joe Hildebrand wrote:
>> On Dec 2, 2016, at 1:51 AM, Adrian Farrel <adrian at olddog.co.uk> wrote:
>> Thanks for this Heather,
>>> If you have suggestions or recommendations, please add them as an issue
>>> in github.
>> No, it's alright, I'll just raise them in an email (this email) for discussion
>> on the mailing list as normal so other only have to look in one place for the
>> conversation :-)
>> 1. You have some embedded code fragments. Is it your intention that these will
>> still be visibly marked <CODE BEGINS> and <CODE ENDS>?
> As far as I know, those markings are optional, right?

Not exactly. And they aren't our choice - they are defined in the IETF Trust
legal provisions:

>>> License to Code Components.
>>> Definition. IETF Contributions and IETF Documents often include
>>> components intended to be directly processed by a computer (“Code Components”).
>>> A list of common Code Components can be found at http://trustee.ietf.org/license-info/. 
>>> Identification. Text in IETF Contributions and IETF Documents of the types
>>> identified in Section 4.a above shall constitute “Code Components”. In addition,
>>> any text found between the markers <CODE BEGINS> and <CODE ENDS>, or otherwise
>>> clearly labeled as a Code Component, shall be considered a “Code Component”.

So regardless of what would be most elegant in XML2RFCv3, authors must be able
to include these labels explicitly.

> The idea is that extracting code from the XML should be much easier than parsing the text for <CODE BEGINS> and <CODE ENDS>.


More information about the rfc-interest mailing list