2.1 Generic process overview - use of "shall"

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: UBL Naming and Design Rules Version 3.0
    • Component/s: Public reviews
    • None
    • Environment:

      Normative

    • Hide

      Edit to say the requirement once and only once. A documented process isn't the same thing as a process.

      Show
      Edit to say the requirement once and only once. A documented process isn't the same thing as a process.

      2.1 Generic process overview reads in part:

      *****
      There shall be a process by which CCTS information regarding the information bundles is managed.
      *****

      Since the draft disclaims use of UPPERCASE for keywords, what is the nature of the "shall," in this sentence? It is followed by a range of options for "process" but doesn't give the appearance of being an enforceable requirement. Yes?

      Ah, I read just a bit further and saw the requirement of a "documented process." But that isn't what the original sentence says.

      Suggest saying the requirement once and only once, without repetition.

            Assignee:
            Unassigned
            Reporter:
            Patrick Durusau
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: