Text for charmod last call comments

Hello

This mail is in completion of my action items:

Action CL: Suggest wording to I18N WG regarding C068.
Action CL: Write up TAG's complete LC comments and
send them to the I18N WG (cc'ing www-tag).
http://www.w3.org/2004/03/22-tag-summary.html

and following the resolutions
Resolved: TAG supports CL's statements (DC abstaining).
Resolved: TAG supports LC comments from Dan Connolly.
http://www.w3.org/2004/03/22-tag-summary.html

I have also had a useful and in-depth phone discussion with Martin
Dürst about the proposed feedback, so he has seen it informally and
understands where it is coming from.

The text of each of the three comments is between START and END. Each
one has been entered into the form that the I18N WG want to be used
for last call comments. I am sending this in email for archiving.

===== START =====

TAG agreed to this comment at its 22 March 2004 TAG teleconference
http://www.w3.org/2004/03/22-tag-summary.html

The TAG believes that its comment C125 regarding the Private Use Area
(PUA) on the previous last call has been substantially addressed.

We note one additional issue in the new text. It discourages an
existing use (encoding of pi or symbol fonts); on the one hand this is
good because inline graphics should be used for graphics, and it says
so

C068 [S] Specifications SHOULD allow the inclusion of or reference to
pictures and graphics where appropriate, to eliminate the need to
(mis)use character-oriented mechanisms for pictures or graphics.
C069 [C] Content SHOULD NOT misuse character technology for pictures
or graphics.

On the other hand, we worry that this might inadvertently encourage
people to encode pi or symbol fonts on the ascii range, which is worse
than using the PUA! For unencoded characters, or symbols, the PUA is
appropriate. To guard against this possibility we suggest adding the
following text - perhaps a new conformance requirement after C069 or
an extension of C069:

C0xx [I][C] Fonts for characters not yet in Unicode, or for graphical
symbols, SHOULD use the PUA rather than overloading existing
characters with unrelated glyphs.

====== END ======


===== START =====

TAG agreed to this comment at its 22 March 2004 TAG teleconference
http://www.w3.org/2004/03/22-tag-summary.html

>> C004 [S] Specifications of protocols and APIs that involve
>> selection of ranges SHOULD provide for discontiguous selections, at
>> least to the extent necessary to support implementation of visual
>> selection on screen on top of those protocols and APIs.

TAG is pleased by the changes made to this section. We still feel that
there is ambiguity there which would be removed by saying
"discontiguous logical selections" in C004, which is the type of
discontiguity needed for visual selection.

====== END ======

===== START =====

TAG agreed to this comment at its 22 March 2004 TAG teleconference
http://www.w3.org/2004/03/22-tag-summary.html

Following our original comment C119, the TAG thanks I18N for splitting
the document in two.
http://www.w3.org/International/Group/2002/charmod-lc/SortByOriginator.html#C119

After considerable discussion, the TAG still feels that the maturity
level of the IRI portion (good, needs substantial testing in CR) does
not match that of the rest of the document (wonderful, should go
straight to PR), as we noted in C119.

Please strike section 7 from this document and move it elsewhere to
avoid delaying the rest of the document.

====== END ======



-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group

Received on Monday, 29 March 2004 14:14:30 UTC