Issue 10963: Global variables (voice-ftf)
Source: France Telecom R&D (Mr. Mariano Belaunde, mariano.belaunde(at)orange.com)
Nature: Uncategorized Issue
Severity: 
Summary: Should we allow global variables between dialogs that are not 
connected (as it is currently)? 


Resolution: (1)	In Section 8.3.1 Dialog, at the end of the actual property list, add a 'standalone' property with the following definition: "states whether the dialog is allowed to refer to global variables. If standalone is True no global variables can be used.
(2)	Update Figure 8.5 by adding the Boolean standalone property in class Dialog.
(3)	In the Textual syntax section (Section 10) add the 'standalone' keyword in the list of reserved words and adjust the BNF rule for dialog as follows:
Replace the definition of the 'dialog_head' non terminal by:
			'dialog_head : 'standalone'? dialog_kind ID within_dialog_opt'

Revised Text: 
Actions taken:
April 20, 2007: received issue
November 7, 2007: closed issue
Discussion: 
Because in most cases dialogs and invoked sub-dialogs execute in the same address space global variables were introduced. However it could be interesting to allow an end-user to declare that a Dialog definition is not depending on global variables of a containing dialog. To this end the resolution proposed below enables the ability to declare "standalone" dialogs.
End of Annotations:=====
s is issue # 10963	From: "BELAUNDE Mariano RD-MAPS-LAN" <mariano.belaunde@orange-ftgroup.com>

Global variables

Should we allow global variables between dialogs that are not 
connected (as it is currently)?