Re: The <h> and <section> elements

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 4. November 2003 14:45 schrieb Lachlan Hunt:
> Hi,
>   I think a *recommendation* (not a rule) should be stated that::
>   "Each <section> SHOULD* only have one associated <h> element
> (exculding those in nested sections), and this <h> element should appear
> before any other <section> content (incl. paragraphs, lists, nested
> sections, etc...)."
>     * Use of the word should as defined in [RFC2119]
>
> [cut: useful examples]
I agree 100% :-)

> Pros:
>     1. Unambiguously associates each heading with it's content.
>     2. Helps to provide a structured document outline.
>     3. Helps improve accessability (because of reasons 1 and 2).
>     4. Not much more difficult to write.
Add: 5. Makes it much easier to access the content associated with a heading 
through XSLT

> Cons:
>     (Can't think of any, please reply if you can.)
Can't think of any, too.

> (Maybe this should be a recommendation in an Accessability (WAI)
> document, rather than the XHTML 2.0 specification?)
Good idea imho.

Bye
- -- 
ITCQIS GmbH
Christian Wolfgang Hujer
Geschäftsführender Gesellschafter (Shareholding CEO)
Telefon: +49  (0)89  27 37 04 37
Telefax: +49  (0)89  27 37 04 39
E-Mail: Christian.Hujer@itcqis.com
WWW: http://www.itcqis.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/qR0lzu6h7O/MKZkRAoKxAJ9bSgU3uk/wG6yuKySKJMkfMIvJGwCbBLN8
OzPdF/Nip9LjtrQ4xLIPnuA=
=axXa
-----END PGP SIGNATURE-----

Received on Wednesday, 5 November 2003 11:42:00 UTC