Issue 10973: PLM 2 FTF -- Editorial issues (plm2-ftf) Source: Object Management Group (Mr. Andrew Watson, andrew@omg.org) Nature: Uncategorized Issue Severity: Summary: E1. Section "0.5 Proof of Concept" If this section gets transferred to the Final Adopted Specification, please fix the following: E1.1 Every instance of "it's" (with an apostrophe) should be "its" (no apostrophe). 3 instances. E1.2 "... evaluated in a interaction scenario ..." should be "... evaluated in an interaction scenario ..." E2. Section "0.8 Edit Directions Against PLM Services V1.0 (dtc/2005-03-08)" As we discussed at the AB meeting, this title should be "Changes from PLM Services V1.0 (dtc/2005-03-08)" (or some similar language). E3. Section "3 Normative References" The document number for Meta Object Facility (MOF) 2.0 XMI Mapping Specification contains a typo - "OMG Document formal.-5-09-01" should be "OMG Document formal/05-09-01". E4. Section "7.2.5.3 Partner role descriptions" The table contains a superfluous hyphen in "person" in one role description "per-son". E5. Section "7.2.11.3 Process definition" Contains mis-hyphenation of "example" ("ex-ample"). E6. Figures 7-11, 7-12, 7-13, 7-14 garbled in the PDF (But I believe this was fixed in the errata during the meeting). E7. Section "7.2.2 UML package" The phrase "XML provides an own mechanism ..." should be "XML provides its own mechanism ..." E8. Section "7.2 UML profile for XML Schema (Informative)" The phrase "An UML profile ..." occurs 5 times on pages 371, 376 & 378. Should be "a UML profile". E9. Section "7.2 UML profile for XML Schema (Informative)" The phrase "... stereotypes, tagged value called properties ...." should be "... stereotypes, tagged values called properties ....". Resolution: Revised Text: Actions taken: April 25, 2007: received issue Discussion: End of Annotations:===== s is issue # 10973 From: Andrew Watson PLM 2 FTF -- Editorial issues E1. Section "0.5 Proof of Concept" If this section gets transferred to the Final Adopted Specification, please fix the following: E1.1 Every instance of "it's" (with an apostrophe) should be "its" (no apostrophe). 3 instances. E1.2 "... evaluated in a interaction scenario ..." should be "... evaluated in an interaction scenario ..." E2. Section "0.8 Edit Directions Against PLM Services V1.0 (dtc/2005-03-08)" As we discussed at the AB meeting, this title should be "Changes from PLM Services V1.0 (dtc/2005-03-08)" (or some similar language). E3. Section "3 Normative References" The document number for Meta Object Facility (MOF) 2.0 XMI Mapping Specification contains a typo - "OMG Document formal.-5-09-01" should be "OMG Document formal/05-09-01". E4. Section "7.2.5.3 Partner role descriptions" The table contains a superfluous hyphen in "person" in one role description "per-son". E5. Section "7.2.11.3 Process definition" Contains mis-hyphenation of "example" ("ex-ample"). E6. Figures 7-11, 7-12, 7-13, 7-14 garbled in the PDF (But I believe this was fixed in the errata during the meeting). E7. Section "7.2.2 UML package" The phrase "XML provides an own mechanism ..." should be "XML provides its own mechanism ..." E8. Section "7.2 UML profile for XML Schema (Informative)" The phrase "An UML profile ..." occurs 5 times on pages 371, 376 & 378. Should be "a UML profile". E9. Section "7.2 UML profile for XML Schema (Informative)" The phrase "... stereotypes, tagged value called properties ...." should be "... stereotypes, tagged values called properties ....".