This is why process models must be completely separate from any execution semantics.
这就是过程模型必须完全和任何执行语义分离的原因。
It is hindered by its lack of standardized execution semantics and persistence format.
缺乏标准的执行语义和持久化格式阻碍了它。
BPEL 1.0, another standard, defined the execution semantics of a workflow process in a runtime.
BPEL 1.0则是另一个标准，定义了运行期中工作流的执行语义。
BPMN 2.0 fixes this by specifying both the modeling semantics as well as the execution semantics.
BPMN 2.0则通过制定模型语义和执行语义解决了这个问题。
For the latter, the BPMN 2.0 execution semantics have been aligned with the BPEL execution semantics.
对于后者，BPMN 2.0执行语义已经跟BPEL执行语义一致了。
The process language doesn't define exact execution semantics for the different activities like BPEL does.
这种过程语言不会象BPEL那样为不同活动定义明确的执行语义。
Finally, it formalizes the execution semantics of BPMN elements, which helps to interpret BPMN process models unambiguously.
最后，它规范化了BPMN元素的执行语义，这有助于清楚地解释BPMN流程模型。
That means, a BPMN process can be deployed and executed on different environments provided they support BPMN 2.0 execution semantics.
这意味着，BPMN流程能被部署和执行于支持BPMN2.0执行语义的各种环境中。
For models that show control flow only, both forms can be used interchangeably and the models will preserve their execution semantics.
对于仅显示控制流的模型，这两种形式可以互换，模型将保留其本身的语义。
(Oracle, Manoj Das) BPMN provides a modeling notation targeted at business analysts, specific to process modeling, and one with execution semantics.
Manoj DasBPMN提供了一种面向业务分析师的建模符号，特别是对于流程建模而言，以及一个具有执行语义的模型。
However, as BPMN 2.0 defines sufficient execution semantics, implementations may start executing BPMN 2.0 natively, creating an overlap with BPEL 2.0.
然而，由于BPMN 2.0定义了充分的执行语义，实现可能会从一开始就直接执行BPMN 2.0，造成和BPEL2.0的重叠。
Activiti takes a different tact, choosing instead to embrace BPMN 2.0, which specifies both execution semantics, as well as the visual description of a process.
Activiti采取的是另一种方式，它使用了BPMN 2.0，后者定义了执行语义和可视化的流程描述。
There were and are quite some discussions on whether BPMN should define execution semantics or whether it should only concentrate on the graphical representations.
对于BPMN是否应该定义执行语义和它是否应该只关注图形表示的问题上，以前和现在都有非常多的讨论。
The task also has a start node, however, this node is optional and does not change the execution semantics of the task, which can only begin execution when the input is available.
该任务也有一个开始节点，不过，这个节点是可选的，不会改变任务的执行语义，这个任务只有在该输入可用的情况下才会开始执行。
For us, the major issues seem to revolve around the execution semantics of a BPMN diagram; for others, it is only a diagram notation and we needn't worry our little heads about execution.
对于我们来说，最大的问题好像是关于BPMN图的执行语义；对其他人来讲，它只是一个图形符号，完全不需要我们操心执行的事儿。
Business Process Execution semantics are difficult to conceptualize.
业务过程执行语义很难概念化。
Business Process Execution semantics are difficult to conceptualize.
业务过程执行语义很难概念化。
应用推荐