ixcon-2----Page:2
1 2 3 4 5 6 7 8 9 10
|
Basic assumptions Minimal “atom” of conference compose from simple descriptions to build side bars, recurring meetings, policies Scheduling handled externally scheduling system references instances (needed in any event) XCON protocol reference time slots (see later) No XCAP for manipulation, but allow whole document as input to transfer or initialize state No separation between CPCP and CCCP “Flat” documents, rather than deeply layered ones Changes of limits (or rules) don’t affect current state Support simple MCUs that are ignorant of time |