Chris Lauwers

The example above shows code that is not very reusable. TOSCA v1.3 addresses this by advertising the `Standard` interface type in the `Root` node type and advertising the `Configure` interface...

Perhaps we need to add a `desired_state` property to the interface. The `state` attribute allows for the definition of a *state machine* associated with the interface that defines the valid...

Yes, getting the state machine right is complicated, and we shouldn't burden template designers with this task. On the other hand, if our goal is to make TOSCA domain-independent, then...

I like the idea of enforcing linear state machines, but that might be difficult to enforce in a parser/validator, especially since an interface might have multiple state variables (e.g., one...

- Perhaps we could initialize the `state` using the `default` keyword? - Do you have examples of a FSM that allows transitions to other states based on return values? I...

It seems to me that the same syntax could be used for modeling synchronous interfaces as for asynchronous interfaces. For example, here is (part of) a synchronous version of an...

> Is a true `precondition` merely enabling the operation or will the orchestrator automatically _execute_ the operation once the `precondition` becomes true? I assume the latter, since otherwise you are...

Presumably, the preconditions can only become true as a result of some event. That same event could also trigger the (enabled) operation. Or, said a different way, in model space...

In this standard state model, what is the difference between "reserve" and "provision"? I'm trying to figure out how these translate into TOSCA concepts such as: - creating a representation...

What I would prefer to do instead is to beef up the **metamodel** section of the document. That section should clearly define the terms that are currently in the glossary....