[ruby] Editotorial feedback on the Use Cases & Exploratory Approaches draft

Richard Ishida, Tue, 10 Jul 2012 16:35:41 +0100:

> We welcome feedback. Please send comments to www-international@w3.org 
> (publicly archived[2]). Please use a relevant and informative subject 
> line that begins with “[ruby] “.

Both now, and when it was a Wiki page, it was hard to grasp the 
structure of the document. This is partly due to the very long and 
repetitive headings.

To make the structure simpler to grasp, here is a number of proposals:

  * Make a separate sub heading for the table since the table
    serves as a guide to the entire document.
  * The '2.7 Approach A4: Grouped rb model' appears to be the only one 
with an unreserved "Yes" to the "meets the use case" question. However 
the table summary [1] does not list that outcome.  Please split the 
relevant cells for column A2 (and column A3) to make room for the a) 
and b) variants.
 * Тhe column heading 'Interleaved rb and rt model' should match
   the rest of the document (currently: 'Enhanced HTML5 model')
 * Add links from row titles to the corresponding section headings
 * Remove the double numbering. Currently, we first have the section 
numbering and then the approach numbering - this also makes the titles 
exceedingly long.

So, w.r.t. numbering etc, then section 2 could e.g. go like this:

   2. The Ruby base styling use case
   <!--I would drop the Accessibility use case as separate heading
      to make section 2 more congruent with the other sections -->
   2.1 with the XHTML 1.1. model
   2.2.a with the current HTML5 model
   2.2.b with the current HTML5 model with span
   2.3.a with the enhanced HTML5 model - explicit rb tag
   2.3.b with the enhanced HTML5 model - implicit rb
   2.4 with the grouped rb model

[1] http://www.w3.org/TR/2012/WD-ruby-use-cases-20120710/#approaches

-- 
Leif H Silli

Received on Tuesday, 10 July 2012 18:19:48 UTC