formalizing ITS integration in XHTML - proposed resolution (first draft)

aloha!

in my preliminary work on providing quick reference wiki space for 
XHTML2 issues, examples & best practice collection, and such

http://www.w3.org/MarkUp/xhtml2/wiki/XHTML2

i noticed that, although we resolved to discuss International Tag Set 
(ITS) integration with yves at the 23 April 2008 virtual face to face, 
but we never "codified" the results of our discussion with yves the WG 
never formally resolved to accept Yves' advice/answers -- i have drafted 
a proposed resolution (which might be moot already, depending upon 
shane's schedule, but i would like to formally propose the following just 
in order to ensure that the WG agree upon what was said and agreed to 
in regards ITS integration.

what follows my signature is a proposed resolution covering the points 
of agreement and clarification concerning ITS integration, which also 
can be found on the discussion page for the ITS issue on the XHTML2 wiki:

http://www.w3.org/MarkUp/xhtml2/wiki/Talk:XHTML2/i18n/ITS

where it is clearly noted that it has yet to be vetted (or voted upon) by
the working group

this may just be a formality or administrivial overkill, but provided 
that i, who was scribing, captured the conversation correctly, it would 
put the procedural ribbon on a WG-to-WG formal request/collaboration, and 
it is best to have it in the form of a resolution so that -- if any 
question pertaining to ITS or the i18n module arise in the future -- 
there is a definitive decision by the WG we can reference...  besides, 
we covered more than merely the answers to the initial 3 questions posed 
to Yves initially (which i "subtopic-ed" in the minutes), so there may 
be more to agree upon (or disagree over)

this falls under my self-assigned action/volunteer offer to collect all 
of the resolutions concerning XHTML2 made since 2008-01 (and going back 
later if deemed necessary after that, although i think i only need to 
trace back until we switched from shane's tracker to the w3c tracker) up 
on the wiki so that the resolutions made pertaining to each module can be 
traced, pointed to and referenced when and if the need for such 
documentation arises...

in any event, i think it a good way to expedite things by not only 
capturing resolutions in minutes, but by collecting them in a consistent 
manner, so that we don't have to grok the archives every time we're 
digging into an issue and/or have differing recollections of precisely 
what was previously decided by the WG...  unfortunately, i have not made
as much progress on this effort as i would like, but i plan on keeping 
atop all new resolutions and have plenty of minutes announcements in 
which i compiled the resolutions from a WG session, so i should be able
to get a lot up -- albeit in a piecemeal fashion -- relatively quickly, 
good lord willin' and the crick don't rise again...

gregory
----------------------------------------------------------------
CONSULT, v.i.  To seek another's disapproval of a course already
decided on.           --  Ambrose Bierce, The Devil's Dictionary
----------------------------------------------------------------
Gregory J. Rosmaita, oedipus@hicom.net
        Camera Obscura: http://www.hicom.net/~oedipus/index.html
----------------------------------------------------------------

formalizing ITS integration in XHTML

   Question: Since the WG did not formally resolve to accept Yves'
   answers to our questions in regards ITS integration, do i (or someone)
   need to propose a resolution at a WG meeting in order to record our
   acceptance of Yves' answers as a RESOLUTION.

<quote cite="http://www.w3.org/MarkUp/xhtml2/wiki/Talk:XHTML2/i18n/ITS"


1. Resolution(s) Regarding International Tag Set (ITS) Integration

   PROPOSED RESOLUTION: the XHTML2 WG accepts the advice regarding ITS
   integration provided by Yves Savourel during the discussion of ITS at
   the 2009-04-23 virtual Face2Face [ref 1], specifically:

    1. authors may use XHTML's native span element to insert inline ITS;
       for this purpose;

    2. XHTML2 will specify ITS integration in its i18n module; [ref 2]

    3. the current Ruby module [ref 3] will also be subsumed into the 
       expanded i18n module [ref 4]

    4. support for external ITS support alone would satisfy the i18n
       community today, but there remains a future case for inline
       support for ITS using XHTML2's native span element;

    5. XHTML will use link with <rel="itsrules"> in head to reference an
       International Tag Set (ITS) document

   -- question posed on wiki by GJR on 2009-05-10

Retrieved from
   "http://www.w3.org/MarkUp/xhtml2/wiki/Talk:XHTML2/i18n/ITS"
</quote>

References
   1. http://www.w3.org/2009/04/23-xhtml-minutes.html#item04
   2. http://www.w3.org/MarkUp/xhtml2/wiki/XHTML2/i18n
   3. http://www.w3.org/MarkUp/xhtml2/wiki/XHTML2/i18n/Ruby
   4. http://www.w3.org/MarkUp/xhtml2/wiki/XHTML2/i18n

Received on Wednesday, 13 May 2009 00:39:48 UTC