ws-calendar — archive

[Gale Horst <ghorst@epri.com>]

Toby & Team: Great to see this work starting take shape. I have missed some of the calls, so my thinking could be out of sync. But I have a few comments to offer. My comments are below with line number references. Line 169 - make sure a reader who is not familiar with "the well-known iCalendar format" has a reference and ability to learn what this is. Line 177 - "A calendar event without an associated contract is of little use." This seems to be an editorial comment. It does't add value and doesn't allow for the concept of motivation in lieu of control that has been discussed in various related group discussions. Motivation still requires calendar/event communication even if no contract is involved. I suggest simply removing this sentence as well as the same phrase repeated in line 247. In a similar way, other implications of an implied supporting contractual requirement may need to be re-examined. We may want items that include contractual data/ties in the data, indicate that those data elements are optional. (These may be ok as is. But I didn't scan the document with that thought in mind.) Line 284-286 in section 3 WS-Calendar Elements "One should think of these elements as degenerate versions of xCal, as a blind cave fish is a degenerate derivation of a fish outside the cave. The eyes may be gone, but all remaining elements are the same." Should probably re-phrase this. After looking up 'degenerate' in Webster, I think we may not want to call out our work in that way nor the cave fish description. (our work is higher quality ;) Perhaps replace this paragraph with something like: "WS-Calendar elements are semantic elements derived from xCal to standardize data and intervals outside of scheduling interactions. These elements may appear as both a subset and superset of xCal. Although parts of xCal may be excluded, the remaining elements are the same. In a similar way, some WS-Calendar elements may elaborate the objects defined in iCalendar to taylor interactions to meet extended requrirements for utilization. For example, in different organizations, meetings may start on the hour or within 5 minutes of the hour. In those organizations, people learn the expected precision. In WS-Calendar however, that precision must be explicit." Line 432 - I may have missed discussion relative to this question. Is there concern regarding two related items where one preceeds or follows the other? Are we asking for a non-time-based sequence? What is ment by "ENDSWHEN"? Hopefully that is a time/calendar based thing and not tieing in work scheduling such as the work addressed by 6196 part 6 type messages? Gale R. Horst Electric Power Research Institute (EPRI) 942 Corridor Park Blvd. Knoxville, TN 37932 Office: 865-218-8078 Cell: 865-368-2603 ghorst@epri.com