Re: [css3-gcpm] More magic areas than footnote and sidenote?

Also sprach marbux:

 > "Should there be a mechanism to create new areas like
 > footnote/sidenote, or are two "magic" area enough?"
 > <http://www.w3.org/TR/2007/WD-css3-gcpm-20070504/#sidenotes>

Thanks for picking up this issue and sending your comments. I'm in the
middle of an edit cycle, so this is helpful.

 > For editing application interoperability purposes, I'm somewhat
 > inclined against a flexible mechanism. However, I see a strong need
 > for at least three more note elements to be defined: [i] endnotes,
 > [ii] comments; and [iii] annotations.

Right. The first one is found in traditional printing and thererfore
falls within the scope of the draft. Named flow should be able to
address this use case. Example XXXII in the current draft reads:

  table .note { 
    float: to(endnote);
  }
  table::after { content: from(endnote) }

Comments and annotations are also useful in electronic publishing even
if they are not part of traditional printing. 

 > If a more generic approach to notes is considered, one might imagine a
 > generic <note> element

HTML5 proposes the <aside> element, arguable "note" is a better name:

  http://www.whatwg.org/specs/web-apps/current-work/#the-aside

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome

Received on Tuesday, 12 August 2008 14:34:34 UTC