W3C home > Mailing lists > Public > public-webcgm-wg@w3.org > February 2007

bug in WebCGM 2.0 DTD

From: Lofton Henderson <lofton@rockynet.com>
Date: Mon, 12 Feb 2007 15:59:17 -0700
Message-Id: <>
To: WebCGM WG <public-webcgm-wg@w3.org>


This is a heads-up message.  It is for your information purposes only.  It 
is NOT intended to be the formal first step in processing an erratum.  We 
are just sorting out the details of those steps.  We will soon begin the 
W3C errata process [0], which you should read.

[0] http://www.w3.org/2005/10/Process-20051014/tr.html#errata

This will be a topic for our Thursday telecon -- how we classify the 
erratum in W3C, how/when to enter it into the WebCGM's W3C errata document 
[1], and whether anyone disagrees with the (below) diagnosis and correction.

[1] http://www.w3.org/2006/WebCGM20-errata.html

Bug summary:

There are three interrelated editorial errors (see "Bug details" below) in 
the DTD file that was published on 2007-01-30 concurrently with the 
publication of REC WebCGM 2.0 [2].

[2] http://www.w3.org/TR/2007/REC-webcgm20-20070130/

The WebCGM 2.0 XCF chapter [3] defines a System Identifier (SI) whose 
associated URI is [4], which you will notice is in OASIS web space.  The 
URI [4] is viewed as the "latest version" URI for the DTD.  It now points 
via a symlink to a specific version [5], in which you will see the error(s).

[3] http://www.w3.org/TR/2007/REC-webcgm20-20070130/WebCGM20-XCF.html#namespace
[4] http://docs.oasis-open.org/webcgm/v2.0/webcgm20.dtd
[5] http://docs.oasis-open.org/webcgm/v2.0//OS/webcgm20.dtd

Bug details:

The three-part error in the DTD is:

E1.) Error: line 92, after "desc CDATA #IMPLIED" there is a stray ">". 
Correction: delete stray ">".
E2.) Error: line 93, the string "%linkuriAttExt;" has "Ext" capitalized 
instead of "EXT" upper case. Correction: change "Ext" to "EXT".
E3.) Error: line 43, the entity definition of "linkuriEXT" is "" instead of 
EMPTY. Correction: change "" to EMPTY.

In the text of the WebCGM 2.0 REC [6], the glitches E1 and E2 are not 
repeated.  However the glitch E3 is repeated in 4.3.8 and 4.4 [6], in the 
in-text listing of the DTD snippets and the complete DTD:
[6] http://docs.oasis-open.org/webcgm/v2.0/OS/WebCGM20-XCF.html

E4.) Error: 4.3.8: in the DTD snippet, the entity definition of 
"linkuriEXT" is "" instead of EMPTY. Correction: change "" to EMPTY.
E5.) Error: 4.4: in the complete DTD, the entity definition of "linkuriEXT" 
is "" instead of EMPTY. Correction: change "" to EMPTY.

Corrections illustrated:

The proposed DTD-code solution to the errors E1-E3 above is illustrated in 
the file [7], a copy of which I have uploaded to WebCGM WG web space:

[7] http://www.w3.org/Graphics/WebCGM/WG/2007/errata-20/webcgm20-20070124.dtd

This file is NOT approved or officially endorsed in any manner.  That 
requires W3C errata processing by the WG (and coordinated processing in OASIS).

Furthermore, the file [7] will NOT be the specific replacement DTD file 
that we want to approve through the errata process.  Although the specific 
code corrections E1-E3 as included in [7] are endorsed by the originator 
and by Dave Cruikshank, the actual replacement DTD file that is ultimately 
approved by the errata process will also have history and version-control 
information in the initial comments section.


This is purely a heads-up and information for users and WG members.  It is 
not to be construed as the initiation of the errata process, which formal 
step will follow in the near future, and does not to imply any sort of 
official status or approval of the illustrated corrections.

Clearly, the OASIS WebCGM TC will need to run a parallel erratum process, 
and coordinate the timing.  More later.

Received on Monday, 12 February 2007 22:59:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:23:39 UTC