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-5) Support of <ImplementationArtifacts> within <NodeTemplate> element

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

Thomas Spatzier  commented on TOSCA-5:

Frank and me created a new working draft WD-05 and incorporated the changes as discussed in the last TC meeting.
WD-05 is based on WD-04, since it depends on changes in WD-04. In the new WD-05 document, all changes from WD-04 have been accepted and only the new changes for WD-05 are highlighted.
I also added the Acknowledgements section to the appendix - that had been discussed on the mail list. I listed (in alphabetical order) all Members, Voting Member, and our Chairs as listed in the TC roster. Please let me know if I forgot anyone.

Here is a link to the zip file containing the word document and XML schema:


> Support of <ImplementationArtifacts> within <NodeTemplate> element
> ------------------------------------------------------------------
>                 Key: TOSCA-5
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-5
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Frank Leymann 
>            Assignee: Frank Leymann 
> Today, a <NodeType> element supports the definition of <DeploymentArtifacts> representing executable entities of the node type itself. These deployment artifacts may be overridden or extended or provided first time by another <DeploymentArtifact> element of the referencing <NodeTemplate>.
> This mechanism should be supported for <ImplementationArtifacts> too: A node type may define the implementation artifacts for its operations, but a node template derived from this node type should be able to actually provide an implementation artifact, override an implementation artifact or extend the set of implementation artifacts. For this purpose, the proposal is to add an <ImplementationArtifacts> element to the <NodeTemplate> element as sibling of the <DeploymentArtifacts> element. 

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]