Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25494

Make SN.2 conditional on SN.1

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • V2.x Message Specification (V2)
    • V2.9.1
    • Infrastructure & Messaging
    • STRUCTURED NUMERIC (SN)
    • Data Types (Chapter 2A)
    • 2A.2.71.2
    • Hide

      Regardless of whether SN.4 (Num2) is populated, SN.2 is also conditionally required if the SN.1 (Comparator) component is populated: Update conditionality predicate for SN.2

      Show
      Regardless of whether SN.4 (Num2) is populated, SN.2 is also conditionally required if the SN.1 (Comparator) component is populated: Update conditionality predicate for SN.2
    • Nick Radov / Michelle Barry : 2-0-0
    • Correction
    • Non-substantive
    • V2.9.1

    Description

      We had already agreed to change the optionality for the SN.2 (Num1) component from "O" (optional) to "C" (conditional) as part of V2-25190, however that issue missed part of the predicate. Regardless of whether SN.4 (Num2) is populated, SN.2 is also conditionally required if the SN.1 (Comparator) component is populated. A comparator only makes sense in the context of a specific number; there is no valid use case for having a comparator without at least one number.

      Attachments

        Activity

          People

            Unassigned Unassigned
            nradov Nick Radov
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: