Last modified: $Date: 2007/07/11 22:49:54 $
Copyright © 2007 W3C® (MIT, ERCIM, Keio), and OASIS. All Rights Reserved. W3C liability, trademark and document use rules apply.
The WebCGM 1.0 Recommendation was produced by collaboration of the W3C and the CGM Open Consortium.
This document lists the known errata to the WebCGM 1.0
Recommendation.
Each entry has the following information:
Please send general comments about this document to the public mailing list public-webcgm@w3.org. An archive is available at http://lists.w3.org/Archives/Public/public-webcgm/.
Added text marked thus. Removed text marked thus. Changed text marked thus.
The processing of errata is governed by the errata process defined in the W3C Process document.
- E01: clarification non-URI characters, IRIs, RFC-2396/3986.
Description:
Date of this entry: 18 June 2007
Class: Class ?.
TBD. (seems like "2", editorial clarification -- no implementations need change to conform? Or does an implementation that only implemented one case need to be modified to handle both cases?)
Overview: During the generation of the text of @@WebCGM 2.0@@, it became clear that the text of @@WebCGM 1.0 section 3.1.1.4@@, "Non-ASCII Characters in URIs", was interpreted in two different ways by implementations. In fact, both interpretations are valid cases of the correct specification, and this was clarified in WebCGM 2.0, @@"3.1.1.4 Non-URI characters in IRIs".@@
In addition, Chris assures us that it is okay as an erratum to retroactively update the usage of "URI" to "IRI" throughout, and to update the RFC-2936 reference(s) with RFC-3986 and 3987.
Proposed fix: Replace the text of WebCGM 1.0 3.1.1.4 with the text of WebCGM 2.0 3.1.1.4. Change RFC reference(s). Change URI to IRI everywhere (except where URI is really meant.) Fix the wording of 'linkuri' per WebCGM 2.0 and issue CL-d8 (this can be part of E01, or a separate erratum).
WG-approved Resolution:
TBD.
- E02: editorial errors in 3.4 <OBJECT> specification.
Date of this entry: 18 June 2007
Class: Class 2.
TBD. (seems like "2", editorial clarification -- no implementations need change to conform)
Overview: There are errors in the <OBJECT...> element illustration following the first paragraph of section 3.4. The ";" that occurs after "WebCGM" should not be there. The WIDTH and HEIGHT attributes should be quoted. Changing element and attribute names to lower case and adding a "/" at the end would make it valid XHTML.
Proposed fix: [...Fix it...]
WG-approved Resolution:
TBD.
- E03: correction (->example) of text search matching in para (3.2.1.3)???
Date of this entry: 18 June 2007
Class: Class ?.
TBD.
Overview: TBD
Proposed fix: TBD
WG-approved Resolution:
TBD.
- E04: fix 3.3 so that 'name' occurs in 'para' & 'subpara', in agreement with 3.1.2.3
Date of this entry: 11 July 2007
Class: Class ?.
TBD.
Overview: TBD
[2] http://www.w3.org/TR/2001/REC-WebCGM-20011217/REC-03-CGM-IC.html#webcgm_3_1_2_3
[3] http://www.w3.org/TR/2001/REC-WebCGM-20011217/REC-03-CGM-IC.html#webcgm_3_3
Proposed fix: add 'name' to the content models of 'para' and 'subpara' in 3.3.
WG-approved Resolution:
TBD.
- E05: clarify viewer handling of MITRE LIMIT
Date of this entry: 11 July 2007
Class: Class ?.
TBD.
Overview: Should be like in 2.0
[4] http://www.w3.org/TR/2007/REC-webcgm20-20070130/WebCGM20-Profile.html#webcgm_4_7_T_18_15
[5] http://www.w3.org/TR/2007/REC-webcgm20-20070130/WebCGM20-Profile.html#webcgm_4_15_T_26_7-mitre
Proposed fix: Fix T.18.15 and T.26.7 as in 2.0.
WG-approved Resolution:
TBD.
- E06: blah...blah.
Date of this entry: 11 July 2007
Class: Class ?.
TBD.
Overview: TBD
Proposed fix: TBD
WG-approved Resolution:
TBD.
- R01: TBD (revised @@ @@ 2007)
Description:
Tbd
Resolution:
Tbd