In the following image we see a parsing ot the familiar UML2.1.2 specification text for 7.3.14 Element (from Kernel) into stereotyped Components as relatable parsing containers. For comparison, the process is repeated for selected text snippets with Comments.

Pros of the Component vs Comment as a "parsing container":

• Can package a dedicated diagram that features the relatable parsing container Component and its text, with its related elements (see next page)
  • TIP: drag that "focus" diagram from the browser onto the parsing container Component to make it the active hyperlink of the container !
  • A Comment can't even really package (let alone package a focus diagram) !
    • (Note that in MagicDraw UML and Comment can contain nested Comments, only)
• Parsing container Components can be nested to form a parsed text tree (and traced using ComponentRealization)
• Can parasitically "wrap" other elements to form logical views of them without "stealing ownership".
  • this is also the major advantage of Component over Artifact (or other Classifiers) as a relatable parsing container.

Cons of the Component vs Comment as "parsing container":

• Can't be related via a Dependency easily to the Property at an Assocation end:
  • when a Property is available to target as an attribute in the attributes compartment this is no problem
  • a Comment handle can be correctly drawn to a Property at an Assocation end

Note the use of tagged values with enumeration literals to describe clearly the source and "coordinates" of the parsed text (in this case from the UML2.1.2 spec) in the parsing containers. In general, try to get as much text out of the parsing container's name, and into the model in this way.

Image: