Re: h and section/div

(me)
>> But I don't think the current definition of <h> fully solves 
>> the semantics<->markup mapping problem.  I suggest 
>> changing the models of section, div, and block* to include 
>> at most one optional title as the first element.

"Ernest Cline" <ernestcline@mindspring.com> responded:

> A good idea, but one which I feel should be addressed by 
> the use of the <caption> element instead of the <title> or
> <h> element.

[Because semantically, a div or block is not large enough to 
make the main table of contents.  If you have a table of
figures, it can look for captions instead of titles.]

OK, I'm now convinced that caption should be used instead,
and h should be limited to a direct child of body or section.

I still think it should be limited to at most one per body or
section.

<body>
<h>
	Supposedly, this applies to the whole document.
</h>

	So it is redundant with title, except for the fact that 
	it should display, instead of just "being available".

<h>
	Wait, how can there be two headings that apply to
	the whole document?  People *will* use it to 
	describe the next section.
</h>
<section>
<h>	Supposedly, this applies to the whole section.
	In practice, it will be used to describe the next
	lower-level division.
</h>
	<section>
		<h>
			So this heading will either be left out, 
			or used for	the next div, which should 
			have a caption instead.
		</h>
		<div>asdlfjkasdlfkj</div>
		<h>
			for div2, obviously, since you don't need 
			a second header	on the section.
		</h>
		<div>div2</div>
	</section>
<h>
	Again, this supposedly applies to the whole section, 
	even though it already has a heading.  It will be used
	for the next div
</h>
<div>asdlfkj</div>
</section>

<h>
	Another heading for the whole document, not just for
	the next section...
</h>
Random text that people will assume is described by the
heading just above.

</body>

Received on Friday, 30 May 2003 11:55:00 UTC