- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Wed, 19 Feb 2014 12:42:26 -0800
- To: Antoine Zimmermann <antoine.zimmermann@emse.fr>
- Cc: RDF WG <public-rdf-wg@w3.org>, Guus Schreiber <guus.schreiber@vu.nl>
On Feb 19, 2014, at 11:56 AM, Antoine Zimmermann <antoine.zimmermann@emse.fr> wrote: > Ok, I see, I understand now. > > The strange thing is that if you do this: > > <section> > <section> > <h3>Section title</h3> > <h4>Subsection 1</h4> > <h4>Subsection 2</h4> > <h4>Subsection 3</h4> > <h4>Subsection 4</h4> > </section> > </section> > > Then the first header (<h3>) stays as a <h3> with an added section number, the next two headers (<h4>) are turned into <h3> without section numbers, and all the following <h4>s stay as they are. > > So after respec processing, you end up with (modulo some more annotations): > > <section> > <section> > <h3>1.1 Section title</h3> > <h3>Subsection 1</h3> > <h3>Subsection 2</h3> > <h4>Subsection 3</h4> > <h4>Subsection 4</h4> > </section> > </section> As a best practice with ReSpec, sub-sections should be modeled using recursive <section> elements, each containing a single header (e.g., <h2>) as the first child element. ReSpec will automatically create an appropriate table of contents, and identify each section based on it's header (unless overridden). AFAIK, the handling of multiple header elements within a section is undefined, as you seem to have found out. Gregg > AZ. > > Le 19/02/2014 18:18, Gregg Kellogg a écrit : >> On Feb 19, 2014, at 9:05 AM, Antoine Zimmermann <antoine.zimmermann@emse.fr> wrote: >> >>> I did this and corrected the typos Markus spotted. >>> >>> Regarding <h3> and <h4>, it seems Respec is changing the first two <h4> headers of each section into <h3> headers. I don't understand why it's doing this, but it can be modified by editing the generated HTML file. >> >> Respec uses different headers (<h2>, <h3>, ...) just to indicate the header of the enclosing section. The actual numbers are determined by the level of inclusion within different section elements. For example: >> >> <section> >> <h2>level 1</h2> >> <p>body</p> >> <section> >> <h2>level 2</h2> >> <p>body</p> >> </section> >> </section> >> >> Will ultimately use the appropriate header based on where it is in the document hierarchy. >> >> Gregg >> >>> AZ >>> >>> Le 19/02/2014 14:38, Guus Schreiber a écrit : >>>> Looks good. Small detail: can you remove the "informative" class from >>>> all sections? >>>> Guus >>>> >>>> On 19-02-14 13:42, Antoine Zimmermann wrote: >>>>> I've updated the W3C note on dataset semantics. >>>>> >>>>> It validates fine with ReSpec and an HTML validator. Should be all good >>>>> for publication. >>>>> >>>>> https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-dataset/index.html >>>> >>>> >>> >>> -- >>> Antoine Zimmermann >>> ISCOD / LSTI - Institut Henri Fayol >>> École Nationale Supérieure des Mines de Saint-Étienne >>> 158 cours Fauriel >>> CS 62362 >>> 42023 Saint-Étienne Cedex 2 >>> France >>> Tél:+33(0)4 77 42 66 03 >>> Fax:+33(0)4 77 42 66 66 >>> http://zimmer.aprilfoolsreview.com/ >>> >> >> > > > -- > Antoine Zimmermann > ISCOD / LSTI - Institut Henri Fayol > École Nationale Supérieure des Mines de Saint-Étienne > 158 cours Fauriel > 42023 Saint-Étienne Cedex 2 > France > Tél:+33(0)4 77 42 66 03 > Fax:+33(0)4 77 42 66 66 > http://zimmer.aprilfoolsreview.com/ > > --- > Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active. > http://www.avast.com >
Received on Wednesday, 19 February 2014 20:42:56 UTC