Issue 10535: Typographical Errors (rtc-ftf) Source: Hitachi (Dr. Saku Egawa, saku.egawa.qm@hitachi.com) Nature: Uncategorized Issue Severity: Summary: I will report several minor problems that seems not worth registering as separate issues. Typographical errors 6.1 Requirements [[BR]] Systematic execution: The execution ordering of modules within an **R** application ... 7.2.2.3 !LifeCycle [[BR]] At any other time, it shall not be required to **performs** any ongoing activity of its own; ... Wording inconsistency 7.3 Execution sementics [[BR]] ... stimulus response processing (also known as discrete events), ... 7.3.2 Stimulus Response Processing [[BR]] The stimulus response design pattern is also referred to as asynchronous event processing. Discussion We should collect all such errors we find in this issue and vote on them together at the very end so that we don't end up with many issues that are so trivial. -- RickWarren, 2006/12/13 Resolution: See the corrections noted below. Revised Text: Correct the following typographical errors: · Section 6.1, Requirements: Remove the extraneous letter 'R' from the sentence "Systematic execution: The execution ordering of modules within an R application…." · Section 7.2.2.2, LightweightRTObject, in the sentence "At any other time, it shall not be required to performs any ongoing activity…" under the subheading "Execution Context," the verb tense is incorrect. "Performs" should be "perform." · In sections 8.3.1.3, Mapping for String Types, and 8.3.1.4, Mapping for Wide String Types, "namespace CORBA" should be "namespace RTC." · In Figure 7.4, Lightweight RTC Lifecycle, there is an incorrect closing square bracket : Inactive[n[. Correct it. · In section 7.2.2, Components, "lightweight robot technology component" should be replaced with "lightweight robotic technology component". · In section 7.2.2.1, lightweightRTComponent, "UML2.0::Components::BasicComponents::Component" should be replaced with "UML::Components::BasicComponents::Component". · In the operation table in section 7.2.2.2, LightweightRTObject, replace "exec_context" with "context" in the argument. · In the operation tables in section 7.2.2.5, ComponentAction, in section 7.3.1.2, DataFlowComponentAction, in section 7.3.2.4, FsmParticipabtAction, and in section 7.3.3.4, MultiModeComponentAction, replace "context" with "exec_handle" in the argument. · In section 7.2.2.6.7. remove_component, Semantics subsection, "The newly added RTC will receive …" should be replaced with "The removed RTC will receive…" · In section 7.3.3.4.1, on_mode_changed, Semantics subsection, remove the extraneous lettes "(context" from the sentence "The new mode can be retrieved with get_current_mode_in_context(context." . · In section 7.4.2.3, PortService, "UML2.0::CompositeStructures::Ports::Port" should be replaced with "UML::CompositeStructures::Ports::Port". · In RTC.idl and in Annex A, add the argument "in ExecutionContext exec_context" to "is_alive" operation in LightweightRTObject interface. · In RTC.idl and in Annex A, replace "exec_context" with "exec_handle" in the arguments of ComponentAction interface, DataFlowComponentAction interface and FsmParticipantAction interface. · In RTC.idl and in Annex A, replace "component" with "comp" in the arguments of ExecutionContext interface. · In the operation table in section 7.2.2.6 ExecutionContext, replace "comp" with "component" in the arguments of ExecutionContext interface. · In RTC.idl and Annex A, replace "OK" and "ERROR" with "RTC_OK" and "RTC_ERROR", and add the following sentence as third sentence in section 8.2.2 Return Codes. However, in an annex and RTC.idl, since a word confliction is expected in mapping to other languages, "OK" and "ERROR" are replaced to "RTC_OK" and "RTC_ERROR". Correct the following wording inconsistency: · The first paragraph in section 7.3, Execution Semantics, contains the text "…stimulus response processing (also known as discrete events)…." The emphasized text should read "asynchronous or discrete event processing" for consistency with other portions of the specifications. · The first sentence of section 7.3.2, Stimulus Response Processing, says "The stimulus response design pattern is also referred to as asynchronous event processing." For consistency, this sentence should be replaced with: "The stimulus response design pattern is also referred to as asynchronous or discrete event processing." · All the words "PRECONDITION_NOT_MET" and "BAD_PARAMETER" should be replaced with "ReturnCode_t::PRECONDITION_NOT_MET" and "ReturnCode_t::BAD_PARAMETER". Actions taken: December 21, 2006: received isuse January 15, 2008: closed issue Discussion: End of Annotations:===== MG issue 10535: Typographical Errors Source: Hitachi (Saku Egawa, saku.egawa.qm@hitachi.com) Severity: Support Text Disposition: New Summary I will report several minor problems that seems not worth registering as separate issues. Typographical errors 6.1 Requirements Systematic execution: The execution ordering of modules within an **R** application ... 7.2.2.3 LifeCycle At any other time, it shall not be required to **performs** any ongoing activity of its own; ... Wording inconsistency 7.3 Execution sementics ... stimulus response processing (also known as discrete events), ... 7.3.2 Stimulus Response Processing The stimulus response design pattern is also referred to as asynchronous event processing. Discussion We should collect all such errors we find in this issue and vote on them together at the very end so that we don't end up with many issues that are so trivial. -- RickWarren, 2006/12/13 Proposed Resolution Revised Text