[OASIS Issue Tracker] (WSCALENDAR-508) 3.1 Time Intervals and (more normative language)

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

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

William Cox updated WSCALENDAR-508:
-----------------------------------

    Resolution: 
(1) the PIM semantics must be self-contained (free standing)
(2) the relationship of the PIM to WS-Calendar must be the same as any PIM to its respective PSMs (i.e., that to understand the PIM one must not be required to read one specific PSM, which would be a normative reference nightmare)
(3) the exposition must be clear to the reader who looks at WS-Calendar and then WS-Calendar PIM
(4) the exposition must clearly use UML terminology rather than XSD terminology (this would clean up section 2.5)

Finally, the circularity in normative reference is addressed by changing the normative reference to WS-Calendar 1.0 to informative. 

> 3.1 Time Intervals and (more normative language)
> ------------------------------------------------
>
>                 Key: WSCALENDAR-508
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-508
>             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
>
>
> 3.1 Time Intervals and Collections of Time-Related Intervals reads in part: ***** Certain terms appear throughout this document and are defined in Table 3‑1. Some terms are discussed in greater depth in later sections. In all cases, the normative definition is in this section. WS-Calendar terminology begins with a specialized terminology for the segments of time, and for groups of related segments of time. These terms are defined in Table 3‑1 through Table 3‑4 below, and are quoted from [WS-Calendar]. The definitions are normative because this is a standalone specification. ***** The "The definitions are normative because this is a standalone specification." was the first thing that caught my eye. Really? Standalone or not that sentence makes no sense. But then noticing, "certain terms," "some terms," etc. Rather than copying from WS-Calendar, why not make a profile of WS-Calendar that has the six (6) changes listed in Appendix D and then require conformance to WS-Calendar and then this as a profile? A lot less writing and unnecessary UML diagrams.



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