Issue 11404: AMS_Property template (amsm-ftf) Source: Selex ES (Mr. Fabrizio Morciano, fmorciano(at)selex-si.com) Nature: Revision Severity: Significant Summary: In the spec the AMS_Property template have been used several times; it has been used in the PIM for instance as: AMS_Property<AMS_StdState,ST_NOSTD> or AMS_Property<AMS_StdMechanism,MS_NONSTD>. Now, it could be useful to always use the same convention to define the names of such “non stardard” enumeration values (such as ST_NOSTD or MS_NONSTD) since sometimes in the document it is used ST_NONSTD instead of ST_NOSTD, or MS_NOSTD instead of MSNONSTD and so on…In this way it would be easier to catch these little inconsistencies. For instance in the diagram 7.16 it is used MS_NONSTD instead of MS_NOSTD... but it is just an example since this kind of error can be found in various parts of the document. Resolution: Generalize the use of *_NONSTD Revised Text: Search and replace HU_NOSTD with HU_NONSTD Search and replace HU_NON_STD with HU_NONSTD Search and replace ST_NOSTD with ST_NONSTD Search and replace MS_NOSTD with MS_NONSTD Replace Figure 7.7 on page 37 with the following figure: Replace Figure 7.20 on page 97 with the following figure: Disposition: Resolved Actions taken: September 14, 2007: received issue July 18, 2008: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 14 Sep 2007 04:52:28 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Fabrizio Company: Morciano mailFrom: fmorciano@selex-si.com Notification: Yes Specification: AMSM Section: General FormalNumber: dtc/07-05-02 Version: Beta 1 RevisionDate: 07-05-02 Page: 32 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Description In the spec the AMS_Property template have been used several times; it has been used in the PIM for instance as: AMS_Property or AMS_Property. Now, it could be useful to always use the same convention to define the names of such .non stardard. enumeration values (such as ST_NOSTD or MS_NONSTD) since sometimes in the document it is used ST_NONSTD instead of ST_NOSTD, or MS_NOSTD instead of MSNONSTD and so on.In this way it would be easier to catch these little inconsistencies. For instance in the diagram 7.16 it is used MS_NONSTD instead of MS_NOSTD... but it is just an example since this kind of error can be found in various parts of the document.