Merge pull request #79 from OpenSimulationInterface/add_bibliograhpy_entries_osmp

Added bibliography entries. Relates to OpenSimulationInterface/open-s…

Author: Stefan Cyliax

doc/spec/basic_conventions.adoc

@@ -1,7 +1,7 @@
 = Basic conventions
 
-The model shall be packaged as a valid FMU for co-simulation, as specified in the FMI 2.0 standard.
-Unless otherwise noted, all specifications in the FMI 2.0 standard apply as-is.
+The model shall be packaged as a valid FMU for co-simulation, as specified in the FMI 2.0 standard cite:[fmi2.0].
+Unless otherwise noted, all specifications in the FMI 2.0 cite:[fmi2.0] standard apply as-is.
 
 The following annotation shall be placed into the `<VendorAnnotations>` element of the `modelDescription.xml` to mark the FMU as being conformant to this version of the specification:
 

doc/spec/binary_variables.adoc

@@ -1,12 +1,12 @@
 = Binary variables
 
-FMI 2.0 does not directly support the efficient exchange of arbitrary binary data between FMUs.
-OSMP therefore introduces the concept of notional binary variables that are mapped to actual integer variables for use with FMI 2.0.
+FMI 2.0 cite:[fmi2.0] does not directly support the efficient exchange of arbitrary binary data between FMUs.
+OSMP therefore introduces the concept of notional binary variables that are mapped to actual integer variables for use with FMI 2.0 cite:[fmi2.0].
 Future FMI versions will directly support binary variables compatible with this concept.
 
 A notional binary variable named `<prefix>` is defined using the following conventions:
 
-The name of the notional binary variable given by `<prefix>` shall be a valid structured name according to FMI 2.0.
+The name of the notional binary variable given by `<prefix>` shall be a valid structured name according to FMI 2.0 cite:[fmi2.0].
 
 The FMU shall not contain any other variable that is named `<prefix>`.
 This restriction ensures that there is no conflict between notional binary variables and actual variables.