[thelist] Coding standards.... [headers]

Julian Rickards julian.rickards at gmail.com
Mon Dec 11 10:14:06 CST 2006


I see the point you (and your friend?) are making but I still don't agree
with skipping headers. Maybe an unordered list might be considered.

On 11/12/06, Barney Carroll <barney at textmatters.com> wrote:
>
> Julian Rickards wrote:
> > Based on my opinion of this topic, I would wonder what larger topic do
> your
> > H3's belong to.
>
> Honestly? The purpose of the author's use of headers here seems pretty
> clear to me (then again I do know him and he isn't a published writer!):
>
> In this context, the h1 is a chapter title. It contains information
> about everything to follow up until the next h1.
>
> The chapter needs breaking up into smaller parts, for each instantiation
> of *ML technology, in chronological order.
>
> Prior to the first 'sub-chapter', there is an introduction (it would be
> terrible to dump the reader in without at least saying what is to
> follow) - but this introduction is a guide to the whole of what follows
> and, whereas not part of any sub-division, is definitely part of the h1.
> This is customary to the point where it is unnecessary to have what you
> might want to be an h2 stating 'Introduction', especially at this size.
>
> The introduction needs to give the reader advance warning of specific
> notions that may be needed to properly understand the content to follow.
> These are two distinct points which should certainly not be h2s - that
> would disrupt the clear semantic flow of h2s as they are presently used
> in the article. Neither do they want their own containing h2, which
> would do the same thing - and to put them within the next existent h2
> defeats the point.




-- 
Website: http://jrickards.ca
Blog: http://pen-and-ink.ca
E-mail: julian dot rickards at gmail dot com



More information about the thelist mailing list