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-16) Primer - Editorial Bucket (non-semantic changes only)

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

Frank Leymann  commented on TOSCA-16:

The reason for using the term "generic type" is that we use "basic type" in the TC in a different manner.  I used "generic" to express that there are types that are domain-independent to a "high degree":  artifact types like JARs, RPMs, SQL DDL, etc but also requirement types like Needs_Shared_Storage or capability types like Can_Auto_Scale can be used in a large spectrum of applications.  The purpose of "6.1 Providing Generic Types" is exactly to explain the concept of artifact types, requirement types, and capability types and emphasize their "generic applicability". There will be no attempt in that section to actually list the artifact types,... required by SugarCRM - this will be in the corresponding sections before. 

It's a valid suggestion to separate Node/Relationship Type Implementations into two separate sections.  Let's discuss this in the Primer call.  My argument to stay with a single section is that both Type Implementations are isomorphic (with the exception that Relationship Type Implementations have no <DeploymentArtifacts> element.

Finally, neither requirement types nor capability types have a corresponding implementation element, i.e. the proposed new section would not fit. 

> Primer - Editorial Bucket (non-semantic changes only)
> -----------------------------------------------------
>                 Key: TOSCA-16
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-16
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Primer 
>            Reporter: Paul Lipton 
> The primer contains examples, overview, value proposition, expanded explanations of key aspects, and much more. 

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]