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

julian.reschke at gmx.de (Julian Reschke) Mon, 11 July 2016 06:45 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Mon, 11 Jul 2016 08:45:35 +0200
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <36c2b458-f997-ac05-19f0-de1fb6c11bb4@rfc-editor.org>
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> <56C483B4.6070002@tzi.org> <8A4B09EE-D1D6-4128-A841-74FE0A71B8D2@att.com> <ABE4C6E5-FF69-4597-8C92-1C6728E0F1A3@vpnc.org> <56C4998E.5000905@gmx.de> <96A3BB9B-D18D-4D8D-8AA8-A5824C7EEF3E@vpnc.org> <56C4D54C.7070808@gmx.de> <58786D16-D782-4FBB-88FF-83CD3D59DF61@cisco.com> <56C5E4F1.7080309@rfc-editor.org> <34f2287d-2ed3-0a5e-18dc-56826be18250@gmx.de> <36c2b458-f997-ac05-19f0-de1fb6c11bb4@rfc-editor.org>
Message-ID: <9ef07332-b397-e1f4-412f-50a6490d1158@gmx.de>

On 2016-07-10 23:17, Heather Flanagan (RFC Series Editor) wrote:
> On 6/25/16 3:40 AM, Julian Reschke wrote:
>> On 2016-02-18 16:36, Heather Flanagan (RFC Series Editor) wrote:
>>> ...
>>> I think if we get clarification on this, the rest of the question of
>>> what to do will make more sense. I've pinged the Trust and will let you
>>> know what they say.
>>>
>>> -Heather
>>> ...
>>
>> And the answer was...?
>>
>
> (Apologies - I thought I'd answered this to the list!)
>
> "Under the TLP all code is licensed under the BSD OSS license.  It
> doesn't matter whether the code is an example or "actual" code.  "
>
> HTH!

Ok,

as far as I understand this means that there are still cases where "CODE 
BEGINS/CODE ENDS" brackets are needed. Right?

In which case I'd argue that it would be good for the vocabulary to 
express this, so that the author doesn't have to put the text into the 
actual code.

Best regards, Julian