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

julian.reschke at gmx.de (Julian Reschke) Thu, 18 February 2016 06:52 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Thu, 18 Feb 2016 07:52:43 +0100
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <58786D16-D782-4FBB-88FF-83CD3D59DF61@cisco.com>
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>
Message-ID: <56C56A3B.9090909@gmx.de>

On 2016-02-17 23:29, Joe Hildebrand (jhildebr) wrote:
>> On 2016-02-17 21:09, Paul Hoffman wrote:
>>> On 17 Feb 2016, at 8:02, Julian Reschke wrote:
>>>
>>>> I'm not completely sure how
>>>>
>>>> a) the need to identify code that should be surrounded with "<CODE
>>>> BEGINS>" / "<CODE ENDS>", and
>>>>
>>>> b) the desire to distinguish between artwork (like diagrams), source
>>>> code (such as ABNF), and examples (such as protocol messages)
>>>>
>>>> relate to each other. Could you elaborate?
>>>
>>> As others have said, (a) is not a real need. Given that, the desire in
>>> (b) might exist for some people but is not a requirement.
>>
>> Ahem. Brian just disagreed with you about (a). So did Joe.
>
> After talking with Paul about this a little, I think I'm wavering a bit.  I think this needs to be a part of the conversation we have with the Trust, to understand if there is an IPR difference between examples and sourcecode.

That statement refers to (b), not (a), right?

> I wonder if calling the element <protocol> instead of <example> might make it clearer why there was a different element with different semantics?

<verbatim>?

Best regards, Julian