OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-calendar message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (WSCALENDAR-507) Section 4.2.1 Model Diagram


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

William Cox commented on WSCALENDAR-507:
----------------------------------------

Part of the exposition reflects on use of the normative reference ISO 8601, where intervals are defined with start, end, and duration, any two of which are optional.

Section 4 should be edited to reflect normative decisions, but the possible expressions in a PSM should be described - we have two PSMs that I've worked with: (1) WS-Calendar 1.0, where start-duration is the required combination, and the ASHRAE SPC201P PSM with respect to the PIM where start and end are required. The optionality and semantics are defined by a PSM, and expressing the range of possibilities seems important.

Modified to address SECTION 4 in its entirety.

> Section 4.2.1 Model Diagram
> ---------------------------
>
>                 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
>         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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]