Up to cover page | Back to ECMAScript binding
WebCGM 2.0 — Appendixes
In addition to the listed editors of
this specification, the following individuals have contributed significantly
to the present WebCGM specification:
- Forrest Carpenter, System Development Inc.
- Franck Duluc, Airbus
- Stuart Galt, The Boeing Company
- Ulrich Laesche, Ematek Informatik GMBH
- Don Larson, Larson Software Technology
- Kevin O'Kane, Auto-trol Technology
- Robert Orosz, Auto-trol Technology
- Andrew Moorhouse, UK Ministry of Defence
- Dieter Weidenbrueck, ITEDO
The following individuals made significant contributions to WebCGM 1.0:
- Maryse Da-Ponte, Airbus
- Bruce Garner, Analyst/Consultant
- Alan Hester, Xerox Corporation
- Bob Hopgood, CCLRC
- Chris Lilley, W3C
- Brad Powell, Zeh Graphic Systems
- Dave Rahnis, Bentley Systems
- Lynne Rosenthal, NIST
- John Gebhardt, Intercap Graphics Systems
- Roy Platon, CCLRC
- Ty Bartosh, Jeppesen Inc.
This section is informative (non-normative).
- WebCGM DOM. A major functional addition is a limited WebCGM Document
Object Model (DOM), carefully targeted at the WebCGM 2.0
requirements.
- WebCGM XCF. The second major functional addition is the definition of a
standard XML Companion File for use by WebCGM (and related) applications,
closely integrated with WebCGM DOM.
- Event model. As an adjunct to the DOM definition, a more detailed event
model has been specified, allowing definition and attachment of user
event handlers to objects, and specifying how "pick" events are handled
in a backward compatible way to WebCGM 1.0.
- Complementing the event model, a new param sub-element is added to the
OBJECT element, to allow handling of onload events.
- Single picture. Whereas ISO CGM:1999 allows multiple independent
pictures in a metafile, and WebCGM 1.0 originally did, multiple pictures
were deemed not amongst the requirements for WebCGM. To simplify WebCGM,
they were deprecated in WebCGM 1.0 2nd Release, and are now removed from
WebCGM 2.0.
- Fragment syntax. Small changes to allowable values, in order to embody
the single-picture rule, but the overall structure of the fragment is
unchanged for backward compatibility.
- Fragment syntax and xcfterm. It is now possible in the link fragment to
specify to load-and-apply an XML companion file before first display of
the graphics of a targeted picture.
- More object behaviors. The set of object behaviors that can be included
in the link fragment syntax has been expanded to give much more user
control. A set of behaviors is built from EBNF syntax, by combinations of
an orthogonal navigation term and highlighting term. The 3 behaviors of
WebCGM 1.0 are deprecated.
- Grnode. WebCGM 2.0 defines a purely graphical grouping mechanism,
"graphical node", which groups graphical primitives as an Application
Structure, but disallows the attributes or properties that associate
intelligence with objects.
- New APS attributes. WebCGM defines new APS attributes of type
'visibility' and 'interactivity' that may be applied to most object (APS)
types.
- Style Properties. For use in DOM and XCF, WebCGM 2.0 defines a set of
Style Properties -- text color, stroke weight, etc -- that transiently
(for the duration of a DOM or viewing session) override the corresponding
CGM attributes for targeted picture and APS nodes.
- URI versus IRI. Unifying different implementation interpretations of
WebCGM 1.0, WebCGM 2.0 clarifies that IRIs (Internationalized Resource
Identifiers) are used to reference resources, and describes how agents
handle them before passing to URI (Uniform Resource Identifier)
resolvers.
- Obsolete features. A number of previously deprecated WebCGM 1.0
features are made obsolete
(removed from WebCGM 2.0).
- Deprecated features. A number WebCGM 1.0 features are deprecated in WebCGM 2.0 (may be
removed in a future revision).
- Symbol Libraries. This capability was in WebCGM 1.0, but was removed
from WebCGM 2.0 because of lack of interest (POLYSYMBOL, several SYMBOL
LIBRARY elements, some registered ESCAPEs, etc).
- 2.0 and has added some graphical items that were deferred from WebCGM
1.0 (for expedience)
- NUBS and NURBS
- clipping to regions other than rectangles
- increased sizes for Cell Array and Tile Array elements
- Auxiliary Colour and Transparency
- text-on-path (i.e., text layout along arbitrary paths)
- increased sizes for Closed Figure elements
- API, Application Programming Interface
- An Application Programming Interface (API) is a set of functions or
methods used to access some functionality.
- Application Structure, APS
- The CGM structure for grouping other elements and assigning them a
unique identifier, a type, and attaching attributes. WebCGM contains
five valid APS types: grobject, layer, para, subpara, grnode.
- APS Attribute, Application Structure Attribute
- The CGM element that is used to define and associate an attribute
with an APS. WebCGM contains ten valid APS Attribute types: region,
viewcontext, linkuri, layername, layerdesc, screentip, name, content,
visibility, interactivity.
- Cascading profile
- A method by which closely related profiles can be expressed
efficiently, by only enumerating the differences between a given
profile and a base profile such as WebCGM.
- CGM, Computer Graphics Metafile
- ISO/IEC standard 8632:1999 (CGM:1999), CGM is a metafile format
consisting of composite raster and scalable vector graphics
information.
- DOM, Document Object Model
- A Document Object Model is a platform- and language-neutral interface
that allows programs and scripts to dynamically access and manipulate
the content, structure and style of documents. WebCGM defines a DOM of
limited scope, allowing discovery and navigation of the WebCGM
structure tree, transient manipulation of styles and standardized
metadata, and discovery and manipulation of application-specific
metadata. The WebCGM DOM is based upon and borrows from the principles
the W3C DOM Level 2 and DOM Level 3 Recommendations.
- EBNF, Extended Bauer Normal Form
- A formal specification technique used in WebCGM to express pieces of
grammar and syntax such as the IRI fragment syntax.
- fragment (IRI fragment)
- As standardized in RFC 3986 and RFC 3987, the fragment is a part of a
IRI that is separated from the path/file name by a "#" character, and
provides information that is reserved for processing by agents that are
invoked by the browser to handle the resource information type of the
IRI. WebCGM standardizes the syntax and semantics of such fragments,
for transmitting object and picture selection and behavior information
to WebCGM viewers.
- handler, event handler
- An event handler is a method called by the WebCGM DOM implementation
whenever a specified event occurs. Users register the event types they
are interested in by calling the addEventListener() method of the
WebCGMMetafile object.
- host application
- The user agent, typically is a script that controls the behavior of a
web page. In the context of WebCGM the host application controls the
behavior of the WebCGM renderer through the DOM.
- host document
- The web page, contains a combination of both HTML and WebCGM
content.
- host environment
- The combination of the host application and the host document
- inheritance
- The determination of values of APS Attributes and Style Properties
for objects in the WebCGM hierarchical object tree, when all aspects
have not been explicitly specified for all objects in the tree. WebCGM
defines an inheritance model that is closely based on CSS (Cascading
Style Sheets, a W3C Recommendation).
- interactive region
- the effective geometric region for the purposes of all interactive
cursor and mouse operations, such as picking and mouseover. By default,
the drawn graphical primitives of the object define the
interactive region. For filled-area primitives this includes: the edge,
if edge visibility is 'on'; the interior, if the interior style is
other than 'empty' or 'hollow'; and, the boundary, for interior style
'hollow'. For all graphical primitive types, drawn graphical
primitives exclude any that are fully transparent (so a fully
transparent object is equivalent to an empty object, for purposes of
interactive region definition). If the object contains a 'region' APS Attribute, then
that region area is the interactive region.
- listener, event listener
- The event listener specifies the interface via which users register
event handlers with the WebCGM DOM implementation. This interface
consists of a single method, handleEvent(), which the WebCGM DOM
implementation calls whenever specified events occur. Users pass
WebCGMEventListener objects as arguments to the addEventListener()
method of the WebCGMMetafile object to register a specific event
handler with the WebCGM DOM implementation.
- metadata
- Non graphical information contained within or associated with
standard graphical files, in WebCGM metadata supports such ancilliary
functions as hierarchical picture structuring, object identification
and navigation, and association of application-specific non-graphical
data with graphical objects.
- metafile
- A mechanism for retraining and transporting graphical data and
control information, containing a device independent description of one
or more pictures.
- namespace, NS
- A method devised and standardized by the XML Namespaces
standard, namespace provides a way to distinguish to which
specification and grammar elements and attributes belong, when
information from distinct XML languages is mixed in the same document.
WebCGM uses namespaces to separate standardized WebCGM XCF elements and
attributes from embedded and intermingled application-specific
metadata.
- Normalized Device Coordinates, NVDC
- The coordinate system that is used to communicate coordinate data
through the WebCGM DOM, NVDC is VDC normalized so that the origin is
lower-left and units are millimeters.
- object
- An Application Structure or Picture in a WebCGM.
- object behavior
- One of a set of (thirteen) ways in which the view of an object or
collection of objects is presented following the execution of a
hyperlink to the object(s). WebCGM standardizes a number of objects
that give complete control over the zoom, pan, and highlight aspects of
the view.
- picture behavior
- One of a set of ways in which the view of a picture (CGM) or document
(HTML) is handled following the execution of a hyperlink to the
content. Based on the 'target' attribute of the HTML 'a' tag, picture
behaviors allow the specification of the new view to occur in a new
window, to overwrite the whole contents of the source window, to
overwrite the parent window, etc.
- PPF, Profile Proforma
- A method of expressing profiles standardized in CGM:1999 (clause 9),
the PPF presents a profile as a single table covering all aspects of
the CGM standard, with a reference column (enumerating a Model Profile
or other base profile), and a column to define the target profile by
comparison to the reference column.
- Style Property
- A graphical attributes that may be applied and manipulated at the APS
or picture level, transiently, by WebCGM DOM and WebCGM XCF. WebCGM 2.0
defines nine style properties.
- target rectangle
- A rectangular region around the target object(s) that is used for the
application of object behaviors following hyperlink execution. The
target region is defined by APS Attributes and/or target geometry, and
for example provides the area to be encompassed by a zoomed view.
- WDOM, WebCGM DOM
- The WebCGM Document Object Model, this terminology is used when it is
needed to unambiguously distinguish the WebCGM DOM from the generalized
W3C DOM specifications.
- XCF, XML Companion File
- An XML file format defined by WebCGM, that can be used to externalize
metadata from WebCGM instances and bind it to objects in the
metafile.
This section is informative (non-normative).
Changes within W3C since W3C-published OASIS
Submission:
- ---200606xx editors draft (candidate LC text)
includes all of below changes---
- Fix the format of numerous References
(both normative and non-normative), correct a couple of references (such
as to WebCGM 2.0 Requirements).
- Fix 3.1.2.2 (picture
behaviors) and 3.1.2.7 to
be more "CDF friendly", generalizing about resource types and
presentations contexts.
- Change URI terminology to IRI terminology throughout, and add some
description to 3.1.1.1.
- In Chapter 5 (DOM), change parameter
name 'namespaceURI' to 'namespaceIRI' and 'fileURI' to 'fileIRI'.
- Fix cover page appropriately for W3C-OASIS
collaboration.
- Fix header line at the top of each Chapter.
- ---20060528 editors draft includes all of below
changes---
- Change listing of Example of
5.7.5 so that mime type is text/ecmascript.
- Fix "Editions and releases of
WebCGM" (1.8).
- Add Unicode to "Normative
references" (1.2), in both "generic" and "specific" form, add ISO
10646 reference in "generic" form, add UTF-8 & UTF-16.
- Correct the 5th line to "var cgmDoc;" in executable examples
of WebCGMEventListener (5.7.9) and
WebCGMEvent (5.7.10),
and in ex_WebCGM_Event.html and ex_WebCGM_EventListener.html.
- Typo, change 2nd occurrence of "Actual" to "Used" in
second-to-last sentence of 5.4.2.4.
- Revise the 3rd paragraph of hyperlinking conceptual
description (2.3.6) to clarify about rfc3986 and point off to
appropriate normative sections.
- Reword the first paragraph of the hyperlinking conceptual
description (2.3.6) to remove unintended "bi-directional"
implications.
- Clarify normative descriptions of para/subpara/content (3.2.1.3, and 3.2.1.4, and 3.2.2.8).
- Clarify conceptual descriptions of para/subpara/content (2.3.2 and 2.3.4) and add forward
links to Ch.3 normative descriptions.
- Editorials in "Overlaying
a picture" section (2.2.3) -- Change "object tag" to "object
element", and "TRANSPARENT" to "background".
- Add some more detail to the discussion of WebCGM drawing model
(2.2.2).
- Update PNG reference in "Normative references" (1.2), add
ISO Register of Graphical Items.
- Rewrite summary of behaviors
section (3.1.2.7) to clarify references and purpose of
incomprehensible table.
- Remove apparent contradiction from XCF-application description
(3.1.2.6) and clarify that the requirements are only for DOM-supporting
viewers.
- Clarify that XCF-relative-URI
description (3.1.1.5) is only about the resolution of an XCF
reference within the fragment of a WebCGM reference.
- Add unicode UTF-16 reference to normative references (1.2)
- Clarify <pict-part>
wording (2.3.6) about backward compatibility with 1.0.
- Restore the WebCGM 1.0
pictseqno ::= (digit)+
production
in the fragment EBNF
(3.1.1.2).
- Rewrite 1st pgph of picture selection description
(3.1.2.1) to clarify about mixed-version 1.0/2.0 environments, and
restore the missing WebCGM 1.0 out-of-range rule for pictseqno.
- Clarify the 'src'
attribute description on WebCGMMetafile interface (5.7.3).
- Correct the declared type of
getAppStructureById to WebCGMAppStructure in the IDL and description
(5.7.5), and the ECMAScript (ch.8); fix
the cut-paste error in the return-value description.
- Correct mapping of deprecated highlight and highlight_all object behaviors (3.1.2.4.1) to
full+newHighlight.
- Fix typo ("v2.0") in DOCTYPE example of XCF namespace (4.2.3) section.
- Fix typo, remove deprecated value "2" from valid compression types list
of TILE (T.19.29).
- Fix typo (missing quotes) to existing fragment EBNF
(3.1.1.2).
- Add extensibility entities to the 'linkuri' element of the XCF
(4.3.8), to the complete DTD
(4.4), and to the standalone DTD file
(webcgm20.dtd).
- Typos in WebCGMPicture interface
(5.7.5) descriptions -- getAppStructureById returns WebCGMNode, not
boolean; state parameter of highlight() description missing.
- Add a new toNodeList() convenience method to WebCGMAppStructure (5.7.6) IDL and
method description, and fix the ECMAScript
binding (ch.8).
- add some intra-ch.7 links and emphasis, fix typo in 6.18, ...
- fix mislabelled Appendices B..D; change "listed authors" to "listed
editors" in Appendix A.
- change document to W3C Working Draft, incl. all stylesheet references,
...
- ---20060313 W3C-published Submission text includes
all of below changes---
- W3C pubrules alignment changes made by Chris Lilley
Changes within OASIS since OASIS-published first Committee
Draft:
- ---20051027 candidate CS text includes all of below
changes---
- alphabetize glossary (App.B)
- integrated BB WebCGMNode example (5.7.4)
- revised 3.2.2.3 URI stuff to point to 3.1.1.3.
- rewrote 3.1.1.4 to clarify URI-escaping, when to apply and when not,
and add examples.
- switched to OASIS cover page, OASIS CSS, and made specialized
WebCGM20.css for unique styles (All).
- integrated SG WebCGMMetafile example (5.7.3)
- removed normative Conformance, References, ECMAScript from Appendixes
and made them Ch.7, Ch.8, Ch.9
- integrated SG WebCGMNodeList example (5.7.7)
- clarified return values of attributes on WebCGMMetafile, if no WebCGM
document is open in viewer (5.7.2 & 5.7.3).
- fixed typos in XCF DTD (4.4).
- minimal changes to examples 1-7 to make them 2.0-legal, "preferred",
and current with new 2.0 behaviors (3.1.3).
- integrate all new figures (Ch.2, Ch.3, Ch.5)
- add descriptions of 'halign' and 'valign' to PARAMs of OBJECT element
(3.4)
- reformat all of interface subsections (5.7.1 - 5.7.10)
- integrate SG WebCGMException example (5.7.1)
- fully integrate BB WebCGMPicture example (5.7.5)
- clarify (3.1.1.4) that WebCGM content does support pre-escaped and
post-escaped URIs;
- replace (incomplete) repetition of URI rules in 'linkuri' (3.2.2.3)
with pointer to 3.1.1.4.
- fix Ch.6 T.15.9 to refer to normative content model snippets of 3.2.1
subsections (3.3 DTD is not normative in 2.0).
- in Ch.6 T.15.9 and 3.2.1, add references to fragment objid production
of 3.1.1.3, for normative rules on APS id in WebCGM content.
- apply DC's
Ch.6 MP corrections, all editorial (multiple Ch.6 subsections).
- remove meaningless NO_MOD_ALLOWED_ERR exception from setAttributeNS
(5.7.4).
- ---20051007 editors draft includes all of below
changes---
- (partially) integrate BB WebCGMPicture example (5.7.5)
- apply RO's
Ch.6 MP corrections, i.e., from the .pdf attachment, all of which
were editorial (affects all Ch.6 subsections).
- apply UL's
Ch.3 editorial comments, i.e., from the .doc attachment.
- reword #1 of "processing namespace attributes" (5.3) -- same net
effect, but remove the vague implication of error.
- clarify 'move' operation in VDC Extent boundary case (3.1.2.4.3).
- 3.2.2.3 Example revised to emphasize preferred form and de-emphasize
discouraged form.
- delete "para, subpara" from "Viewer behavior" description of 3.2.1.5,
since their normative content models don't allow grnode children.
- regex production for hex digits in color sub-type is [0-9a-fA-F] --
case insensitive, per the section's examples (5.3).
- DL
Ch.5 editorial comments implemented (as amended by LH
suggestions).
- clarify wording of 1st bullet, item #4, "processing child elements"
list (5.3).
- reiterate/clarify up front that "picture behaviors" collectively
addresses CGM pictures and HTML documents/pages (3.1.2.2).
- reiterate "picture behaviors" collective concept also in footnote to
informative table of 3.1.2.7.
- explicitly clarify that xcfurl can be absolute or relative, and the
latter is resolved relative to the companion WebCGM instance
(3.1.1.5)
- fix (WebCGM 1.0) loophole that would have allowed format
effector-whitespace chars in 'name' (3.1.1.3).
- clarify that WebCGM 'target' picture behavior is based upon / derived
from HTML 4.01, not identical to it (3.1.1.3).
- copied definition of "format effectors" from CGM:1999 into T.14.5.
- API added to glossary (Appendix D)
- fix editorial errors in object behaviors table (3.1.2.4.1) and object
behaviors default (3.1.2.4.1)
- viewer handling of old (deprecated) object behaviors more precisely
defined (3.1.2.4.1, A.2.2).
- clarify language about what a URI fragment is (3.1.1.1)
- clarify language of optional / required attributes; clarify language
about private metadata (2.3.4)
- revise 2.3.4 to remove "optional" from the bullets and express it
before the list, along with "'layername' is required."
- replace "WebCGM viewers" w/ "WebCGM-supporting applications" in
1.1.
- remove and integrate last pgph of Abstract into rewritten 1st pgph
(plus bullet list) of 1.3.
- fix editorial error in IDL (5.7.7) and ECMAScript (App.F) -- newItem of
WebCGMNodeList::appendItem is type WebCGMNode, as stated in the text, not
(nonsensical) WebCGMString.
- ---2nd CD text---20050909 text includes all of
below changes---
- added OASIS Logo and "Notices" to cover page.
- added "A.5 Normativity", to explain normative/informative content and
conformance requirements.
- added RFC 2119 to normative references (B.1).
- added exception NO_MODIFICATION_ALLOWED_ERR to setAppStructureAttr,
removeAppStructureAttr (5.7.6).
- added legal-character reference to WebCGMNode.setAppStructureNS(), for
exception determination (5.7.4).
- added definitions (Appendix D) of event handler, event listener, host
application, host document, host environment.
- change A.4.2 (profile extensions rules) to non-normative, edit to
reflect resolved issues and cascading policy.
- add Null return value discussion to Basic Data Types (5.5.2.1), link
all Ch.5 "null" return specifications to it.
- WebCGMPicture (5.7.5) .getAppStructureById (fix),
getAppStructuresByName (ok): make consistent about "null" return.
- WebCGMNode (5.7.4) .childnodes (fix), .attributes (ok),
.getElementsByTagNameNS (fix): make consistent about "null" return.
- 5.7.10, fix 2nd bullet list to reflect that event handlers are only
attached to the WebCGMMetafile interface.
- add "empty string" discussion to Basic Data Types (5.5.2.2), link all
subsequent Ch.5 occurrences of "empty string" to it.
- change default namespace to "#FIXED" in XCF (4.3.3 & 4.4).
- fixed getAppStructureById for null return (was: returns empty list)
(5.7.5).
- changed 'null' to 'empty string' in namespaceURI, prefix, localName
attributes of WebCGMNode interface (5.7.4).
- added ATTR_NODE to WebCGMNode.namespaceURI applicability (5.7.4).
- Clarify resolution of relative URIs for applyCompanionFile, improve
wording and linking of description (5.7.5).
- In 3.2.1.5, grnode, clarify "Viewer behavior" wording about
interactive, direct child, etc.
- ---20050804 text includes all of below
changes---
- first cut at definitions of majority of terms in the glossary (Appendix
D).
- added XCF webcgm/xmlns examples, and clarified that xmlns must be
present on 'webcgm' (4.3.3).
- reference DOM basic data types from XCF "Data types and encodings"
(4.3.1).
- wrote comprehensive "Basic data types" section (5.5).
- changed "deprecated" to "discouraged" in 'linkuri' (to align past
intent with new "deprecated" definition) (3.2.2.3).
- added correct/incorrect usage examples to getWebCGMDocument.src
description (5.7.3)
- added local TOCs to chapters 1 and 6.
- added extensibility rules for profiles to Conformance clause (appendix
A.4.1).
- fixed example 5.1b to remove private graphical stuff (5.3).
- added extensibility rules for implementations to Conformance clause
(appendix A.4.2).
- added precise definition of "deprecated" to conformance clause
(A.2)
- added local TOC to start of Ch.2
- ---20050719 editors draft includes all of below
changes---
- moved Ch.4 "Data types & encodings" before the descriptions of the
XCF elements (4.3.1).
- added clarifying example of 3rd parameter usage to 'linkuri'
(3.2.2.3).
- added explanation to Fundamental Interfaces (5.7) of
picture-as-root.
- added explanation to WebCGMAttr (5.7.8) about parentNode, sibling
nodes, etc (null).
- added first cut of ECMAScript binding (appendix F).
- mark example 5.1b for replacement (it's more or less invalidated by
past couple months developments) (5.3).
- replace character-height SP with the text-size SP (5.7.5, 4.3.2,
4.4).
- clarified WebCGMNode.attributes about apsid and pictid, added table of
NodeType / Attributes (5.7.4).
- added getAppName() and getAppVersion() to GetWebCGMDocument interface
(5.7.2).
- replaced enumeration of objBehaviors in frag. EBNF with the 3-line
generating EBNF (3.1.1.2).
- moved behaviors-summary table to new 3.1.1.7, linked to rules
elsewhere.
- added example in 3.1.1.5 of resolution of relative URI in xcfterm of
fragment.
- fixed the NO_MODIFICATION_ALLOWED_ERR exception description on
WebCGMNode:Attr (5.7.8).
- correct FILE_INCOMPATIBILITY_ERR to FILE_INVALID_ERR in WebCGMException
IDL (5.7.1).
- removed deprecation warnings about sRGB (2.2.2, 2.5.3, 6.5, A.2).
- change visibility to pictureVisibility on 'webcgm' XCF (4.3.3), change
setPictVisibility() to setPictureVisibility (5.7.5).
- remove "must navigate first, then highlight", from obj behaviors
(3.1.2.4)
- remove hasAttributesNS() from WebCGMNode interface; fix explanation of
attributes, hasAttributes (5.7.4).
- ---20050708 editors draft includes all of below
changes---
- added summary table to 3.1.2, picBehavior & objBehavior rules for
H2C, C2H, C2C, DOM, XCF.
- added clearHighlight special form to obj-selection-keywords and
obj-behaviors sections (3.1.1.2, 3.1.2.4.1).
- updated fragment EBNF for all changes to obj. behaviors (3.1.1.2).
- added 'visibility' to XCF 'webCGM' element (4.3.3).
- finalize wording of parentNode attribute on WebCGMNode interface
(5.7.4).
- finalize format of metafileDescription attribute on WebCGMMetafile
interface (5.7.3).
- finalize description of 'src' attribute on WebCGMMetafile interface
(5.7.3).
- remove clearStyleProperty method from WebCGMPicture interface, explain
that "inherit" has same effect (5.7.5).
- text-font included in Style Properties of 5.7.5 and XCF; explain
initial value "metafile".
- clarify that 'attributes' and hasAttributes() on WebCGMNode include the
apsid parameter of BegAps (5.7.4).
- added informative note to PPF (Ch.6) T.14.4 and T.14.5 that Unicode
octet strings are "big-endian".
- added 'onload' param sub-element to OBJECT (3.4).
- in SP definitions (5.7.5), add inheritance-related specs of Computed
Value, "Inherited:yes", and "inherit" value.
- in SP definitions (5.7.5) clarify "replacement mode" (not accumulate),
and "order counts".
- prohibit intensity plus {fill-color | stroke-color | text color} on
same XCF element (4.3.2).
- finished editing obj. Behaviors sections (3.1.2.3, 3.1.2.4).
- added %styleProperties; to other XCF elements, and fixed the extension
entity definitions on all of them (4.3, 4.4).
- added "xmlns CDATA #implied" to ATTLIST of XCF 'webcgm' element (4.3.3,
4.4).
- added "Namespaces in XML" to normative references (B.1).
- UTF-8 & UTF-16 corrections made to PPF (ch.6, T.16.14).
- setPictVisibility() added to WebCGMPicture interface (5.7.5).
- ---20050627 editors draft includes all of below
changes---
- new 'layer' content picture in Ch.2, to allow empty layers (2.3.5).
- started implementing the new object behaviors of the URI fragment,
deprecating old (1.0) 3 behaviors (3.1.2.3, 3.1.2.4).
- deprecate viewport param element of OBJECT (3.4).
- fixed format of example on metafileDescription attribute, defined on
WebCGMMetafile interface (5.7.3).
- added picBehavior and same-CGM rules to src attribute, defined on
WebCGMMetafile interface (5.7.3).
- added new draft of DOM ch.5.4, "Inheritance model..."
- swapped example 4.1 to be last example (now 4.3), indicated "partial
inventory; "full description" is out-of-scope; also fixed the parallel
text in Ch.2.
- added Ch.4 XCF subsection defining Conforming WebCGM XCF file
(4.2.4)
- added Ch.4 XCF subsection for Namespace, Public Identifer, System
Identifier (4.2.3).
- clarified "mostly flat" structure of XCF, add example to illustrate,
mention webcgm-Picture root correspondence (4.2.1).
- added to 'version' attribute of 'webcgm' element, "every XCF must
identify version by 'version' or DTD" (4.3.3).
- change "mouse region" to "interactive region" (everywhere, mostly Ch.3
and Appendix D).
- added Style Properties to XCF, define styleProperties entity, add to
DTD (all 4.3 subsections, 4.4).
- restructured XCF (Ch.4) sub-sections.
- clarify that _replace picture behavior does not reload CGM, for
intra-CGM link within the same picture (3.1.2.2).
- clarify in OBJECT (3.4) that the FIXED param elt. only affects viewers'
user zoom/pan controls.
- in Style Prop. table of Interface WebCGMPicture (5.7.5), stroke-weight
and character-height must be > 0.
- Added placeholder "ECMAScript binding" appendix (F), per 20050608
telecon.
- ---20050610 editors draft includes all of below
changes---
- add local TOC to chapter 3.
- annotate "No example this WebCGM version" in 5.4.1.3 "Used Values".
- add "not fully transparent" to definition of mouse region, mention also
in 5.7.10.
- remove 1.0 restriction and allow empty layers in 2.0 (3.2.1.2,
3.3).
- convert content model of grobject to EBNF (3.2.1.1).
- clarify in 3.2.2.9 (visibility) and 3.2.2.10 (interactivity) that they
inherit to/thru grnode, even though they don't apply to it .
- fix viewer behavior of grobject (3.2.1.1), to reconcile former items
#2,3,4 with event model (5.7.10), by converting them to an example.
- clarify (no functional change) viewer behavior for linkuri (3.2.2.3)
and screentip (3.2.2.6), to make consistent w/ the event model
(5.7.10).
- make 3.4 description of <object> element XHTML friendly (lower
case, etc).
- clarify in 'visibility' (3.2.2.9) and 'interactivity' (3.2.2.10) that
they inherit to/through 'grnode' even though they don't apply.
- clarified / corrected wording of grnode (3.2.1.5)
- added notation definition to 3.1.1.2, and referenced it from 3.2.1.
- added introductory text, clarified wording, flagged issues, in object
behaviors sections (3.1.2.4).
- changed example 3 (3.1.3.4) to avoid deprecated view_context behavior,
fixed examples 5,6,7 for 'zoom' default instead of 'highlight', clarified
wording (e.g., re. target rectangle) in several examples.
- added notation definition before EBNF in 3.1.1.2 (frag. syntax)
- added bullet to 3.1.1.3-#3, specifying (char)+ for xcfterm
- added 3.1.1.5 about resolving relative URI for xcfurl, link that from
3.1.2.6.
- updated RFC 2936 to RFC 3986, Xpointer to REC Xpointer Framework, XML
1.0 2nd Ed to XML 1.0 3rd Ed., HTML 4.0 to HTML 4.01 (throughout the
spec).
- clarified (in 5.4) those parts of CSS2 inheritance model that don't
apply to any WebCGM cases yet.
- ---20050530 editors draft includes all of below
changes---
- implemented AM review editorial comments on Overview (Ch.1) (200505??
email)
- implemented FC review comments (editorial) on 5.7 (20050524 email)
- implemented DL review comments (editorial) on 5.1 - 5.6 (20050506
email)
- clarify that all 3 parts of linkuri must be supplied (even if empty) in
WebCGMs (3.2.2.3) and DOM (5.5).
- moved addEventListener method from WebCGMPicture node (5.7.5) to
WebCGMMetafile node (5.7.3).
- define "mouse region" in common, for prev. "picking region", 'region'
ApsAttr, new events model, etc (3.2.1.1, 3.2.2.1, 5.7.10).
- in 5.5 define validChar for Delimited String (by ref to individual APS
Attr data rules, plus Char. Repertoire 3.1.1.3)
- a Delimited String cannot contain both a QUOTE and an APOSTROPHE within
substring data content (5.5).
- Delimited String containing a single substring is coded identically to
simple string (5.5).
- added "inherit" value for 'visibility' and 'interactivity' -- (3.2.2.9,
3.2.2.10, 4.3), 5.7.6.
- 5.7.5 table: removed Note after it; fixed inaccurate descriptions of
all style properties.
- 5.7.5 table: added Initial Value, add absolute to stroke-weight &
character-height
- 5.7.6, changed 'viewcontext' to simple string, fixed it and 'region'
examples (wsp)
- renamed "style attribute" to "style property" throughout Ch.5 &
Ch.4, including names of methods.
- added a subsection to XCF, describing attribute encoding (4.3.1).
- readability of Abstract improved, Status updated.
- added first-draft terms list for glossary, of DC (Appendix D).
- fixed parameters of Example 4.1 consistently with Ch.5
specifications.
Back to top of appendixes