1866 Change of description text "float" to "floating point"
- Created
- 21 Mar 2023
- Status
- In Force (Editorial)Closed: the editorial correction is part of the standard. No further comments are taken. Show the workflow
- Batch
- 57/2673/INFThis tissue went out with this batch, which was closed on 01 Apr 2024.
- Part
- Part 7-4 (2020; Edition 2.1)
- Links
- None
- Page
- 133 of INF
- Clause
- 6.3.9
- Paragraph
- Table 51
Issue
For the DO 'ApcFTrk' the explanation text uses the term "float" which is not quite clear.
Proposal
Modify the explanation text from "float" to "floating point".
Modify the description text of Table 209 accordingly.
Modify the description of abbreviation 'F' in Table 1 accordingly.
Consider whether to also modify the description in Part 7-3 clause 4 item "f" (no dedicated Tissue created for this)
| Discussion | Created |
|---|---|
| In Force (Editorial) Batch '57/2673/INF' (2) closed | 01 Apr 24 |
| Editorial Accepted Editorial | 12 Dec 23 |
| Approval (Editorial) As the tissue is proposed to be editorial and nobody rejects, the tissue state is changed to Approval(Editorial). | 05 May 23 |
|
Discussion (red)
I would accept that proposal to use the naming convention from part 7-3.
Description would be: Control service tracking for controllable analogue setpoint data with analogue float value control. Abbreviation would be: F - Float, floating point value The character of the tissue is editorial, not interop, because it improves the wording. Semantic was clear all the time. |
23 Mar 23 |
|
Accepted
Note that 7-3 - Clause 6.11.4 - defines "Analogue float value control (AnalogueValueCtlF)".
Therefore, an editorial change in 7-4 could be to use the 7-3 naming convention. Control service tracking for controllable analogue setpoint data with analogue float value control - see 7-3. Note that the type is unambiguously given in the LTRK specification: CTS(AnalogueValueCtlF) |
23 Mar 23 |
|
Accepted
I would state in table 1 for the abbreviation F float and floating point. Both descriptions of F will be valid.
The change in table 51 is valuable to improve description of ApcFTrk. |
22 Mar 23 |
| Accepted Open for discussion | 21 Mar 23 |