[OASIS Issue Tracker] (WSCALENDAR-507) Section 4 Descriptions

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

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

William Cox updated WSCALENDAR-507:
-----------------------------------

              Summary: Section 4 Descriptions  (was: Section 4.2.1 Model Diagram)
    Affects Version/s: PIM CSPRD02
             Proposal: 
Commenter: Revise Section 4 as a whole to separate normative text from speculation on what other choices might lead to. Pointing out every case in this section and others would require a complete edit of the document so I leave that to the next revision from the TC.

wtc: Consider expression of PSM range of possibilities, as it has not been clear to PSM creators to date.

  was:Revise Section 4 to separate normative text from speculation on what other choices might lead to. Pointing out every case in this section and others would require a complete edit of the document so I leave that to the next revision from the TC.


Update to specify all of Section 4. 4.2.1 is an exemplar of the issue.

> Section 4 Descriptions
> ----------------------
>
>                 Key: WSCALENDAR-507
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-507
>             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
>
>
> Section 4.2.1 Model Diagram reads in part: ***** The class · ToleranceValueType is comprised of a set of optional attributes of DurationType. Tolerances can be expressed in any combination; however, the complexity of rules addressing the relationships of tolerances in start, end, and duration will likely lead to implementation-specific rules limiting the concurrent uses of tolerance attributes. ***** It is difficult to tell is this is expressing a normative requirement or is it simply commentary along the way? The majority of section 4 reads this way so take this as a single example.



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