[rfc-i] How to indent artwork with surrounding block

cabo at tzi.org (Carsten Bormann) Wed, 17 February 2016 14:29 UTC

From: cabo at tzi.org (Carsten Bormann)
Date: Wed, 17 Feb 2016 15:29:08 +0100
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <56C480A6.9060509@gmx.de>
References: <76FD8A33-4FE3-4333-8E7C-BE2E274C1D24@cisco.com> <970A412E-B227-420F-8EE7-611A228D93E1@vpnc.org> <56C3EFA0.9010208@gmail.com> <A2D5E0B4-9BE7-4166-BC17-EA078C938C97@att.com> <56C480A6.9060509@gmx.de>
Message-ID: <56C483B4.6070002@tzi.org>

Ah, interesting.

"otherwise clearly labeled as a Code Component" could indeed be done
with an attribute (or could be implied from the sourcecode GI -- not
sure that this is desirable).

Gr??e, Carsten


Julian Reschke wrote:
> On 2016-02-17 14:55, HANSEN, TONY L wrote:
>> ...
>>> To be clear, are you assuming that tags like <CODE BEGINS> and <CODE
>>> ENDS>
>>> will continue to be inserted manually by individual authors, as part
>>> of the
>>> <sourcecode> text?
>>>
>>> I have no problem with that, but it needs to be explicit.
>>
>> Hopefully there will be absolutely no need for <CODE BEGINS> or <CODE
>> ENDS> to ever be seen again. Why bother when tools can be made
>> available to easily extract the code blocks? I'm really curious.
>>
>>     Tony Hansen
> 
> AFAIU, <CODE BEGINS> and <CODE ENDS> aren't embedded for extraction but
> for IPR reasons. See
> <http://trustee.ietf.org/license-info/IETF-TLP-5.htm>, Section 4b).
> 
> Best regards, Julian
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>