Remark / Proposal for create conference function in CCXML

All,

the <createconference> element reqiures an ECMA left hand side
expression that receives the conference id. Additional
requirements define that this id shall be in a "URI format" and
"uniquely addressable and possibly connect to".

With the assumption that the CCXML interpreter and the confenerence
functions are different resources, propably implemented on different
systems, I would further assume that only the conference resource can
generate an identfier with the required characteristics.

Thus to fulfil the requirements the CCXML interpreter has to interact
somehow with the conference resource to obtain such an identifier.
IMO this contradicts with the required asynchronous behaviour of CCXML.

A proposal to modify the "createconference":

1) Remove the constraints "URI format" and "uniquely addressable"
    from this identifier. The identfier itself shall remain to support
    e.g. destroyconference even before a conference.created event
    was thrown. As all other identifiers in the CCXML specification
    it shall be just an identifier with no special or inherited meaning
    (all other identifiers are opaque from CCXML script's point
    of view).

2) Add a new parameter to the conference.created event (e.g.
    "conferenceaddress") that contains the uniquely addressable
    conference id (the current conferenceid parameter shall be the same
    as in "createconference").
    This parameter could be optional if the conference resource does
    not support an "external addressable" behaviour.

These modifications would decouple the CCXML interpreter from the
conference resource and maintain the asynchronous behaviour. In addition
a uniquely addressable conference identifier/address shall be valid only
after the conference was successfully created.

Regards
Werner

Received on Monday, 11 October 2004 19:01:18 UTC