Re: section/heading reformulation

My interpretation may be way off but this is how I understand it:

Everything following a heading is related to that heading until 
another heading of the same rank is discovered.

There are two types of sections, explicit (using <section>) and 
implied. So for example: 
<h>heading 1</h>
<section>
    <p>It is explicitly stated that everything int this section, 
including other sections and headings are related to the previous heading</p>


--- mr.hartung.acc10@streber24.de wrote:

> 
> Johannes Koch wrote: 
> 
> > I thought, the way to go with XHTML 2 was
> > 
> > <section>
> >    <h>heading of section_1</h>
> >    <!--this is section_1-->
> >    <section>
> >      <h>heading of section_1.1</h>
> >      <!--this is section_1.1-->
> >    </section>
> > </section>
> > 
> 
> You are partially right and me, I ve been
> partially wrong, but both only partially,
> so please take a look at the example 
> given in the sepcs: 
> 
> <body>
> 
> <h>Events</h>
> 
> <section>
> 
>     <h>Introduction</h>
>     <p>....</p>
>     <h>Specifying events</h>
>     <p>...</p>
> 
>     <section>
>         <h>Attaching events to the handler</h>
>         <p>...</p>
>     </section>
> 
>     <section>
>         <h>Attaching events to the listener</h>
>         <p>...</p>
>     </section>
> 
>     <section>
>         <h>Specifying the binding elsewhere</h>
>         <p>...</p>
>     </section>
> 
> </section>    
> 
> </body>
> 
> Does it mean, that on the "h1-level" the <body>
> tag fullfills the <section> job? Seems so.
> 
> Maybe it is tought that way, but I think it is
> a little bit vague and unprecise, as <body> and 
> <section> belong to different modules (document,
> structure) with different content model, somehow
> different meaning and so on.
> 
> As I take consideration in the field of moving 
> whole sections between different levels, this 
> current solution seems to me to heavily fixed 
> on the document and not allowing e.g. the level1
> section to be moved to another level (where does
> it end? - possibly long before </body>).
> 
> (a) So I would prefer a solution with <h> only 
> allowed inside a <section> so that you can 
> always identify the relationship. In the 
> example above, where should an alogrithm know
> beginning (o.k. may be in follow-up to the 
> heading, but thats loose structure instead of
> XML usual nesting) but mainly: the END of the 
> h1-section? inside a document there can be 
> appendix etc before the <body> tag closes! 
> 
> (b) Furthermore I would demand for a restriction
> that allows only one <h> per <section>. This
> is not forbidden currently. But I consider it 
> necessarry to avoid structures like: 
> 
>   <section>
>     <h>The heading</h>
>     <h>Another heading - but wherefore?</h> 
>     <p>...</p> 
>     <h>And once again.</h>
>   </section> 
>     
> 
> What do you think thereof?
> 
> Yours sincerely,
> Mr B S Hartung, Germany, Dresden 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Received on Friday, 4 August 2006 14:50:31 UTC