It does however provide a point to which different implementation can trace common semantics. We know that an arch will provide support to an overhanging structure. Conceptually it is irrelevant if the arch is round, lancet or basket-handle. Similarly we know that a notification will carry information from a managed object to a managing object. The exact manner in which this interaction is begun and carried out does not enter into consideration in this component of the model.
Style is an important step in model refinement.
Design patterns are normally devoid of semantics to enhance reusability. For example in large networks, alarm notification by polling would generate a large traffic load and alarm notifications by event forwarding will be the preferred solution in this environment. The degree to which interoperability can be achieved between implementations is also subject the diversity of styles chosen. With greater degrees of stylistic variations the bridge between two protocols will be required to do more than simple message translation. As an example, consider a bridge between a domain where alarm notifications occur through polling and a domain where alarm notifications occur through event forwarding.