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

paul.hoffman at vpnc.org (Paul Hoffman) Wed, 17 February 2016 15:24 UTC

From: paul.hoffman at vpnc.org (Paul Hoffman)
Date: Wed, 17 Feb 2016 07:24:11 -0800
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <8A4B09EE-D1D6-4128-A841-74FE0A71B8D2@att.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>
Message-ID: <ABE4C6E5-FF69-4597-8C92-1C6728E0F1A3@vpnc.org>

On 17 Feb 2016, at 7:01, HANSEN, TONY L wrote:

> Yes, <CODE BEGINS> and <CODE ENDS> is just one way in which code 
> components can be identified. It's definitely not a requirement.

Exactly. I misunderstood the need for those, and thus supported the 
<example> idea earlier, but now I am quite sure we don't need it.

> Are there cases where one can have source code within the XML to which 
> the IPR statement applies, as well as code within the XML to which the 
> IPR statement does NOT apply? Does 
> <http://trustee.ietf.org/license-info/IETF-TLP-5.htm> imply though 
> that we should have an attribute within the XML that indicates whether 
> the IPR code statement applies or not? Or is this a rat hole?

The Trust can tell us all that in the future. Adding an attribute to 
<sourcecode> based on actual requirements, not guesses, is easy.

--Paul Hoffman