[OASIS Issue Tracker] (WSCALENDAR-522) Unclear conformance requirements in section 9.2.3 "Conformance issues"

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/WSCALENDAR-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated WSCALENDAR-522:
-----------------------------------

    Resolution: 
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.

Reference: WSCALENDAR-521

  was:Consider placement and wording of Section 9.2.3 and entire Conformance section. Reference: WSCALENDAR-521


> Unclear conformance requirements in section 9.2.3 "Conformance issues"
> ----------------------------------------------------------------------
>
>                 Key: WSCALENDAR-522
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-522
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: PIM
>    Affects Versions: PIM CSPRD02
>         Environment: TAB Comments
>            Reporter: Toby Considine
>            Assignee: William Cox
>             Fix For: PIM WD11
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)