[rfc-i] [Ietf-and-github] New Version Notification for draft-kwatsen-git-xiax-automation-00.txt
julian.reschke at gmx.de
Tue Feb 26 10:03:51 PST 2019
On 26.02.2019 17:47, Henrik Levkowetz wrote:
> On 2019-02-26 17:33, Julian Reschke wrote:
>> On 26.02.2019 17:24, Kent Watsen wrote:
>>> I hadn't seen this issue before, but I did see Henrik's comments about
>>> markers in
>>> draft-levkowetz-xml2rfc-v3-implementation-notes. FWIW, the
>>> "xiax:markers" attribute
>>> is primarily only to support xml2rfc v2 documents; v3 documents can just
>>> use the built-in
>>> "markers" attribute.
>>> That said, I think that markers are, in general, a mistake. That they
>>> were only put their
>>> for tools scrapping plain-text documents. Assuming tools extract from
>>> XML, then no
>>> markers are needed, neither for framing (to aid the scraping process) or
>>> for capturing
>>> the file's name (which is better served by the aforementioned "name"
>> The original reason for "CODE BEGINS" etc was for licensing (to clarify
>> that part of the content is considered to be a "code component").
> No, it was not. The original reason was to delimit code for other purposes.
> The association with licencing came later
The oldest RFC I see containing "CODE BEGINS" is RFC 5403, dated
The oldest "code components" list mentioned on
<https://trustee.ietf.org/trust-legal-provisions.html> is dated November
Best regards, Julian
More information about the rfc-interest