Automating Google Workspace (GWS) & more with Apps Script
Partner Generation for Petri Net Based Service Models
1. Partner Generation for Petri Net Based Service Models Karsten Wolf (= Karsten Schmidt) Universität Rostock Open Workflow Nets
2. Wellformedness Workflow nets: Soundness - always possible to reach end state - every transition reachable open Workflow nets: There exist partner(s) such that - always possible to reach end state (Controllability) - every transition reachable (Transition covering)
11. Example for a reduction rule I Do not send messages that cannot be consumed in the future of at least one state Preserves most permissive partner
12. Example for a reduction rule II Do not send anything as long as you can receive something Does not preserve most permissive partner !b
13. Decentralized partner generation traced back to centralized case: C 1 ... C n C 1 || ... || C n Approach: as central case, but remove - bad states - states where actions belonging to different parties are not commutative Algorithm is nondeterministic
27. Synchronous interaction Simultaneous occurrence relevant (irrelevant in asynchronous case) Otherwise, same algorithms applicable
28.
29. Justification of construction (centralized partner) K(q) = { m | [m,q] reachable in composed system} … remember construction …
30.
31.
32. Properties of partners II a b c a b ac bc c a b c b bc c a b c a c not knowledge-aware knowledge-aware P w.r.t. N knowlegde-aware iff removing all but one incoming edges does not change K(q)
33.
34.
35. Ad 2. mb ka mb ka kd Idea: merge states q, q‘ with K(q) = K(q‘) a b c , a b, , a c, , a b, , a c, a b a c c a b a Not knowledge driven Knowledge-driven