It is often useful to parasitically wrap Class elements (like the read-only metaclasses of the UML and SysML profiles for Magicdraw).

Some reasons include:

1. one can't add hyperlinks to read-only elements
2. one can provide a different packaging context - such as relationship to chapters of a technical document that refers to wrapped read-only Class.
3. one can provide a container for documentation and parsed text related to the read-only element

Example: Analysis of SysML1.0 Figure 11.8 - Abstract Syntax for SysML Activity Extensions in MD SysML 15

I use a wrapper Component 11.3.2.3 Discrete to contain information about the SysML stereotype Discrete:

• the <<Discrete>> stereotype is in the read-only SysML Profile.Activities)
• the 11.3.2.3 Discrete Component is the "conformance wrapper" for the stereotype:
  • it carries a hyperlink to a diagram about  the "concept" 11.3.2.3 Discrete as described in the spec (as opposed to the implementation in MD SysML
  • it has a parastic Realizes relationship to SysML Profile.Activities.Discrete (see next images)

This is repeated for each and every stereotype in the specification, which is the basis of the conformance process using UML Parsing Analysis.

Image: