You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon every major release the latest version of `master` is tagged `v<major>.0`. The maintenance of this release is performed on a support branch `support/v<major>.x` starting at this tag.
Upon every major release the latest version of `master` is tagged `v<major>.0`. The maintenance of this release is performed on a support branch `support/v<major>.x` starting at this tag.
Releases and pre-releases are tagged on the respective branches following the [Semantic Versioning](https://semver.org/) when the API, XSD schema or file structure of the FMU archive change.
Releases and pre-releases are tagged on the respective branches following the [Semantic Versioning](https://semver.org/) when the API, XSD schema or file structure of the FMU archive change.
@@ -269,7 +269,7 @@ When writing or editing the specification documents please follow the [AsciiDoc
269
269
- Use Atx style [section titles](https://asciidoctor.org/docs/asciidoc-recommended-practices/#section-titles)
270
270
- Use four dashes (`----`) for [delimited blocks](https://asciidoctor.org/docs/asciidoc-recommended-practices/#delimited-blocks)
271
271
- Use the asterisk (`*`) as marker for nested [lists](https://asciidoctor.org/docs/asciidoc-recommended-practices/#lists)
272
-
- Use angle brackets and backticks when citing XML elements.
272
+
- Use angle brackets and backticks when citing XML elements.
273
273
Example:
274
274
```
275
275
The internal step size can be provided by the attribute <<fixedInternalStepSize>> in element `<fmiModelDescription><CoSimulation>`.
@@ -287,7 +287,7 @@ Quotes must only be included if they are part of the original source or markup c
287
287
288
288
### Cross References
289
289
290
-
When creating a [cross reference](https://asciidoctor.org/docs/asciidoc-writers-guide/#cross-references) (xref) use dash-separated, all-lowercase names.
290
+
When creating a [cross reference](https://asciidoctor.org/docs/asciidoc-writers-guide/#cross-references) (xref) use dash-separated, all-lowercase names.
291
291
Example:
292
292
293
293
```
@@ -298,7 +298,7 @@ Example:
298
298
These parts are defined in <<fmi-common-concepts>>.
299
299
```
300
300
301
-
To reference a function, type, definition or argument, use its name as xref and add a pre-formatted label. Do not add brackets to function names.
301
+
To reference a function, type, definition or argument, use its name as xref and add a pre-formatted label. Do not add brackets to function names.
302
302
Example:
303
303
304
304
```
@@ -315,16 +315,16 @@ A Clock interval is set by the environment for the current time instant by the f
315
315
316
316
### Spelling and Capitalization
317
317
318
-
- Names start with a capital letter.
319
-
Example:
318
+
- Names start with a capital letter.
319
+
Example:
320
320
> A Co-Simulation FMU is different from a Model Exchange FMU.
321
321
322
-
- General concepts are lower case.
323
-
Example:
322
+
- General concepts are lower case.
323
+
Example:
324
324
> A co-simulation environment is different from a model exchange environment.
325
325
326
-
- Segments of C or XML are cited exactly as they appear in the code.
327
-
Example:
326
+
- Segments of C or XML are cited exactly as they appear in the code.
327
+
Example:
328
328
> The <<fmiModelDescription>> of a Model Exchange FMU must contain a `<ModelExchange>` element.
329
329
330
330
- Headings are to be capitalized with the following rules:
@@ -333,7 +333,7 @@ A Clock interval is set by the environment for the current time instant by the f
333
333
334
334
### Non-ASCII Characters
335
335
336
-
To avoid encoding problems AsciiDoc files may only contain ASCII characters. Non-ASCII characters can be escaped using the decimal representation of the Unicode character.
336
+
To avoid encoding problems AsciiDoc files may only contain ASCII characters. Non-ASCII characters can be escaped using the decimal representation of the Unicode character.
337
337
Example:
338
338
339
339
```
@@ -365,7 +365,7 @@ will be rendered as
365
365
366
366
### Italic Paragraphs
367
367
368
-
Every line of an italic paragraph (e.g. in non-normative text) should be surrounded by underscores, so the text is highlighted correctly in code editors.
368
+
Every line of an italic paragraph (e.g. in non-normative text) should be surrounded by underscores, so the text is highlighted correctly in code editors.
0 commit comments