Hi Paul, You are correct that the syntax for navigating the TOSCA topology graph needs a lot more work. Calin and I have made a number of proposals in the past to address this, based on a concept we call TOSCAPath (which tries to combine graph traversal with JSONPath concepts). This is something we'd love to get into the 2.0 spec. As a workaround for your issue, could you specify a target node type in your requirement definition? If you had a target node type, then the current get_property syntax would allow you to identify the capability property as follows: get_property: [ TARGET, <capability_name>, <capability_property_name ] Chris