Issue 7407: The specification is fond of using 'typically.' (uml2-rtf) Source: (, ) Nature: Clarification Severity: Minor Summary: The specification is fond of using 'typically.' The term should be use with care in a specification. Typically, 'must' or 'may' are better choices. For example, at 7.4.1 p.42: The multiplicity bounds are typically shown in the format: lower-bound..upper-bound It will be better to write: The multiplicity bounds are shown in the format: lower-bound..upper-bound simply deleting 'typically.' (In this case, the syntax specification should show the case when the two bounds are equal.) Resolution: Revised Text: Actions taken: May 31, 2004: received issue August 23, 2006: closed issue Discussion: This is indeed a valid issue, since the term typically (sorry!) leads to confusion and ambiguity that should not be encountered in a spec. Unfrotunately, there are 72 uses of this term in the current spec and each one would have to be reviewed individually. This does not seem feasible in the short time left for the work of this FTF. Therefore, it is work that should be picked up by a subsequent RTF.======================The discussion associated with the resolution to issue 6456 equally applies here (except that there are 71 uses of this term and its derivatives – still a very large number). Disposition: Closed, no change End of Annotations:===== m: webmaster@omg.org Date: 31 May 2004 23:54:11 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Joaquin Miller Company: X-Change Technologies mailFrom: no@but.thanks Notification: Yes Specification: UML Section: throughout FormalNumber: ptc/03-08-02 Version: 2.0 RevisionDate: 8/-/3 Page: Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Opera 7.22 [en] Description The specification is fond of using 'typically.' The term should be use with care in a specification. Typically, 'must' or 'may' are better choices. For example, at 7.4.1 p.42: The multiplicity bounds are typically shown in the format: lower-bound..upper-bound It will be better to write: The multiplicity bounds are shown in the format: lower-bound..upper-bound simply deleting 'typically.' (In this case, the syntax specification should show the case when the two bounds are equal.) Reply-To: Joaquin Miller X-Sender: jm-acm.no@sbcglobal.net@pop.sbcglobal.yahoo.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 25 Jun 2004 14:38:12 -0700 To: UML Superstructure FTF From: Joaquin Miller Subject: Ballot 16 X-Change Technologies votes yes on all issues in Ballot 16, except: No on issue 7407. We would change our vote to yes if at least this one wrong use of 'typically' was simply deleted as proposed. PGP Fingerprint: CA23 6BCA ACAB 6006 E3C3 0E79 2122 94B4 E5FD 42C3 To: Joaquin Miller Cc: UML Superstructure FTF Subject: Re: Ballot 16 X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Fri, 25 Jun 2004 19:23:36 -0400 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 6.0.2CF2|July 23, 2003) at 06/25/2004 19:23:38, Serialize complete at 06/25/2004 19:23:38 My apologies, Joaquin, regarding issue 7407: I had not understood that you were asking for at least a minimal concession. I would have really been happy to accomodate. OTOH, this way the issue lives and should be addressed more broadly by an RTF. Regards, Bran Joaquin Miller 06/25/2004 05:37 PM Please respond to Joaquin Miller To UML Superstructure FTF cc Subject Ballot 16 X-Change Technologies votes yes on all issues in Ballot 16, except: No on issue 7407. We would change our vote to yes if at least this one wrong use of 'typically' was simply deleted as proposed. PGP Fingerprint: CA23 6BCA ACAB 6006 E3C3 0E79 2122 94B4 E5FD 42C3 :wq