References

If this reference is not set then EObjectActionProvider creates a new Action using AppFactory in newAction() method. If this reference is set and is Action then a copy of the action is created and returned. Otherwise the reference value it is adapted to ActionProvider which is used to create an action. This allows to merge actions and chain action generation. E.g. generate Ecore model documentation and merge it into the Engineering documentation.

Alignments to this aim.

Aims to which this alignable aligns. E.g. a module level principle may align to organization pirinciples.

Map entries

Element documentation, e.g. Markdown documentation.

What needs to be done to achieve the containing Key Result.

Markers pointing to where this model element was loaded from - location, line and column numbers. Multiple markers are supported for situations when a single model element is loaded from multiple locations, e.g. a row in an Excel document or a database and then pom.xml and readme.md is a source repository. Another possiblity is an element being created from a prototype and then loaded - in this case the object will inherit markers from its prototype and will have a marker point to the location where it was loaded from. Markers are listed in the reverse order, i.e. the prototype marker would be after the load marker in the list.

Pluggable representations of a model element, e.g. a component diagram for modules.

Resources associated with the element, e.g. documentation.

Sections for model element documentation.

Table of contents configuration.