The TC tentatively approved this approach on 10/25:

a. Artifact Types
• The kind of executables and their invariant properties/metadata
• Variant metadata that need to be described in body of artifact-specific content of corresponding element or in corresponding block of TOSCA.meta file
b. Requirements and Capabilities
• Distinguish between quality of services (scalability, availability, pricing,...) and dependencies  QoS become Policies, dependencies become Requirements and Capabilities
c. Explain that this is done "once and forever" by vendor consortium  primer will define samples (i.e. non-normative) for the types SugarCRM requires