Issue 13218: Typos in the Ruby CORBA Langaugae Mapping spec (rclm-ftf) Source: Remedy IT (Mr. Johnny Willemsen, jwillemsen(at)remedy.nl) Nature: Revision Severity: Minor Summary: We want to report the following small changes to the Beta 1 spec: Page 13 corrected font of section “Normative References” Page 13 updated CORBA v3.0.3 to v3.1 in section 1.1 and 3 Page 18 7.4.1 corrected mechamism to mechanism Page 12 7.12 changed typechecking into “type checking” Page:22 7.11 Mapping for Wide string types: change first phrase to "The OMG IDL Wide string type" 7.12.2 Change last sentence 'if the Any contained a specific' should be 'if the Any contains a specific' Page:27 7.20 para 4: change "a accessor" to "an accessor" 7.20 updated reference to CORBA v3.1 Page 29 Removed a few empty lines 7.23 : '_get_ ‘firstname, as defined' should be '_get_firstname, as defined' Page 31 7.25.1 Changed toplevel to “top level” Page 31 Removed reference to Test.idl and TestS.rb, that only makes the example unclear Page 32 Changed accomodate to accommodate Page 34 7.25.2, changed “Ofcourse” to “Of course” and “coulde” to “could” Change 'The implementation method result depends then on the number of result values:' to 'The implementation method result depends on the number of result values as follows:' Check heading of table 7.3 Resolution: Agreed to make the following revisions to the document Revised Text: Update on page 13 the font of section “Normative References” On page 13, section 1.1 and 3, Update 3.0.3 to 3.1 and formal/04-03-12 to formal/2008-01-04 On Page 18 7.4.1 corrected mechamism to mechanism On Page:22 7.11 Mapping for Wide string types: change first phrase to "The OMG IDL wide string type", the wide was lacking On Page 12 7.12 changed typechecking into “type checking” In 7.18.2 Change last sentence to 'Object references mapped from Any values will also be automatically narrowed if the Any contains a specific interface type.' On Page:27 7.20 para 4: change "a accessor" to "an accessor" In 7.20 Update chapter 4.11 to chapter 8.11, removed “(OMGspec formal/04-03-12)” On Page 29 Removed a few empty lines In 7.23 : '_get_ ‘firstname, as defined' should be '_get_firstname, as defined' On Page 31 7.25.1 Changed toplevel to “top level” On Page 31 Removed all lines that mention Test.idl or TestS.rb On Page 32 Change accomodate to accommodate On Page 34 7.25.2, changed “Ofcourse” to “Of course” and “coulde” to “could” On Page 34 7.25.2, Change 'The implementation method result depends then on the number of result values:' to 'The implementation method result depends on the number of result values as follows:' * Change the heading of table 7.3 to"Ruby reserved member names Actions taken: January 8, 2009: received issue October 15, 2009: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 08 Jan 2009 16:02:54 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Johnny Willemsen Company: Remedy IT mailFrom: jwillemsen@remedy.nl Notification: Yes Specification: RCLM Section: - FormalNumber: 09-01-01 Version: Beta 1 RevisionDate: jan 2009 Page: - Nature: Revision Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729) Description We want to report the following small changes to the Beta 1 spec: Page 13 corrected font of section .Normative References. Page 13 updated CORBA v3.0.3 to v3.1 in section 1.1 and 3 Page 18 7.4.1 corrected mechamism to mechanism Page 12 7.12 changed typechecking into .type checking. Page:22 7.11 Mapping for Wide string types: change first phrase to "The OMG IDL Wide string type" 7.12.2 Change last sentence 'if the Any contained a specific' should be 'if the Any contains a specific' Page:27 7.20 para 4: change "a accessor" to "an accessor" 7.20 updated reference to CORBA v3.1 Page 29 Removed a few empty lines 7.23 : '_get_ .firstname, as defined' should be '_get_firstname, as defined' Page 31 7.25.1 Changed toplevel to .top level. Page 31 Removed reference to Test.idl and TestS.rb, that only makes the example unclear Page 32 Changed accomodate to accommodate Page 34 7.25.2, changed .Ofcourse. to .Of course. and .coulde. to .could. Change 'The implementation method result depends then on the number of result values:' to 'The implementation method result depends on the number of result values as follows:' Check heading of table 7.3 Cc: rclm-ftf@omg.org From: Victor Giddings To: Subject: Re: Vote poll 1 Date: Thu, 26 Mar 2009 10:43:25 -0400 X-Mailer: Apple Mail (2.930.3) Objective Interface votes as follows: Issue 13218: NO The following are problems in the "revised convenience document" that, if addressed, would allow me to change my vote to yes: - section 7.20 (page 16): suggest removing the document number from 2nd paragraph. Since it is in the normative references, that can serve as the source of document number, and any future updates will be restricted to one place. - at bottom of page 18, there still appears to be an extra space in _get_ firstname - page 21: the resolution of "On Page 34 7.25.2, Change 'The implementation method result depends then on the number of result values:' to 'The implementation method result depends on the number of result values as follows:'" has not been applied. Also, I wanted to open a discussion of the following: In other specifications, we have insisted that the revised specification have "traceability comments" inserted that refer to the issues that caused the change. Since we have only one issue and all of the items are typos, I don't see this is as critical to this effort. However, finding the changes was made harder by not having these notations. Finally, I've filed this as a new issue: In the default implementation in section 7.25.2, class "PortableServer::DynamicImplementation", this is "&&" which should be "&&". Regards, Vic Victor Giddings victor_giddings@omg.org On Mar 20, 2009, at 8:13 AM, Johnny Willemsen wrote: Hi, Let us redo this in the correct way. Attached the updated document. Can I have a vote on this document? Johnny I think this proposed change is good enough to vote on: However minor edits" enter "agreed to make the following revisions to the document" in the Resolution section of the issue documentation. Also change "format" to "formal" in the second revision. With these two changes I vote "yes" on poll 1 for this ftf. Tom Rutt Johnny -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133 <08-08-02-Ruby.odt>