Introduce matching rule 'none'

docs/2_4_common_schema.adoc

@@ -1892,7 +1892,7 @@ The terminal name must be unique on each level.
 
 [[matchingRule,`matchingRule`]]
 The normalized string attribute `matchingRule` describes the rules for variable matching in a connection of terminals.
-As detailed in <<table-predefined-matching-rules>>, there are three predefined matching rules: `plug`, `bus`, and `sequence`.
+As detailed in <<table-predefined-matching-rules>>, there are four predefined matching rules: `plug`, `bus`, `sequence`, and `none`.
 Other standards may define new matching rules.
 In order to avoid ambiguities and conflicts, rule names must follow the reverse domain notation of a domain that is controlled by the entity defining the semantics and content of the additional entries.
 The rule names beginning with `org.modelica` and `org.fmi-standard` are explicitly reserved for use by layered standards defined by Modelica Association or its own projects (<<MAP,MAPs>>).
@@ -1919,6 +1919,11 @@ An importer may connect terminals if some or no terminal member variables are pr
 |Matching of the variables is based on the order of the terminal member variables.
 An importer should connect terminals only if the number of member variables matches.
 
+[[none,`none`]]
+|`none`
+|Matching of the variables is not intended by the creator. 
+An importer may connect terminals based on the user's additional input.
+
 |====
 
 [[terminalKind,`terminalKind`]]