Merge pull request #195 from pmai/fix/highcut_variable_names

Only recommend high-cut variable names

docs/3____physical_signal_abstraction.adoc

@@ -124,8 +124,10 @@ All <<high-cut-terminal-member-variable-for-signals,`TerminalMemberVariables`>>
 <<high-cut-pdu-terminal,PDU terminals>> list all the contained signals as `<TerminalMemberVariable>`.
 
 Attribute definitions::
- * `variableName` refers to the input or output variable name of the FMU and to enforce uniqueness is built as follows: `BusName.FrameName.PDUName.SignalName`, e.g., `Powertrain.tcuSensors.tcuSensors.vCar`.
+ * `variableName` refers to the input or output variable name of the FMU.
     These variables represent the signal abstraction layer ("high cut").
+    Unless there are other requirements, it is recommended to build the variable names as follows: `BusName.FrameName.PDUName.SignalName`, e.g., `Powertrain.tcuSensors.tcuSensors.vCar`.
+    This approach automatically provides unique names for all bus-related variables, and can also be used for the clock variables, to allow automatic grouping by non-terminal-aware tools.
  * `memberName` is the `SignalName` as given in the <<high-cut-network-description-files>>, e.g., `vCar`, if given.
     This is redundant information but simplifies signal name extraction.
  * `variableKind` is `signal`.