SNIP_ADAPTIVE_COM_FIGURE_Figure_4_3_MANIFESTSPECIFICATION

Figure 4.3: Specification of namespaces in PortInterfaces [TPS_MANI_01004] Semantics of ServiceInterface.namespace ⌈The aggregation ServiceInterface.namespace shall be used to define the namespace to be used for the source code that corresponds to the given ServiceInterface.⌋ [TPS_MANI_01005] The definition of the namespace of a ServiceInterface may follow a hierarchical pattern ⌈The namespace of a ServiceInterface may follow a hierarchical pattern, as supported by many modern programming languages. The separator between the elements of the hierarchical namespace definition depends on the used programming language and is not explicitly defined in the model. The model only defines the elements of the hierarchical namespace pattern. ⌋ <SERVICE-INTERFACE> <SHORT-NAME>MyServiceInterface</SHORT-NAME> <NAMESPACES> <SYMBOL-PROPS> <SHORT-NAME>first</SHORT-NAME> <SYMBOL>com</SYMBOL> </SYMBOL-PROPS> <SYMBOL-PROPS> <SHORT-NAME>second</SHORT-NAME> <SYMBOL>myCompany</SYMBOL> </SYMBOL-PROPS> <SYMBOL-PROPS> <SHORT-NAME>third</SHORT-NAME> <SYMBOL>software</SYMBOL> </SYMBOL-PROPS> </NAMESPACES> </SERVICE-INTERFACE> Listing 4.1: Example for the definition of a namespace for a given ServiceInterface As the consequence of the ability to define a hierarchical namespace, the aggregation ServiceInterface.namespace is qualified as being ordered. This means that the order of individual elements to the collection of namespaces has a semantical relevance 1. 1This means that the definition of a namespace a::b is semantically different from the definition of a namespace b::a.