Open aszs opened 2 years ago
In my opinion, capabilities (and requirements) are the “ports” through which nodes interact with one another (by establishing relationships) and as such capabilities don’t have lifecycles of their own. I don’t see any use cases for interfaces on capabilities that are decoupled from interfaces on the nodes that contain these capabilities.
From: Philippe Merle @.> Sent: Friday, March 11, 2022 4:18 AM To: oasis-open/tosca-community-contributions @.> Cc: Subscribed @.***> Subject: Re: [oasis-open/tosca-community-contributions] Allow interfaces on capabilities? (Issue #72)
What are the use cases where interfaces on capabilities would be needed?
— Reply to this email directly, view it on GitHubhttps://github.com/oasis-open/tosca-community-contributions/issues/72#issuecomment-1065061324, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AASPLIJLHGWCQJ3GMGP6QULU7M2WLANCNFSM5QNLMGGQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you are subscribed to this thread.Message ID: @.**@.>>
What are the use cases where interfaces on capabilities would be needed?