normative type definitions this section is normative and contains normative type definitions must Except for the examples, be supported for conformance to this specification. The declarative approach is heavily dependent of the definition of basic types that a declarative container must understand. The definition of these types must be very clear such that the operational semantics can be precisely followed by a declarative container to achieve the effects intended by the modeler of a topology in an interoperable manner. Assumptions Assumes alignment with/dependence on XML normative types proposal for TOSCA v1.1 Assumes that the normative types will be versioned and the TOSCA TC will preserve backwards compatibility. Assumes that security and access control will be addressed in future revisions or versions of this specification. TOSCA normative type names normative type has three names declared: Type URI This is the unique identifying name for the type. – These are reserved names within the TOSCA namespace. Shorthand Name This is the shorter (simpler) name that can be used in place of its – corresponding, full Type URI name. These are reserved names within TOSCA namespace that MAY be used in place of the full Type URI. Profiles of the OASIS TOSCA Simple Profile specifcaition SHALL assure non-collision of names for new types when they are introduced. TOSCA type designers SHOULD NOT create new types with names that would collide with any TOSCA normative type Shorthand Name. Type Qualified Name This is a modified Shorthand Name that includes the namespace – prefix which clearly qualifies it as being part of the TOSCA namespace. This name MAY be used to assure there is no collision when types are imported from other (non) TOSCA approved sources. Additional requirements Case sensitivity - Type URI, Shorthand and Type Qualified names SHALL be treated as case sensitive. The case of each type name has been carefully selected by the TOSCA working group and TOSCA orchestrators and processors SHALL strictly recognize the name casing as specified in this specification or any of its approved profiles.
normative type definitions Except for the examples, this section is normative and contains normative type definitions must be supported for conformance to this specification. The declarative approach is heavily dependent of the definition of basic types that a declarative container must understand. The definition of these types must be very clear such that the operational semantics can be precisely followed by a declarative container to achieve the effects intended by the modeler of a topology in an interoperable manner. Assumptions Assumes alignment with/dependence on XML normative types proposal for TOSCA v1.1 Assumes that the normative types will be versioned and the TOSCA TC will preserve backwards compatibility. Assumes that security and access control will be addressed in future revisions or versions of this specification. TOSCA normative type names normative type has three names declared: Type URI – This is the unique identifying name for the type. These are reserved names within the TOSCA namespace. Shorthand Name – This is the shorter (simpler) name that can be used in place of its corresponding, full Type URI name. These are reserved names within TOSCA namespace that MAY be used in place of the full Type URI. Profiles of the OASIS TOSCA Simple Profile specifcaition SHALL assure non-collision of names for new types when they are introduced. TOSCA type designers SHOULD NOT create new types with names that would collide with any TOSCA normative type Shorthand Name. Type Qualified Name – This is a modified Shorthand Name that includes the namespace prefix which clearly qualifies it as being part of the TOSCA namespace. This name MAY be used to assure there is no collision when types are imported from other (non) TOSCA approved sources. Additional requirements Case sensitivity - Type URI, Shorthand and Type Qualified names SHALL be treated as case sensitive. The case of each type name has been carefully selected by the TOSCA working group and TOSCA orchestrators and processors SHALL strictly recognize the name casing as specified in this specification or any of its approved profiles.