W3C home > Mailing lists > Public > public-xhtml2@w3.org > December 2008

[XHTML2] Issue Raisig, Shaping, & Disposition (and wiki page pointers)

From: Gregory J. Rosmaita <oedipus@hicom.net>
Date: Thu, 25 Dec 2008 06:03:42 +0000
To: public-xhtml2@w3.org
Message-Id: <20081225055621.M53170@hicom.net>


in an attempt to harvest some low-hanging fruit in the run up to a new 
draft of XHTML2, i have mounted the following page on the XHTML2 wiki 
to promote an expeditious discussion of the issues raised (and if you 
don't see your sibboleth on the list, feel free to create a page and 
add to the effort...


i don't know how to log these requests stroke requirements -- well, 
technically i do, using tracker to create new issues, but i don't want 
to "spam" the public-xhtml2 list with issues that the WG hasn't agreed 
are issues as the tracker emails the list whenever an issue is opened, 
so that it can form the spool from which a thread can be auto-logged 
to the issue page (the old "magic words in the subject line trick") -- 
although the tracker did implement the "Raised" (as opposed to binary 
"Open" and "Close") state, it did so only for "Actions" and not "Issues"
so i am still unsure as to how exactly issues are to be logged and 
tagged as 
"Raised" for discussion at XHTML2 WG telcons, using the tracker agenda 
planner stroke shaper:


i don't know how the WG will dispose of them, but these are the partial 
of labor that originated as personal observations on the last editor's 
draft of XHTML2 for the PF WG, and i wanted to try and get consensus on
them before we push a new draft of XHTML2, gregory.

Proposed Elements & Element Reform for XHTML2
* http://www.w3.org/MarkUp/xhtml2/wiki/ProposedElements

   Note: This document does not reflect the opinions of anyone other than
   its author. [1] It has not been vetted or approved by anyone, although
   its aim is to foster expeditious explorations of the issues enumerated
   below. What are currently bullet points will be transformed into
   actual links once the relevant wiki document has been ported/created.

   Note 2: the for attribute [2] is defined in HTML to bind LABEL (or 
   multiple LABELs) to a form control using an IDREF; i propose that the 
   @for mechanism, which works in tandem with @id be extended in XHTML2 
   to provide explicit bindings between labelling text and the object it 
   labels, as well as a means of re-using values for ABBR, DFN, Q and 
   CITE; the first instance {at least} of "for" in the wiki pages listed 
   below should be hyperlinks pointing directly to the HTML4 definition 
   of "for")

New Elements

     * D - A Single Letter Element to Indicate Dialogue [3]
          + related: A Single Element to Indicate Dialogue [4]

Elements in Need of Reform

     * Q - A Single Quote Element [5]
     * Initialisms: Abbreviations, Acronyms and Their Ilk [6]
     * Making sense of CITE and @cite [7]
     * INS, DEL and MOD (marking changes/revisions) [8]
     * for/id associations for DFN
     * for/id associations for Abbreviated Forms [6]

 1. http://www.w3.org/MarkUp/xhtml2/wiki/User:GJR
 2. http://www.w3.org/TR/html401/interact/forms.html#adef-for
 3. http://www.w3.org/MarkUp/xhtml2/wiki/ProposedElements/D
 4. http://esw.w3.org/topic/PF/XTech/HTML5/D
 5. http://www.w3.org/MarkUp/xhtml2/wiki/ProposedElements/Q
 6. http://www.w3.org/MarkUp/xhtml2/wiki/ProposedElements/Initialisms
6a) http://www.w3.org/MarkUp/xhtml2/wiki/Talk:ProposedElements/Initialisms
 7. http://www.w3.org/MarkUp/xhtml2/wiki/ProposedElements/CITE_and_cite
 8. http://www.w3.org/MarkUp/xhtml2/wiki/ProposedElements/MOD

Related Discussion:
 * http://www.w3.org/MarkUp/xhtml2/wiki/Talk:Main_Page

lex parsimoniae:
  * entia non sunt multiplicanda praeter necessitatem.
the law of succinctness:
  * entities should not be multiplied beyond necessity.
Gregory J. Rosmaita, oedipus@hicom.net
         Camera Obscura: http://www.hicom.net/~oedipus/
Received on Thursday, 25 December 2008 06:04:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:30:31 UTC