Skip to content

Commit

Permalink
Split of normative part.
Browse files Browse the repository at this point in the history
  • Loading branch information
HansOlsson committed Sep 8, 2020
1 parent b998695 commit 711326c
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions chapters/annotations.tex
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,7 @@ \chapter{Annotations}\label{annotations}
Annotations are intended for storing extra information about a model,
such as graphics, documentation or versioning, etc. A Modelica tool is
free to define and use other annotations, in addition to those defined
here, according to \cref{vendor-specific-annotations}. The only requirement is that any tool
shall save files with all annotations from this chapter and all
vendor-specific annotations intact. To ensure this, annotations must be
here, according to \cref{vendor-specific-annotations}. Annotations must be
represented with constructs according to the Modelica grammar (for
replaceable class declarations with a constraining-clause also refer to
\cref{constraining-clause-annotations}). The specification in this document defines the
Expand All @@ -16,7 +14,9 @@ \section{Vendor-Specific Annotations}\label{vendor-specific-annotations}

A vendor may -- anywhere inside an annotation -- add specific, possibly
undocumented, annotations which are not intended to be interpreted by
other tools. Two variants of vendor-specific annotations exist; one
other tools. The only requirement is that any tool
shall save files with all vendor-specific annotations (and all annotations from this chapter) intact.
Two variants of vendor-specific annotations exist; one
simple and one hierarchical. Double underscore concatenated with a
vendor name as initial characters of the identifier are used to identify
vendor-specific annotations.
Expand Down

0 comments on commit 711326c

Please sign in to comment.