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

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

From: cabo at tzi.org (Carsten Bormann)
Date: Wed, 17 Feb 2016 08:12:30 +0100
Subject: [rfc-i] How to indent artwork with surrounding block
In-Reply-To: <56C41744.9030405@gmx.de>
References: <76FD8A33-4FE3-4333-8E7C-BE2E274C1D24@cisco.com> <970A412E-B227-420F-8EE7-611A228D93E1@vpnc.org> <56C3EFA0.9010208@gmail.com> <56C41744.9030405@gmx.de>
Message-ID: <56C41D5E.7050403@tzi.org>

Julian Reschke 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.
> 
> I have a big problem with that, as it (a) defeats styling and (b) breaks
> the code semantics. That's why I suggested a separate attribute for that
> (see
> <http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#ext-rfc2629.artwork).

Generally these markers are extremely intrusive.

There are also several drafts where an xpath expression of the form

//artwork[@type='CDDL']/text()

or similar is the defined way to generate the complete source code for
the draft; having to add post processing to *remove* the <CODE BEGINS>
etc. noise sounds nonsensically counterproductive.

So, yes, the author needs to be in control.

Gr??e, Carsten