| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| UPOS1162-5 | RFC wrong number was used in VoiceRecognition and SpeechSynthesis devices. | UPOS 1.16.1 | open | |||
| UPOS1162-2 | See issue UPOS1151-11, SmartCardRW Status Diagram Confusing, readData Method Handling Unclear | UPOS 1.15 | open | |||
| UPOS1162-1 | Bad version number used in header | UPOS 1.16.1 | open |
In chapter 42 of VoiceRecognition's section 42.6.7 and in chapter 44 of SpeechSynthesis's section 44.4.7 had a incorrect RFC# 4664.
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.