Unclear conformance requirements in section 9.2.3 "Conformance issues"

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • PIM WD11, PIM WD12
    • Affects Version/s: PIM CSPRD02
    • Component/s: PIM
    • None
    • Environment:

      TAB Comments

    • Hide

      Consider placement and wording of Section 9.2.3 and entire Conformance section. Split section 9 into a Rules Section and a Conformance Section.

      Add note that these are requirements on conforming specifications, and that they indicate documentation as well as behavior requirements. Clarify 9.2.3 as documentation requirement on specifications claiming conformance.

      Clarify wording for elements of the referenced bullet list [PIM WD12]

      Reference: WSCALENDAR-521

      Show
      Consider placement and wording of Section 9.2.3 and entire Conformance section. Split section 9 into a Rules Section and a Conformance Section. Add note that these are requirements on conforming specifications, and that they indicate documentation as well as behavior requirements. Clarify 9.2.3 as documentation requirement on specifications claiming conformance. Clarify wording for elements of the referenced bullet list [PIM WD12] Reference: WSCALENDAR-521

      Unclear conformance requirements in section 9.2.3 "Conformance issues" [line 677]

      For "Precision" bullet point [line 682]: reads more like a recommendation that probably belongs best in the body of the specification ( also, missing question mark).

      For "Time Zones and UTC" [line 684] : it is unclear how these details "restrict the variability inherent in the expressions of Date and Time ": there are several "may" statements normative requirements, and one "cannot". It would be clearer if normative keywords were used (MAY, MAY NOT). Even so, such optional keywords are difficult to interpret in a conformance clause: they sound more like "relaxation" than restrictions - (and a conformance clause is not supposed to relax normative requirements) as stated in the body.

            Assignee:
            Toby Considine (Inactive)
            Reporter:
            Toby Considine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: