UPOS 1.16.1 RTF Avatar
  1. OMG Issue

UPOS1161 — Missing remarks, status description improvement, capability read-write vs read-only and ErrorResponse improvements

  • Key: UPOS1161-4
  • Status: closed  
  • Source: Lexmark ( Mr. Andy Mattice)
  • Summary:

    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

  • Reported: UPOS 1.16b2 — Wed, 23 Mar 2022 03:16 GMT
  • Disposition: Resolved — UPOS 1.16.1
  • Disposition Summary:

    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.

  • Updated: Wed, 13 Jul 2022 14:18 GMT
  • Attachments: