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: [OASIS Issue Tracker] Commented: (TOSCA-116) Normative Base Types Proposal (Node/Relationship) - derived from experience with SugarCRM private interop.

    [ http://tools.oasis-open.org/issues/browse/TOSCA-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33699#action_33699 ] 

Alex Heneveld commented on TOSCA-116:

from discussion on 10 Jun 2013 call and chat room, there seems to be agreement to use capabilities instead of types.

Alex Heneveld (Cloudsoft): using Capabilities (as strongly typed mixins) would be more powerful and less brittle than this type hierarchy approach
Alex Heneveld (Cloudsoft): in other words ... the "types" are purely interfaces, they are not implementation; what i'm suggesting is using capabilities essentially as marker interfaces (and possibly no need at all for a type hierarchy!)

Dale Moberg: Mixin as alternative to diamond -- +1 from fan of scala traits!
Travis Tripp (HP): +1 to Alex on Capabilities
Derek Palma (Vnomic): I agree with Alex. Capabilities are really a matching feature. Operations are still on the node, so the resulting selected node has to be able to support the desired.
Paul Lipton (co-chair) : +1 to Alex. Pattern matching seems to meet the use cases better than class hierarchy in many ways.
Paul Lipton (co-chair) : All opinions I just expressed were personal, not co-chair.

> Normative Base Types Proposal (Node/Relationship) - derived from experience with SugarCRM private interop.
> ----------------------------------------------------------------------------------------------------------
>                 Key: TOSCA-116
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-116
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Interop
>            Reporter: Matthew Rutkowski 
> This issue (task) will be used to propose and develop a set of normative, base node and relationship types that will evolve to support Interop. SC use cases.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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