I think the solution should not be to remove DataEvent and ErrorEvent from the status diagram. Both events are necessary to signal availability of data or reader problems to the application.
Instead, the text in chapter 37.5 after Input should be changed as follows:

Remove the first sentence "The application must invoke the readData method in order to request data from the smart card."

To make it more clear, the arrows marked with "DataEvent()" and "readData(action, count, data)" should be exchanged.

UPOS version 1.16.1 seems to add and extend UPOS 1.15, not 1.16. UPOS 1.16 does not exist.
However, should I be wrong and UPOS version 1.16 does exist, the specification is not on your web site (History consists of specifications UPOS 1.15 and UPOS 1.16.1 only).
In addition, in both 1.16.1 specifications (normative and informative document), no bookmarks are present, making it hard to work with both of them.

We have found an item in UPOS 1.16 (dtc-20-12-01.docx) that needs to be modified as a specification.
All of these items are extracted, issues and correction items are clearly shown, and the corrections and edits of the specification items are proposed as UPOS 1.16.1.
Attached documents are as follows.
1) UPOS RCSD 1.16 Issues Table
Note :All of the to be corrected items in the UPOS 1.16 spec. is listed up.
2) UPOS RCSD 1.16.1_withBar.docx
Note: All of the issues to be corrected is listed and indicated line by line with the explanation.
3) UPOS RCSD 1.16.1_clean.docx
Note: Clean file of UPOS RCSD 1.16.1
These documents have only RCSD related 11 device chapters.
That is to say;
Chapter 21 Lights
Chapter 29 POS Power
Chapter 39 Video Capture
Chapter 40 Individual Recognition
Chapter 41 Sound Recorder
Chapter 42 Voice Recognition
Chapter 43 Sound Player
Chapter 44 Speech Synthesis
Chapter 45 Gesture Control
Chapter 46 Device Monitor
Chapter 47 Graphic Display

All of UPOS1.16.1 issue resolved documents

After discussion with Denis and OMG Retail DTF member, finally we reached to the all issues resolved version.
As the final submission version documents are listed below.
1. Original UPOS 1.16
dtc-20-12-01.docx
2. UPOS1.16 Issue and Resolved Item Listed Table
UPOS RCSD 1.16 Issues Table_02032022.xlsx
3. UPOS1.16.1 with Bar + Issue Item and revised item Table
UPOS RCSD 1.16.1_02032022_withBar.docx
4. UPOS1.16.1 clean Version (UPOS1.16.1 Final Version Candidate)
UPOS RCSD 1.16.1_02032022_clean.docx

Please take look at those, and after your review, I would like to go to the voting for your approval.

Regards.

Tad Furuhata

Video Capture ER_CONTINUEINPUT should be ER_RETRY, "input" should be "data"

Examples:

Error Event behavior was incorrect.

ER_CONTINUEINPUT was incorrect and should be changed to
ER_RETRY

clearInput method description of "input" should be changed to "data".

ErrorEvent description of "input" should be changed to "data".

-------------

Issue Group D

Remarks in bar doc:

P89
P90
P91

Video Capture ER_CONTINUEINPUT to ER_RETRY, and "input" to "data"

See attached spreadsheet for extent of modifications.

Video Capture ER_CONTINUEINPUT should be ER_RETRY, "input" should be "data"

Missing remarks, repairing typos and descriptions. Retry behavior improperly documented for input vs output device behavior.

Examples:

Capability needs to be used under the read-only, however description was read-write. This should be corrected.

In addition, regarding the Remarks section, description was not good enough to explain this property’s behavior.

In the Remarks initialization description was missing.

In the See also section, referenced properties were missing.

In Attribute, regarding the ErrorResponse value, ER_RETRY should be eliminated, since this is the input device.
Also, in the ER_CLEAR output device related description was corrected since there are typo of loci and there is not output data because of input device.

In See Also section, Status, Error code, State model description were not needed.
Then “Device Input Model” on page Intro-22” and “Error Handling” on page Intro-23 were added instead.

-------------

Issue Group B

Remarks in bar doc:

P84
P85
P89
P90
P90
P90
P91
P93
P96
P97
P102
P106
P107
P108
P113
P128
P129
P138
P143
P146
P164
P174
P174
P178
P196
P205
P218
P232
P240
P241
P241
P246
P247
P252
P252
P254

Added missing remarks, improved status descriptions, repaired capability read-write vs read-only and ErrorResponse improvements for UPOS1161-4

See attached spreadsheet for extent of modifications.

Example:

39/ Video Capture

CapAssociatedHardTotalsDevice Property

Capability needs to be used under the read-only, however description was read-write. Therefore, it was changed from read-write to read-writeonly.
In addition, regarding the Remarks section, description was not good enough to explain this property’s behavior.
Therefore, “Holds the open name of the associated Hard Totals device, if the device is able to write to such devices which is the case, if CapStorage is either VCAP_CST_ALL or VCAP_CST_HARDTOTALS_ONLY.
If CapStorage is VCAP_CST_HOST_ONLY this property value must be the empty string. “was corrected as follows.
“Indicate that the device is able to store the recorded data into the Associated Hard Totals device and Hholds the its open name of the associated Hard Totals Device, if the device is able to write to such devices which is the case, if CapStorage is either VCAP_CST_ALL or VCAP_CST_HARDTOTALS_ONLY.
If CapStorage is VCAP_CST_HOST_ONLY, the device is not able to store the data into the Associated Hard Totals device and this property value must be the empty string. This property is initialized by the open method.

Repairing documentation to match expected implementation.

Examples:

This method can be used after open claim enable, however summary section missing the claim and it was added in the use after section.

This property is able to read and write. In that case there should be the E_ILLEGAL error code. However, that description was missing. Therefore, E_ILLEGAL related description was added as listed below.
Some possible values of the exception’s ErrorCode property are:
Value Meaning
E_ILLEGAL An invalid value was specified.

--------------

Issue Group A

Remarks in bar doc:

P38
P52
P67
P68
P74
P85
P92
P93
P99
P100
P101
P102
P103
P104
P105
P106
P107
P116
P126
P133
P139
P140
P141
P149
P168
P175
P181
P199
P221
P235
P236
P247

Property and method descriptions adjusted for UPOS1161-3

See attached spreadsheet for proposed modifications.

Example:

39/ Video Capture

VideoFrameRate Property

This property needs to be used under the open, claim enable, however is the spec claim, enable were missing and newly added.
Access after open, claim enable.
In the See also section, CapVideoFrameRate Property was missing, therefore it was added.

StatusUpdateEvent values and description in Remarks need improvement

Examples:

39/ Video Capture

TakePhoto

In the Remarks, StatusUpdateEvent related description was not good enough. Therefore, those description was added.
“The process of recorded data storing is performed asynchronously. StatusUpdateEvents are invoked for delivered to the application when the start and the end state were changed.”

-------------

Issue Group H

Remarks in bar doc:

P89
P90
P109
P110
P111
P114

Improved StatusUpdateEvent values and description in Remarks

Method descriptions, remarks and specific instances of StatusUpdateEvent needed improvement.

Read-only properties mistakenly marked read-write, and missing Remarks

Examples:

43/ Sound Player

CapAssociatedHardTotalsDevice Property

This property can be used as read only, therefore, read-write was corrected as read-only.
In the Remarks initialization description was missing.
Therefore, this description was added.
This property is initialized by the open method.

-------------

Issue Group G

Remarks in bar doc:

P168
P173
P188
P243

Fixed read-only property designations and added missing remarks for UPOS1161-9

Some properties were mistakenly described as read-write when they should be read-only. Also clarified descriptions.

Cover page version and submission date

Examples:

In the cover page there was an old description. This specification proposing the UPOS 1.16.1 and it editing the UPOS1.16. Also, documentation submission date is Sept. 2021.

-------------

Issue Group C

Remarks in bar doc:

P14

Cover page and submission date adjusted for UPOS1161-5

In the cover page there was an old description. This specification was intended to be UPOS 1.16.1 as an adjustment to UPOS1.16. Also, documentation submission date was Sept. 2021.

Method behavior descriptions missing several conditions

Examples:

47/ Graphic Display...

clearInput Method, clearInputProperties Method, clearOutput Method

This method behavior description missing the several conditions. Therefore, those are newly added.

void:

-------------

Issue Group F

Remarks in bar doc:

P116
P132
P133
P149
P168
P181
P182
P199
P221
P235
P236

Added missing method conditions for UPOS1161-8

See attached spreadsheet for extent of modifications.

Example:

42/ Voice Recognition
ClearInput Method,
ClearInputProperties Method

Added: void:

Method use descriptions accidentally comma delimited, not consistent with others

Examples:

POS Power restartPOS and shutdownPOS methods...

Therefore, use after open,
enable is changed to use after open-enable.

-------------

Issue Group E

Remarks in bar doc:

P77
P78
P90
P91
P194

Repaired "method use" descriptions for UPOS1161-7

See attached spreadsheet for extent of modifications.

Some "method use" descriptions needed clarification and repair of dashed-terminology that was comma-delimited.