${taskforce.name} Avatar
  1. OMG Task Force

UnifiedPOS RCSD Version 1.16 FTF 2 — All Issues

Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
UPOS116_-37 Electronic Journal: Bad Description for Value ER_CLEAR UPOS 1.15 open
UPOS116_-11 Bookmarks of Summary pages are broken UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-3 Add EVRW_ST_CAT definition to ServiceType property UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-1 RCSD device description needs the more explanation about the device models and related properties methods events. UPOS 1.15 UPOS 1.16b2 Closed; No Change closed
UPOS116_-5 Table separation line layout UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-7 Version Information UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-9 Version information of PaymentDetail property UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-13 Description of the table of PaymentCondition property UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-15 Errors, See Also layout of DailyLog property UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-17 Version number for which TransisionEvent was specified UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-19 CapDailyLog type different UPOS 1.15b2 UPOS 1.16b2 Closed; Out Of Scope closed
UPOS116_-21 UPOS 1.16 RCSD all of issues are corrected and editing was completed UPOS 1.15 UPOS 1.16b2 Closed; No Change closed
UPOS116_-23 Several issues are pointed out for the UPOS1.16 FTF however they are for the UPOS1.15beta2 issues. UPOS 1.15 UPOS 1.16b2 Closed; No Change closed

Issues Descriptions

Electronic Journal: Bad Description for Value ER_CLEAR

  • Status: open  
  • Source: Free Software Developer ( Martin Conrad)
  • Summary:

    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.)

  • Reported: UPOS 1.15 — Thu, 16 Mar 2023 23:04 GMT
  • Updated: Wed, 22 Mar 2023 15:35 GMT

Bookmarks of Summary pages are broken

  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

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

  • Reported: UPOS 1.15b2 — Sat, 3 Aug 2019 06:07 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

Add EVRW_ST_CAT definition to ServiceType property

  • Key: UPOS116_-3
  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

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

  • Reported: UPOS 1.15b2 — Thu, 8 Aug 2019 09:58 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

RCSD device description needs the more explanation about the device models and related properties methods events.


Table separation line layout

  • Key: UPOS116_-5
  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

    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

  • Reported: UPOS 1.15b2 — Thu, 1 Aug 2019 12:17 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

Version Information

  • Key: UPOS116_-7
  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

    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

  • Reported: UPOS 1.15b2 — Thu, 1 Aug 2019 12:02 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

Version information of PaymentDetail property

  • Key: UPOS116_-9
  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

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

  • Reported: UPOS 1.15b2 — Thu, 1 Aug 2019 11:54 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

Description of the table of PaymentCondition property

  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

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

  • Reported: UPOS 1.15b2 — Thu, 1 Aug 2019 11:51 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

Errors, See Also layout of DailyLog property

  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

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

  • Reported: UPOS 1.15b2 — Thu, 1 Aug 2019 11:43 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

Version number for which TransisionEvent was specified

  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

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

  • Reported: UPOS 1.15b2 — Thu, 1 Aug 2019 11:36 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

CapDailyLog type different

  • Status: closed  
  • Source: Individual ( Kunio Fukuchi)
  • Summary:

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

  • Reported: UPOS 1.15b2 — Thu, 1 Aug 2019 11:31 GMT
  • Disposition: Closed; Out Of Scope — UPOS 1.16b2
  • Disposition Summary:

    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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT

UPOS 1.16 RCSD all of issues are corrected and editing was completed

  • Status: closed  
  • Source: Microsoft ( Mr. Tadashi Furuhata)
  • Summary:

    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

  • Reported: UPOS 1.15 — Fri, 15 May 2020 04:18 GMT
  • Disposition: Closed; No Change — UPOS 1.16b2
  • Disposition Summary:

    *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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT
  • Attachments:

Several issues are pointed out for the UPOS1.16 FTF however they are for the UPOS1.15beta2 issues.

  • Status: closed  
  • Source: Microsoft ( Mr. Tadashi Furuhata)
  • Summary:

    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.

  • Reported: UPOS 1.15 — Tue, 3 Mar 2020 06:35 GMT
  • Disposition: Closed; No Change — UPOS 1.16b2
  • Disposition Summary:

    *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.

  • Updated: Thu, 1 Apr 2021 20:58 GMT
  • Attachments: