- From: Lofton Henderson <lofton@rockynet.com>
- Date: Fri, 31 Aug 2007 15:34:38 -0600
- To: WebCGM WG <public-webcgm-wg@w3.org>
WebCGM WG, Current collection of potential 2.0 errata: http://lists.w3.org/Archives/Public/public-webcgm-wg/2007Aug/0020.html http://lists.w3.org/Archives/Public/public-webcgm-wg/2007Aug/0021.html New addition to collection... Case insensitivity of <param> attribute values ---------- A careful look at section 3.4 of WebCGM 1.0 [1] and section 3.4 of WebCGM 2.0 [2] indicates that the keyword values of the two attributes of the <param> sub-element of <object> are presented without regard to case. See for example the treatment of the value 'middle', which is variously presented as 'middle' or 'Middle' in the text and in the figures. This follows the general treatment of most non-graphical text strings as case-insensitive in WebCGM. See for example the PPF entries for a couple of Metafile Descriptor elements [3]: METAFILE DESCRIPTION, T.16.2, which says "Parameter strings are considered case insensitive", or T.16.13 FONT LIST, which says "Font names are considered case insensitive." This erratum was discussed in Seattle. A spot check of WebCGM viewers shows that case-insensitive is commonly assumed. It is also agreed to be an editorial correction (Class 2). CONCLUSION. It should be explicitly clarified in [2] that attribute values of the <param> sub-element are case-insensitive, with the single exception of the value associated with the 'onload' <param> (which is the name of a script function to be invoked.) [This erratum applies to WebCGM 1.0 as well, with the exception of the 'onload' proviso.] [1] http://www.w3.org/TR/2001/REC-WebCGM-20011217/REC-03-CGM-IC.html#webcgm_3_4 [2] http://www.w3.org/TR/2007/REC-webcgm20-20070130/WebCGM20-IC.html#webcgm_3_4 [3] http://www.w3.org/TR/2007/REC-webcgm20-20070130/WebCGM20-Profile.html#webcgm_4_5 Regards, -Lofton.
Received on Friday, 31 August 2007 21:34:15 UTC