xml europe 2002 barcelona, 21 - 23 may webcgm dom - external control for web graphics dave...

XML Europe 2002Barcelona, 21 - 23 May

WebCGM DOM - External Control for Web Graphics

Dave CruikshankTechnical Fellow, The Boeing Company

CTO, CGM Open

Ulrich LaeschePresident, Ematek Informatik GmbH


Agenda

• Background

• Application Structuring

• WebCGM Application Structures

• WebCGM DOM Requirements

• Development Status

• Example


Background

• CGM (ISO/IEC 8632)– Computer Graphics Metafile - interchange– Robust 2-dimensional graphics language– Stable – 15 years as an ISO standard– Widely supported – technical documentation,

CAD/CAM, desktop publishing, etc.– Widely profiled – Air Transport Assn, CALS,

AECMA, automotive, telecommunications, etc.


Background - CGM

Version 2 (Am1:1989)

CGM Version 1 (1987)


Defect Corrections

Republish

CGM:1992


Background - CGM

Profiles&Conformance (Am1:1994)

CGM Version 3 (1992)


Defect Corrections

Republish

CGM:1999


Background• CGM Open– Consortium formed in 1998

(www.cgmopen.org)Users Vendors IndependentsBoeingEADSBombardierUS NavyMOD UKXerox(AECMA)

ItedoSys Dev IncLarson S/WAuto-trolEmatekBentley(Corel)

NISTLofton HendersonBruce Garner


Background - WebCGM

• Based on ATA GREXCHANGE

• Extensions for application structuring

• Targeted for technical illustrations– 2D– Line art– Navigation functionality


Background - WebCGM

WebCGM V1.0 (1999)

Defect Corrections

Republish

WebCGM V1.0 Release 2 (2001)


Application Structuring

• Group graphical primitives by type

• Attach attributes to groups to support:– Linking– Information retrieval– Viewer behavior– Etc.


WebCGM Application Structure Types

Picture Body

subparagrobject gdata

layer

para

para

opt

repcho

repcho

gdata – graphicalprimitivesopt – optionalrep – repeatcho – choice

grobject gdata

repcho

grobject gdatapara

gdata


WebCGM Application Structure Attributes

• layer– id– layer Description– layer Name

• grobject– id– region– view Context– linkuri– screentip– name

• para & subpara– id– region– linkuri– screentip– content


WebCGM

• What does that buy us?– The ability to navigate through and

between illustrations• example


WebCGM

• Why a DOM?– Control over viewer behavior externally• Attributes of primitives (color, weight, font,

etc.)• Visibility of objects

– Remove some (most) of the metadata from the CGM file• Context sensitive linking• Context sensitive screen tips


WebCGM DOM requirements

• Metafile level– Access to:• File name• URL• Metafile version• Metafile Description



• Picture level– Access to:• Picture name• VDC extent• Parent• List of children

– Control over:• Links between children



• Graphical primitives– Control over:• Color• Intensity• Line weight• Edge weight



• Layer application structure type– Access to:

• Identifier• Layer name• Layer description• Parent• List of children

– Control over:• Visibility• Links between children



• Grobject application structure type– Access to:

• Identifier• Name• Region• View context• Parent• List of children

– Control over:• Linkuri• Screentip• visibility



• Para and subpara application structure type– Access to:

• Identifier• Region• View context• Content• Parent• List of children

– Control over:• Linkuri• Screentip• visibility



• Application structure graphical primitives– Control over:

• Color• Intensity• Line weight• Edge weight• Text font• Text size• Text scale factor



• Event handling:– OnClick– OnMouseOver– OnMouseOut– OnLoad– OnUnload


DOM Work in Progress

Watch this space

http://www.cgmopen.org

xml europe 2002 barcelona, 21 - 23 may webcgm dom - external control for web graphics dave...

Documents

xml europe

background webcgm webcgm

webcgm dom requirements

webcgm dom external

gdata para gdata slide

background cgm version

dom work

ematek informatik gmbh