Re: [cgmo-webcgm] Ecmascript binding question

["Ulrich Laesche" <ulrich@ematek.de>]

Hi Ben,

I didn't particularly ask for an Ecmascript binding.  My question was how
applications written with bindings from two or more different vendors could
be exchanged.  For example, will it be possible to use one vendors API and
to use another vendors viewer (in case the viewer vendor has the spec
implemented, of course)?

Thanks and regards
Ulrich


----- Original Message -----
From: Benoit Bezaire <benoit@itedo.com>
To: CGM Open WebCGM TC <cgmo-webcgm@lists.oasis-open.org>
Sent: Thursday, August 12, 2004 4:05 PM
Subject: [cgmo-webcgm] Ecmascript binding question


> Hi all,
>
>   We have a question for CGM vendors regarding the Ecmascript binding.
>   During yesterday's call, all the vendors expressed the need for the
>   Ecmascript binding in order to start implementation.  Could it be
>   explained to us (Itedo developers) why that is so?
>
>   Our opinion is that the IDL snippet found in the spec provide all
>   the information needed for implementation.  If you believe that not
>   to be true, could someone please explain.
>
>   To us, an Ecmascript binding is the same as the IDL but using
>   different words.  Example (the DOM Level 2 Attr interface):
>
>   IDL snippet:
>   interface Attr : Node {
>     readonly attribute DOMString        name;
>     readonly attribute boolean          specified;
>              attribute DOMString        value;
>                                         // raises(DOMException) on setting
>
>     // Introduced in DOM Level 2:
>     readonly attribute Element          ownerElement;
>   };
>
>   Ecmascript binding snippet:
>   Object Attr
>   Attr has the all the properties and methods of the Node object as
>   well as the properties and methods defined below.
>   The Attr object has the following properties:
>   name
>       This read-only property is of type String.
>   specified
>       This read-only property is of type Boolean.
>   value
>       This property is of type String and can raise a DOMException object
on setting.
>   ownerElement
>       This read-only property is a Element object.
>
>
>   Could we be explained why this helps?
>
>   Regards,
>
> --
>  Benoit                 mailto:benoit@itedo.com