Every ArchiMate concept may carry attributes, and elements and relationships are enriched with supplementary information through the profiling mechanism. A profile must be defined as a set of typed attributes, may be coupled to concepts dynamically at the user's discretion, and may give each attribute a user-changeable default. Tools that support the language must be able to implement predefined profiles, and a profile definition language must allow users to define new profiles that add attribute sets to existing element or relationship types.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.