• Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: 3.1.1
    • Component/s: edits
    • None
    • Environment:

      Conformance

    • Hide

      If you want to highlight "MUST" statements, to be consistent highlight this one. Personally I would take it as evidence that saying something once is hard enough.

      Show
      If you want to highlight "MUST" statements, to be consistent highlight this one. Personally I would take it as evidence that saying something once is hard enough.

      2.1.2 Flags reads in part:

      *****
      Where a bit is marked as "Reserved", it MUST be set as shown in the table and is reserved for future use.
      *****

      Which is not highlighted in yellow nor does it appear in Appendix A.

      One of the dangers of the appendix of "mandatory" statements is that it violates the DRY principle - Don't Repeat Yourself.

      That avoids the danger that you may drop (as here) or omit (as with the packet types) information that is needed for conformance.

            Assignee:
            Rahul Gupta (Inactive)
            Reporter:
            Patrick Durusau
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: