[OASIS Issue Tracker] (WSCALENDAR-504) General: Support the simple case more directly

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

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

William Cox commented on WSCALENDAR-504:
----------------------------------------

Our examples for building/facility management are in ASHRAE 201; that's a counterexample for "the simple stuff" -- you can't do facility schedules without those gaps.

Logging behavior might be sporadic or interval based. 

201 uses specialized intervals with dt_start and dt_end which satisfies one approach to process scheduling and management.

The text sounds like it's already in several other places, and suggested by e.g. WSCALENDAR-502 

I suggest making this a sub-issue to WSCALENDAR-502 which addresses the larger question without getting into specific domain design approaches and existing practice.

> General: Support the simple case more directly
> ----------------------------------------------
>
>                 Key: WSCALENDAR-504
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-504
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: STRM CSPRD02
>         Environment: Steve Ray
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>             Fix For: STRM WD06
>
>
> While it seems to support many different kinds of collections of intervals and is therefore pretty powerful, it doesn't seem very easy to do the simple stuff - i.e. most people will likely do simple linear sequences most of the time. In the ASHRAE SPC201P FSGIM committee, while we are inheriting WS-Cal and are using it for the general case, we created a way to do this simple case directly. As I recall, I think that's the Sequence class which contains an ordered set of SimpleIntervals.



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