OASIS logo W3C

WebCGM v2.1 Errata

OASIS Committee Draft 01
11 August 2010

Document Identifier:

WebCGM-v2.1-errata

Specification URIs:

This Version:
XHTML: http://docs.oasis-open.org/webcgm/v2.1/errata/cd01/webcgm-v2.1-errata.html
PDF: http://docs.oasis-open.org/webcgm/v2.1/errata/cd01/webcgm-v2.1-errata.pdf
Previous Version:
None.
Latest Version:
XHTML: http://docs.oasis-open.org/webcgm/v2.1/errata/webcgm-v2.1-errata.html
PDF: http://docs.oasis-open.org/webcgm/v2.1/errata/webcgm-v2.1-errata.pdf
Declared XML namespaces:
http://www.cgmopen.org/schema/webcgm/
System Identifier:
http://docs.oasis-open.org/webcgm/v2.1/webcgm21.dtd

Technical Committee:

OASIS CGM Open WebCGM TC

Chair(s):

Stuart Galt, The Boeing Company

Editor:

Lofton Henderson, Individual

Related Work:

These errata apply to

WebCGM 2.1 OASIS Standard ,

which is identical in technical content to:

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

Abstract:

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.

Status:

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.

The errata in this document apply to the final published WebCGM 2.1 specification of OASIS. Some of these editorial corrections were already applied in the final published specification of W3C. The rest will be processed as errata by W3C. The two organizations' respective final versions of errata documents will apply respectively to the OASIS Standard and the W3C Recommendation.

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 .)

Notices

Copyright 2010 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.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

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.


Table of Contents

1. E01 -- typo in WebCGM 2.0 XCF internal DTD

2. E02 -- extraneous Line Type Continuation references

3. E03 -- extraneous Edge Type Continuation references

4. E04 -- incorrect reference to XCF in section 3.2.1.7

5. E05 -- incorrect XCF reference in section 5.6.2.1

6. E06 -- add reference to 2.1 Test Suite

7. E07 -- clean up text in Appendix B

8. E08 -- duplicated text in item() description

9. E09 -- clarification of highlight() method description


1. E01 -- typo in WebCGM 2.0 XCF internal DTD

1.1 E01 overview:

In the internal complete DTD of XCF (section 4.4), the first line ends with ">>" instead of ">". This typo occurs only in the internal complete DTD, not in the external DTD file.

1.2 E01 changes to WebCGM v2.1 OS text:

In section 4.4, complete DTD, change ">>" to ">".


2. E02 -- extraneous Line Type Continuation references

2.1 E02 overview:

'lineTypeCont' appears in the ACI DTD snippet for defaultAttributes element (section 9.3.3), and "Line Type Continuation" appears in the bullet list following. These are editorial oversights -- Line Type Continuation was removed from the ACI before completion of the OASIS Standard, as can be seen from: there is no defining subsection 9.3.3.x; it does not appear in the ACI complete DTD of section 9.4; nor does it appear in the (normative) external file of the complete ACI DTD.

2.2 E02 changes to WebCGM v2.1 OS text:

In section 9.3.3 defaultAttributes element, delete "lineTypeCont |". In the following bullet list, delete the Line Type Continuation bullet.


3. E03 -- extraneous Edge Type Continuation references

3.1 E03 Overview:

'edgeTypeCont' appears in the ACI DTD snippet for defaultAttributes element (section 9.3.3), and "Edge Type Continuation" appears in the bullet list following. These are editorial oversights -- Edge Type Continuation was removed from the ACI before completion of the OASIS Standard, as can be seen from: there is no defining subsection 9.3.3.x; it does not appear in the ACI complete DTD of section 9.4; nor does it appear in the (normative) external file of the complete ACI DTD.

2.2 E03 changes to WebCGM v2.1 OS text:

In section 9.3.3 defaultAttributes element, delete "edgeTypeCont |". In the following bullet list, delete the Edge Type Continuation bullet.


4. E04 -- incorrect XCF reference in section 3.2.1.7

4.1 E04 overview:

In WebCGM 2.1 section 3.2.1.7, last paragraph, it is implied that geometric transform functionality is accessible via the XCF. This is an editorial oversight -- geometric transform was removed from the XCF before completion of the OASIS Standard.

4.2 E04 changes to WebCGM v2.1 OS text:

In WebCGM 2.1 section 3.2.1.7, last paragraph, change "WebCGM DOM (Chapter 5) and WebCGM XCF (Chapter 4) allow" to "WebCGM DOM (Chapter 5) allows".


5.0 E05 -- incorrect XCF reference in section 5.6.2.1

5.1 E05 overview:

In WebCGM 2.1 section 5.6.2.1, first sentence, it is implied that geometric transform functionality is accessible via the XCF. This is an editorial oversight -- geometric transform was removed from the XCF before completion of the OASIS Standard.

5.2 E05 changes to WebCGM v2.1 OS text:

In WebCGM 2.1 section 5.6.2.1, first sentence, change "by a DOM call or XCF data," to "by a DOM call"


6.0 E06 -- add reference to 2.1 Test Suite

6.1 E06 overview:

Section 7.6 contains references to earlier WebCGM test suites, but not to the WebCGM 2.1 test suite.

6.2 E06 changes to WebCGM v2.1 OS text:

In section 7.6, delete ", currently being upgraded to 2.1" from the 3rd bullet. Add a new 4th bullet whose text is "A WebCGM 2.1 test suite."; attach a link to http://docs.oasis-open.org/webcgm/test-materials/webcgm21ts/webcgm21-ts-index.html .


7.0 E07 -- clean up text in Appendix B

7.1 E07 overview:

Item #1 of Appendix B contains an incorrect reference to XCF for geometric transform functionality. This is an editorial oversight -- geometric transform was removed from the XCF before completion of the OASIS Standard.

7.2 E07 changes to WebCGM v2.1 OS text

Delete "and XCF facilities" from Item #1 of Appendix B.


8.0 E08 -- duplicated text in item() description

8.1 E08 overview:

Text is duplicated in the description of the item() method of WebCGMNodeList, section 5.7.7.

8.2 E08 changes to WebCGM v2.1 OS text

In the "Return value" section of the item() method description, delete "that is not a valid index."


9.0 E09 -- clarification of highlight() method description

9.1 E09 overview:

There is an ambiguity in the highlight() method description of WebCGMPicture (section 5.7.5). The text of the type parameter reads, "Denotes a behavior identical to the corresponding highlighting object behavior keywords of the fragment syntax." However, the intended object behavior keywords are addHighlight and newHighlight, not the simple add and new values of the highlight() method type parameter.

9.2 E09 changes to WebCGM v2.1 OS text

Make the correspondence explicit by adding a new second sentence: "The type parameter values add and new correspond respectively to the object behavior keywords addHighlight and newHighlight."