Issue 1455: Declare these attributes as [MANAGER, is_locked, is_read_only] (boca-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: Section 2.2.4 (BOCA Meta-Model in CDL) [is_abstract] relationship_kind BocaRelationshipReference: BocaStructuralFeature { attribute AggregationKind aggregation; attribute boolean implicit_delete=FALSE; attribute boolean implicit_copy=FALSE; attribute boolean implicit_move=FALSE; attribute BocaRelationshipReference with_respect_to; attribute MultiplicityKind multiplicity=MultiplicityKind(0..1); attribute boolean is_navigable=TRUE; relationship inverse References BocaRelationshipReference; }; The following attributes of BocaRelationshipReference should be features of particular subtypes of this abstract type that are inherent features of those relationship subtypes rather than features of instances of the relationship subtypes: ? aggregation ? implicit_delete ? implicit_copy ? implicit_move In other words they should be typemanager-level features rather than instance-level features. Yet, these attributes are not declared with the MANAGER specifier. Recommendation: Declare these attributes as [MANAGER, is_locked, is_read_only]. Resolution: Revised Text: BocaStructuralFeature Actions taken: June 3, 1998: received issue June 23, 1998: closed issue Discussion: End of Annotations:===== *ISSUE 26* Section 2.2.4 (BOCA Meta-Model in CDL) identifiable BocaAttribute: BocaStructuralFeature { {keyword="attribute";}; attribute boolean type_parameter=FALSE; attribute boolean required=FALSE; }; /* attribute */ The fact that the type_parameter attribute appears this far down the meta-model hierarchy means that it is not possible to specify typemanager-level operations and state sets. Recommendation: The type_parameter attribute should be declared in BocaFeature rather than in BocaAttribute.