Du Li and Richard R. Muntz. A Collaboration Specification Language. Proceedings of the 2nd USENIX Conference on Domain Specific Languages (DSL'99), Oct. 1999, Austin, Texas  Home/Search   Document Details and Download   Summary   Related Articles   Check

....for capturing and recording state information regarding the ongoing collaboration. In our COCA implementation of the presence awareness system, the PA Server Database and the PA Controllers each are implemented as a cocavm. Policies are specified by the user in the COCA specification language [19], in the form of inference rules. The inference engine in the cocavm is part of the PA Controller. Upon receipt of a message from either the local user interface or from remote sites, the cocavm evaluates the inference rules for a match. The corresponding inference rule is then fired. The ....

D. Li and R. R. Muntz. A collaboration specification language. In Proceedings of the 2nd USENIX Conference on Domain Specific Languages, Oct 1999.

....for capturing and recording state information regarding the ongoing collaboration. In our COCA implementation of the presence awareness system, the PA Server Database and the PA Controllers each are implemented as a cocavm. Policies are specified by the user in the COCA specification language [19], in the form of inference rules. The inference engine in the cocavm is part of the PA Controller. Upon receipt of a message from either the local user interface or from remote sites, the cocavm evaluates the inference rules for a match. The corresponding inference rule is then fired. The ....

D. Li and R. R. Muntz. A collaboration specification language. In Proceedings of the 2nd USENIX Conference on Domain Specific Languages, Oct 1999.

....part only handles object rendering. So the implementation of the user interface is greatly simplified and easy to extend. The coordination part which implements policies such as awareness control, access control, and concurrency control is specified in a powerful logic based coordination language[18] and enforced by the COCA runtime system, a copy of which runs at each participant site to monitor and control its interaction with other sites. Coordination policies can be dynamically changed on the fly[19] and are subject to verification[20] In particular, we have shown in [17] how the same ....

Du Li and Richard R. Muntz. A Collaboration Specification Language. Proceedings of the 2nd USENIX Conference on Domain Specific Languages (DSL'99), Oct. 1999, Austin, Texas

....sampling and propagation. 3. SYSTEM ARCHITECTURE CAB allows users to define new object types (UDTs) new operations (UDOs) and object relationships (UDGs) All the definitions can be done either by using a scripting lan Figure 2: Relate objects to a UDG instance. guage, as is presented in [23], or by demonstration, as will be discussed in Section 4. UDOs and UDGs have been introduced in the previous section. A UDT is used to avoid repetitive drawing of a set of objects. Each instantiation of a UDT will draw the set of objects automatically. It is a concept di#erent from UDG in that the ....

....module interacts with the user directly. It takes care of object rendering and user input event trapping. The data structures each have a set of APIs defined allowing for manipulation of the corresponding data. The engine interprets scripts written in a language that is based on first order logic [23]. The engine has two ports to interact with engines in other CAB processes, which is the basis for coordination among multiple CABs. A clean interface is defined between the engine and the kernel modules: When a UDT UDO UDG script is loaded by the engine, either from a configuration file or from ....

[Article contains additional citation context not shown here]

D. Li and R. R. Muntz. A collaboration specification language. In Proceedings of the 2nd USENIX Conference on Domain Specific Languages (DSL'99), Austin, Texas, Oct. 1999.

....and supporting collaborations over the Internet. In our approach, coordination policies are separated from user interfaces and other computation modules in building collaborative systems. Compared to similar systems, e.g. DCWPL[2] and Trellis[10] we provide a logic based specification language [18] to describe coordination policies, which features constructs for efficient and flexible group communication and for modular and object oriented policy specification and composition. We use roles as a unit to specify a wide range of coordination policies including access control, concurrency ....

....Their meaning and usage will be discussed in the remainder of this section. As a matter of fact, it would be tedious for the user to specify all the meta policies for each collaboration from scratch. We also provide language constructs to support policy reuse and composition which are discussed in [18]. drawer role moderator role DB COCA Console: cocash whiteboard tool: wb floor control tool: mt cocavm cocavm bootstrap collaboration bootstrap role stub (skeleton) meta out meta in Fig. 10. Meta policy for runtime dynamics. In Figure 10, filled boxes denote meta policy code ....

Du Li and Richard R. Muntz. A Collaboration Specification Language, to appear in Proceedings of the 2nd USENIX Conference on Domain Specific Languages (DSL'99), Oct. 1999, Austin, Texas

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC