Actions

Special

Search results

  • ...three tokens to arrive in order to continue the process.[3] Therefore, the semantics of the OR-Join connector is called non-local.[1] * [*1] N. Cuntz and E. Kindler, “On the Semantics of EPCs: Efficient Calculation and Simulation,” Bus. Process Manag., pp.
    2 KB (261 words) - 14:27, 15 January 2021
  • ...rall behaviour of the EPC and cannot be checked locally.[3] Therefore, the semantics of the XOR-Join connector is called non-local. [1] * [*1] N. Cuntz and E. Kindler, “On the Semantics of EPCs: Efficient Calculation and Simulation,” Bus. Process Manag., pp.
    3 KB (410 words) - 14:25, 15 January 2021
  • * [*1] N. Cuntz and E. Kindler, “On the Semantics of EPCs: Efficient Calculation and Simulation,” Bus. Process Manag., pp. * [*3] E. Kindler "On the semantics of EPCs: resolving the vicious circle", Data & Knowledge Engineering - Spec
    2 KB (295 words) - 14:30, 15 January 2021
  • * [*1] N. Cuntz and E. Kindler, “On the Semantics of EPCs: Efficient Calculation and Simulation,” Bus. Process Manag., pp. * [*2] E. Kindler "On the semantics of EPCs: resolving the vicious circle", Data & Knowledge Engineering - Spec
    2 KB (230 words) - 14:30, 15 January 2021
  • ...riggered by a [[function]] and followed by multiple events. <br>Due to the semantics of events as passive elements, they lack the ability to determine the [[eve * [*1] N. Cuntz and E. Kindler, “On the Semantics of EPCs: Efficient Calculation and Simulation,” Bus. Process Manag., pp.
    3 KB (358 words) - 14:27, 15 January 2021
  • == Semantics == * [*2] N. Cuntz and E. Kindler, “On the Semantics of EPCs: Efficient Calculation and Simulation,” Bus. Process Manag., pp.
    6 KB (780 words) - 13:45, 15 January 2021
  • * [*1] N. Cuntz and E. Kindler, “On the Semantics of EPCs: Efficient Calculation and Simulation,” Bus. Process Manag., pp. * [*2] E. Kindler "On the semantics of EPCs: resolving the vicious circle", Data & Knowledge Engineering - Spec
    2 KB (257 words) - 14:26, 15 January 2021
  • ...XOR-Split to be triggered by a function and followed by events. Due to the semantics of events as passive elements, they lack the ability to determine the event == Semantics ==
    8 KB (1,091 words) - 13:49, 15 January 2021
  • ...[Function|function]] and followed by multiple [[Event|events]]. Due to the semantics of events as passive elements, they lack the ability to determine the event == Semantics ==
    8 KB (1,113 words) - 13:46, 15 January 2021
  • == Semantics ==
    6 KB (793 words) - 15:55, 25 January 2021
  • # Semantics ...behavioural aspects of EPC elements. Again, both formal and ontology-based semantics can be created using platform features.
    14 KB (2,169 words) - 15:31, 14 January 2021
  • ...llowing paths can be treaded). Some literature demand that for the sake of semantics and pragmatics splitting paths need to be merged again by the same type of '''Formal semantics'''
    20 KB (2,769 words) - 15:42, 25 January 2021
  • Due to the semantics of events as passive elements, they lack the ability to determine the [[Fun ...ify states with [[Control flow|control flow]] arcs<ref>E. Kindler, “On the semantics of EPCs: Resolving the vicious circle,” Data Knowl. Eng., vol. 56, no. 1,
    9 KB (1,343 words) - 16:43, 25 January 2021
  • * [*2] Ekkart Kindler "On the semantics of EPCs: resolving the vicious circle", Data & Knowledge Engineering - Spec
    4 KB (551 words) - 14:22, 15 January 2021