Table A5-22 12 JC Comment: R, E [CSG Webex 14 March]: Agreed Closed – DM167 reponse and alert attirbutes are with the suggested change. missing. [OPLINKP WG/WHL/4 22 – Suggested Change: March]: Agreed. Add attributes for DM167., and M” “M” Table A5-22 26 TL Need to make sure intent matched E Agreed to be Closed Comment: [Editors 21 March]: – DM113R intent from SPR (also noted above from CSG, done. comment 10) [OPLINKP WG/WHL/4 22 – Suggested Change: Currently March]: Agreed. of the requested Should be “Notification revised to: of the speed defined by the “Notification specified speed types is the specified speed.” A5-22 53 AW DM78R (distance) FROM (positionR) It refers to 1. 1- [Editors 21 March]: 1 – – comment 41. No (to/from) variable. Closed The same comment to that made in Comment 12 regarding the (to/from) variable 1 - [OPLINKP WG/WHL/4 22 – March]: Implement a variable. “to/from” See also comment 29. should be used “To” 2. 165 when the ground ATC wants to refer to a The variable (traffic type and or location) does downstream waypoint in the route (e.g. not support options such as “crossing”, aircraft will report the flying distance up to direction” etc “opposite this waypoint in the FMS flight plan). should be used in any other case, “From” including to request distance from a 3. DM167 WE WILL MAINTAIN (level waypoint that is not part of the Flight Plan. single)AT TIME (time) Minor typo add <space> between and 2- [Editors 21 March]: Neither in – “)” – GOLD the initial definition of “AT” TrafficTypeLocation paramater contained this information. CSG
Table A5-22 12 JC Comment: DM167 reponse and alert attirbutes are missing. Suggested Change: Add attributes for DM167., “M” and M” R, E [CSG Webex – 14 March]: Agreed with the suggested change. [OPLINKP WG/WHL/4 – 22 March]: Agreed. Closed Table A5-22 DM113R 26 TL Comment: Need to make sure intent matched intent from SPR (also noted above from CSG, comment 10) Suggested Change: Currently “Notification of the requested Should be revised to: “Notification of the speed defined by the specified speed types is the specified speed.” E [Editors – 21 March]: Agreed to be done. [OPLINKP WG/WHL/4 – 22 March]: Agreed. Closed A5-22 53 AW 1. DM78R (distance) FROM (positionR) The same comment to that made in Comment 12 regarding the (to/from) variable 2. 165 The variable (traffic type and or location) does not support options such as “crossing”, “opposite direction” etc 3. DM167 WE WILL MAINTAIN (level single)AT TIME (time) Minor typo – add <space> between “)” and “AT” 1- [Editors – 21 March]: It refers to comment 41. No (to/from) variable. 1 - [OPLINKP WG/WHL/4 – 22 March]: Implement a “to/from” variable. See also comment 29. “To” should be used when the ground ATC wants to refer to a downstream waypoint in the route (e.g. aircraft will report the flying distance up to this waypoint in the FMS flight plan). “From” should be used in any other case, including to request distance from a waypoint that is not part of the Flight Plan. 2- [Editors – 21 March]: Neither in GOLD the initial definition of TrafficTypeLocation paramater contained this information. CSG 1 – Closed
OPLINKPWGWHL-4-APR.docx