- From: Serge Voloshenyuk <serge_voloshenyuk@yahoo.com>
- Date: Tue, 20 Feb 2007 19:46:07 -0800 (PST)
- To: www-voice@w3.org
- Message-ID: <98145.5552.qm@web34312.mail.mud.yahoo.com>
Hi I have question about semantics of <src> attribute of state. Could it mean the same as XInclude? Or some variant of <invoke> with common data space? I mean: In first case: External state set must have common space for ids. Ids must be unique. And transition between included and including set are possible. In this case including machine can't have two different states with the same value for <src> attribute. In second case: Including and included machines has separate namespaces for ids. Crossfile transitions are impossible. Included machine sees main machine's data. But without syntax stateid.dataname. Maybe including machine could see included data too using next syntax: <id of state with src attribute>.dataid. Several states of main machine can have the same src value. As for me second case is more preferable. And I've read in this mailing list that it will be possible to include substate of included machine. Maybe with next syntax: src="url#stateid". If it's correct, than next question: What if included state subtree has transition to state outside included subtree? I think that this feature is possible only if including is interpreted as invoking of external machine with overridded <initialstate> attribute. Your comments? With regards, Serge. P.S. You wrote that new version of draft must be soon. How long could it be? --------------------------------- The fish are biting. Get more visitors on your site using Yahoo! Search Marketing.
Received on Wednesday, 21 February 2007 13:15:57 UTC