Issue 1715:  Navigability constraint expressed wrongly (mof-rtf)
Source:  (, )
Nature:  Revision
Severity:  Minor
Summary: Summary: The "is_navigable" attribute on AssociationEnd is intended to allow
 a modeler to prevent the creation of References for the end.  Unfortunately
 the Constraint that expresses this is on the AssociationEnd and the
 "is_navigable" attribute rather than on Reference.  This means that 
 the existence of References constrains the value of "is_navigable"
 rather than the other way around.
 

Resolution: closed, no action required
Revised Text: 
Actions taken:
July 22, 1998: received issue
July 24, 1998: closed issue
Discussion: 
This is a duplicate of #Issue1712
Implementation: No action required on this duplicate. Done [KR].
End of Annotations:=====
Return-Path: <crawley@dstc.edu.au>
Resent-Message-Id: <199807221129.VAA17177@piglet.dstc.edu.au>
To: mof-rtf@omg.org
Subject: Navigability constraint expressed wrongly
Date: Wed, 22 Jul 1998 16:40:27 +1000
From: Stephen Crawley <crawley@dstc.edu.au>
Resent-To: issues@omg.org
Resent-Date: Wed, 22 Jul 1998 21:29:17 +1000
Resent-From: Stephen Crawley <crawley@dstc.edu.au>


Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au)
Nature: Revision
Severity: Minor

The 'is_navigable' attribute on AssociationEnd is intended to allow
a modeler to prevent the creation of References for the end.
Unfortunately
the Constraint that expresses this is on the AssociationEnd and the
'is_navigable' attribute rather than on Reference.  This means that 
the existence of References constrains the value of 'is_navigable'
rather than the other way around.