W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2008

Re: CCXML <startdialog> question - ISSUE-113

From: RJ Auburn <rj@voxeo.com>
Date: Thu, 27 Mar 2008 08:02:23 -0400
Cc: www-voice@w3.org, W3C Voice Browser Working Group <w3c-voice-wg@w3.org>, Hrvoje Nezic <hrvoje.nezic@envox-lab.hr>
Message-Id: <1385633B-51D0-4001-9654-1152B1B1A14D@voxeo.com>
To: Petr Kuba <kuba@optimsys.cz>

Petr

Since we have not heard any response we are going to assume you are ok  
with our resolution of this problem. We have closed out this issue in  
our issue tracker.

Thank you once again for your feedback to the CCXML specification.

Best regards,

	RJ

---
RJ Auburn
CTO, Voxeo Corporation
tel:+1-407-418-1800



On Feb 14, 2008, at 10:00:27, RJ Auburn wrote:
>
> Peter,
>
> For now the CCXML working group feels that this feature is not in  
> scope for CCXML 1.0 but could be considered for 1.1. The current  
> text and a number of the underlying models assume that dialogs do  
> not work in this way and based on some informal polling it does not  
> sound like we would be able to get the required number of  
> implementation reports to require support for this feature at this  
> time.
>
> If this resolution is not acceptable to you please let us know by  
> March 6th 2008 otherwise we will assume this is ok and go on ahead  
> and defer it to a future release of CCXML.
>
> Best regards,
>
> 	RJ
> ---
> RJ Auburn
> CTO, Voxeo Corporation
> tel:+1-407-418-1800
>
>
>
> On Nov 28, 2006, at 02:53:38, Petr Kuba wrote:
>
>>
>> Hi,
>>
>> > Do you have a use case that would require this functionality? If  
>> so it's something we could consider for
>> > future versions.
>>
>> I have a use case. This feature is useful for solutions we develop  
>> in OptimSys.
>>
>> Consider a dialog reporting current time. This dialog can run  
>> continually and connections just join to it. It means that at the  
>> beginning there is no connection joined.
>>
>> Generally speaking, since it is allowed to unjoin a connection and  
>> a dialog (which results to a dialog not being joined to any  
>> connection) why it is not allowed to start a dialog in unjoined  
>> state?
>>
>> Regards,
>> Petr
>>
>> -- 
>> Petr Kuba, Project Manager
>> OptimSys, s.r.o
>> kuba@optimsys.cz
>> Tel: +420 541 143 065
>> Fax: +420 541 143 066
>> http://www.optimsys.cz
>>
>>
>>
>> RJ Auburn wrote:
>>>
>>> Hrvoje,
>>>
>>> As the spec is currently written the assumption would be that you  
>>> can NOT start dialogs that are detached from both Conference and  
>>> Connection ID's.
>>>
>>> Do you have a use case that would require this functionality? If  
>>> so it's something we could consider for future versions.
>>>
>>> Thanks,
>>>
>>>   RJ
>>>
>>> ---
>>> RJ Auburn
>>> CTO, Voxeo Corporation
>>> tel:+1-407-418-1800
>>>
>>>
>>>
>>> On Nov 27, 2006, at 11:58 AM, Hrvoje Nezic wrote:
>>>
>>>> Dear group,
>>>>
>>>> I would highly appreciate if someone would clarify usage of  
>>>> connectionid and conferenceid
>>>> attributes of <startdialog> element.
>>>>
>>>> The question is:
>>>> Is it possible to start a dialog which is not joined with a  
>>>> connection or a conference, and join the dialog later by an  
>>>> explicit <join>?
>>>>
>>>> The specification states the following:
>>>>
>>>> "If both the connectionid and the conferenceid are omitted and  
>>>> the dialog was previously prepared using a dialogprepare element  
>>>> with a connectionid or conferenceid specified, the interpreter  
>>>> must use the id as specified on the dialogprepare element.
>>>> If neither the connectionid or conferenceid is specified and the  
>>>> dialog had not previously been prepared, the interpreter must use  
>>>> the id indicated in the current event being processed."
>>>>
>>>> But specification doesn't say what happens if the current event  
>>>> is not a connection or conference event, and so doesn't have a  
>>>> connection or conference id. Is it an error, or is it allowed,  
>>>> meaning that the dialog is not joined with a connection or  
>>>> conference?
>>>>
>>>> Thanks!
>>>>
>>>
>>
>>
>
>
Received on Thursday, 27 March 2008 12:03:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 27 March 2008 12:03:50 GMT