Chris Lauwers

I envision *declarative policies* to be defined using a set of invariants, i.e. Boolean expressions that must hold true at all times. However, this will likely require extensions to our...

I second Paul's proposal.

Thanks @pmjordan. We'll make this a discussion topic for the Language Ad-Hoc once we finish substitution/requirement mappings.

> > So when we open up for custom extensions to the TOSCA 1.3 scalar units, we need to allow built-in units that do not follow the symbol-multiplier scheme. I...

My interpretation is that such a range is acceptable. Implementations should also be able to verify that `$equal(60 s, 1 h)` is `True`

In Version 2, a relationship type is mandatory for requirements. As stated in https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd05/TOSCA-v2.0-csd05.html#_Toc125468856 , it can be specified either in the requirement assignment or in the requirement definition: ```...

My apologies, but I believe I have an error in the filter clause in the above example. I think the condition in the filter needs a `get_property` function to work...

Node filters now use boolean expressions as documented in https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd05/TOSCA-v2.0-csd05.html#_Toc125468604. Using this syntax, the example above would look as follows: ``` tosca_definitions_version: tosca_2_0 capability_types: Host: {} relationship_types: HostedOn: {} node_types:...

Comments are not supposed to show up in the rendered document, only in the markdown text itself. If comments show up (such as the Mike Rehder comment you're referencing) that...

In order to automatically create workflows, we need to define: 1. State machines for the interfaces defined for nodes and relationships. This is described in https://github.com/oasis-open/tosca-community-contributions/issues/147 2. How are relationship...