OASIS logo W3C

WebCGM v2.0 Errata

OASIS Standard
09 May 2007

Document Identifier:


Specification URIs:

This Version:
XHTML: http://docs.oasis-open.org/webcgm/v2.0/errata/os/webcgm-v2.0-errata.html
PDF: http://docs.oasis-open.org/webcgm/v2.0/errata/os/webcgm-v2.0-errata.pdf
DTD: http://docs.oasis-open.org/webcgm/v2.0/errata/os/webcgm20-20070509.dtd
Previous Version:
XHTML: http://docs.oasis-open.org/webcgm/v2.0/errata/cd01/webcgm-v2.0-errata.html
PDF: http://docs.oasis-open.org/webcgm/v2.0/errata/cd01/webcgm-v2.0-errata.pdf
DTD: http://docs.oasis-open.org/webcgm/v2.0/errata/cd01/webcgm20-20070228.dtd
Latest Version:
XHTML: http://docs.oasis-open.org/webcgm/v2.0/errata/webcgm-v2.0-errata.html
PDF: http://docs.oasis-open.org/webcgm/v2.0/errata/webcgm-v2.0-errata.pdf

Declared XML namespaces:
System Identifier:

Technical Committee:



David Cruikshank, The Boeing Company


Lofton Henderson, Individual

Related Work:

These errata apply to

WebCGM 2.0 OASIS Standard ,

which is identical in technical content to:

WebCGM 2.0 W3C Recommendation, available at http://www.w3.org/TR/2007/REC-webcgm20-20070130/ .


Computer Graphics Metafile (CGM) is an ISO standard, defined by ISO/IEC 8632:1999, for the interchange of 2D vector and mixed vector/raster graphics. WebCGM is a profile of CGM, which adds Web linking and is optimized for Web applications in technical illustration, electronic documentation, geophysical data visualization, and similar fields. First published (1.0) in 1999 and followed by a second (errata) release in 2001, WebCGM unifies potentially diverse approaches to CGM utilization in Web document applications. It therefore represents a significant interoperability agreement amongst major users and implementers of the ISO CGM standard.

WebCGM 2.0 adds a DOM (API) specification for programmatic access to WebCGM objects, and a specification of an XML Companion File (XCF) architecture, for externalization of non-graphical metadata. WebCGM 2.0, in addition, builds upon and extends the graphical and intelligent content of WebCGM 1.0, delivering functionality that was forecast for WebCGM 1.0, but was postponed in order to get the standard and its implementations to users expeditiously.

The design criteria for WebCGM aim at a balance between graphical expressive power on the one hand, and simplicity and implementability on the other. A small but powerful set of standardized metadata elements supports the functionalities of hyperlinking and document navigation, picture structuring and layering, and enabling search and query of WebCGM picture content.


This document was last revised or approved by the OASIS CGM Open WebCGM TC on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

These errata are being produced jointly by OASIS and W3C. The two organizations' respective final versions of these errata, published concurrently, apply respectively to the OASIS Standard and the W3C Recommendation. They have identical content except for cover page and formatting differences as appropriate to the two organizations.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page ( at www.oasis-open.org/committees/tc_home.php?wg_abbrev=cgmo-webcgm .)

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page ( www.oasis-open.org/committees/cgmo-webcgm/ipr.php .)

The non-normative errata page for this specification is located at www.oasis-open.org/committees/cgmo-webcgm.


Copyright 2007 OASIS Open, and W3C (MIT, ERCIM, Keio). All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.


OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.


Erratum identifier: E01

Overview: There are three interrelated editorial errors (see "Bug details" below) in the external DTD file ([4], [5]) that was published on 2007-01-30 concurrently with the publication of OASIS Standard (OS) WebCGM 2.0 and W3C REC WebCGM 2.0 [2].

[1] http://docs.oasis-open.org/webcgm/v2.0/OS/webcgm-v2.0-index.html
[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 resides in OASIS web space. The URI [4] is viewed as the "Latest version" URI for the DTD,for the latest version that has been approved at the OS level. As of the WebCGM 2.0 original publication date of 20070130, it pointed via a symlink to a specific version [5], in which you will see the error(s) are apparent.

[3] http://docs.oasis-open.org/webcgm/v2.0/OS/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 20070130-published DTD [5] is:

E01.1: line 92, after "desc CDATA #IMPLIED" there is a stray ">". Correction: delete stray ">".

E01.2: line 93, the string "%linkuriAttExt;" has "Ext" capitalized instead of "EXT" upper case. Correction: change "Ext" to "EXT".

E01.3: line 43, the entity definition of "linkuriEXT" is "" instead of EMPTY. Correction: change the 2-character string "" to the 7-character string "EMPTY".

In theWebCGM 2.0 REC text [6], the glitches E01.1 and E01.2 are not repeated. However the editorial glitch E01.3 is repeated in 4.3.8 and 4.4 of Chapter 4 [6], in the in-text listing of the DTD snippets and in the in-text complete DTD:

[6] http://docs.oasis-open.org/webcgm/v2.0/OS/WebCGM20-XCF.html

E01.4: section 4.3.8: in the DTD snippet, the entity definition of "linkuriEXT" is "" instead of EMPTY. Correction: change the 2-character string "" to the 7-character string "EMPTY".

E01.5: section 4.4: in the complete DTD, the entity definition of "linkuriEXT" is "" instead of EMPTY. Correction: change the 2-character string "" to the 7-character string "EMPTY".

Changes to text of WebCGM 2.0 OASIS Standard

Make these two changes to the 20070130-published text of WebCGM 2.0 [1], chapter 4 [6], to fix E01.4 and E01.5:

  1. Section 4.3.8, change the line,

    <!ENTITY % linkuriEXT "" >


    <!ENTITY % linkuriEXT "EMPTY" >

  2. Section 4.4, change the line,

    <!ENTITY % linkuriEXT "" >


    <!ENTITY % linkuriEXT "EMPTY" >


To fix E01.1, E01.2, and E01.3 in the 20070130-published external DTD file [5], replace that file with the corrected external DTD file, which is referenced by the cover page URI under "Specification URIs", "This version", "DTD".