The description for ER_CLEAR is wrong: Replace
Clear all buffered output data including all asynchronous output. (The effect is the same as calling clearInput.)
with
Clear all buffered output data including all asynchronous output when locus is EL_OUTPUT and all buffered input data when locus is EL_INPUT. (The effect is the same as calling clearInput when locus is EL_INPUT or clearOutput when locus is EL_OUTPUT.)

The bookmarks on the summary pages of many devices are broken, and there are many meaningless bookmarks.

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

Improvement advice
A value that classifies the service function added in version 1.16 has not been added.

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

EVRW is not described in UPOS 1.16 RCSD specification, therefore this issue and correction should be done in UPOS 1.15 whole specification.
Therefore as UPOS 1.16 RCSD this should be closes as out of scope.

UPOS 1.16 RCSD proposed 9 new devices but compare to the current UPOS specifiation it nees the more detailed device behavir explanation compare to the current UPOS1.15 specfication.

*All of required correction and editing was completed. *

Based on the suggestion and discussion about the UPOS 1.16 RCSD specification, issue editing and to make the document history to identify all of the changes from current one to new one was completed.
Also, regarding the class diagram changing history was included.
Please refer to the attached revised with history type UPOS 1.16 RCSD specification.

In each of the following, the start position of the line that separates the item names in the table and the explanation of the values is at the left end of the page.

14-15 CapDailyLog Property
14-60 PaymentCondition Property
14-68 PaymentMedia Property
14-73 TransactionType Property
14-76, 14-77 accessDailyLog Method
14-83 -> 14-88 authorizeCompletion Method to authorizeVoidPreSales Method
14-92 cashDeposit Method
14-93 checkCard Method

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

Although updated information is not described, Update in Release 1.15 is added below.
15-10 General Information
15-48 CountryCode Property
because added Germany

15-50 DateType Property
because added TICKET_START, TICKET_END

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

It is described as Added in Release 1.9, but it is correctly Added in Release 1.15.

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

Descriptions of Value and Meaning of BONUS_COMBINATION_X are not separated and appear to be connected.

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

The indent position / bold of the item name has been moved to the text part.

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

It is described as 1.15, but it is correctly 1.14.

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

It is described as boolean, but it is correctly int32.

This is not a UPOS 1.16 RCSD Issue and should be transferred to UPOS 1.15 FTF

This is not included in the UPOS 1.16 RCSD specification.
Therefore, as UPOS 1.16 RCSD specification does not include this.
And this should be closes as out of scope.

UPOS 1.16 RCSD Final Candidate specification documents are availablle now as listed in this document.
We got many points to be corrected from the Retail DTF members during the UPOS 1.16 FTF process and discussion.
Now, all of issues and solutions are listed in the attached spread sheet.
Finally, all of UPOS 1.16 RCSD specifition editing and corrections are completed.
Please refer to the attached files and would like to ask voting to close this FTF.

Here is the document names and purpose of each document.
1. UPOS 1.16 Issues and Solution Table_05152020.xlsx
=> List of all issues and its solutions
2. retail-19-07-04_Original.docx
=> UPOS1.16 RCSD specification original document as 1.16 beta2
3. retail-19-07-04_Revised_05152020_Clean.docx
=> UPOS 1,16 RCSD completed specification clean version
4. retail-19-07-04-Revised_05152020_withBar.docx
=> UPOS 1.16 RCSD completed specificaion with bar version
5. UPOS 1.16 RCSD XML Files 05142020.zip
=> UPOS 1.16 RCSD Class diagram xmi files

// end

*All of required correction and editing was completed. *

All of issues are resolved by the proposal for UPOS116-1.
Therefore this issue is also resolved.

Some issues are corrected from dtc-18-12-20 to smsc-20-02.01.
However still several issues are remaining.

1) 15.2 Summary CapDailyLogType was incorrect
2) 15.6.6 TransitionEvent TransitionEvent Updated timing is incorrect
3) 14.4.48 DailyLog Property In this section See also description format is incorrect.
4) 14.4.55 PaymentCondition Property This section's description format is incorrect.
5) 15.4.56 PaymentDetail Property This property's updated timing is incorrect.
6) 16.3 General Information German Fiscal Information was missing.
7) Each section's Format is not good shape
Added or Updated line description should be in 1 line not 2 lines.
Need to add the ruled line in the parameter, value and meaning section.

*All of required correction and editing was completed. *

All of issues are resolved by the proposal of UPOS116-1.
Therefore, this issue is also resolved.