UTP11 — Stereotypes should be decorated with angle brackets «»

Within the descriptional sections, the specification often refers to stereotype names, without showing the typical stereotype brackets («»).
For example:

"A data partition stereotyped classifier..." may be changed to
"A «DataPartition» stereotyped classifier.."

or

"The notation for data partition is a classifier with stereotype data partition."
may be changed to
"The notation for data partition is a classifier with stereotype «DataPartition»."

This should be consequently done along the descriptional sections to increase redeability and consistency, also regarding other UML profile specifications.

The sections need to be harmonized with each other. The contents of the stereotype sections vary from section to section. Sometimes stereotypes are written in upper-case letters (e.g. GetTimezoneAction), sometines in lower-case letters (e.g. default, default application, test component). The same counts for the notation sections of each stereotype. The resolution of this issue aims at aligning the stereotype's section with each other by using the following scheme:
All UML metaclasses are written in camel-case style starting with upper-case letters (e.g. StructuredClassifier)
All UTP concepts are written in lower-case letters (e.g. default application, get timezone action) in the description and semantics section. Whenever a dedidacted UTP concept is referenced, the stereotype style is used (e.g. see «ValidationAction» for further details). In case the concept does not represent a stereotype, the letter-case variant is used (e.g. No additional notation for arbiter defined). - UTP concepts in the examples sections are written in stereotype style («ValidationAction») since the examples section addresses the application of the technical concept, i.e. the stereotype.
UTP concepts in the notation sections are written in stereotype style («ValidationAction») since the notation section addresses the visualization of the technical concept, i.e. the stereotype. When no additional notation is defined for the stereotype, the standardized paragraph “No additional notation for «StereotypeName» defined.” is used.
In the constraint section, the stereotype style («TestContext») is used when the constraints required a particular stereotype to be applied on a UML metaclass (e.g. “a classifier with «TestContext» applied” instead of “a classifier with test context stereotype applied”).