FIXED - CSD03 - Define normative Artifact Types (including deployment/packages, impls., and runtime types)

A) Runtime Types:

• It has been suggested we have "Software Library" types such: PHP and Java
• perhaps these can be "Features" that are expressed as capabilities of WebServers and as Requirements by WebApplication Node Types

B) Deployment Types:

• We know that we need to express RPMs, ZIP an TAR in someway and describe what dependent "provider" tooling is needed on different platforms to accomplish an installation
• Thomas commented on "RPM" types the following: "Or should we make this more generic like "OS-Package" that can have a type "rpm", "deb" etc. and then the respective installer gets selected based on package type?"

C) Implementation Types:

• We know we need to describe "Bash" (.sh) scripts. If so (and OpenStack is a target impl. for TOSCA YAML), we should look at defining (normatively) Chef and Puppet as well.
• Thomas commented: "I would make this more generic, e.g. "Script" which can have a script language property to select the interpreter"