OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [tosca] Property VS Capability


Hi Luca,

 

Properties and capabilities are very similar. The main difference is that capabilities can be the target of a relationship. Either way, properties and capabilities (which can have sub-properties) specify values for state of the component.

 

Chris

 

From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of Luca Gioppo
Sent: Thursday, June 11, 2015 6:49 AM
To: TOSCA
Subject: [tosca] Property VS Capability

 

On H.1.2.4 it seems to me that we are using Capabilities in place of Properties.

 

Shouldn't the Capability declare "what the node is capable of" and the Property the "desired state"?

in that case the example is wrong the get_input should go on a property of the Property section not of the capability.

To be honest all the Compute specification is following this strange approach where no properties seems to be defined but only capabilities and seems to be uncorrect.

 

Will open a Jira for this.

 

Luca



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]