RE: [ws-calendar] Groups - WS-Calendar-1 0-spec-wd-06.pdf uploaded

["Considine, Toby (Campus Services IT)" <Toby.Considine@unc.edu>]

Excellent points all.

Contract is meant to be a web service contract, which is only tangentially a business contract. Without a contract (something we are requesting, or notifying, some xml payload which is expected to elicit a response, what do we have?

I welcome suggestions....

Define what a contract means in web services?
Some other words?

I agree that the repetition, an artifact of editing is not good.

Yeah, degenerate only makes sense to a biologist. Your appendix and the cave-fish are both degenerate. Will re-work.

As to sequence, there is no guarantee, nor valid expectation that a set of xml objects will maintain order when processed and re-processed. Hence each needs a sequence (A then B then C then D). Other sequences and other technologies may have different constraints.

I put the sequence words in yellow, because they need discussion (as you identified)
B may follow A
A may precede B
A and B may need to start at the same time
A and B may need to finish at the same time.
D may have a requirement of finishing before J is scheduled to start.

I was trying to reach for the basic project sequencing requirements.

Thanks, Gale...

tc








"If flies are allowed to vote, how meaningful would a poll on what to have for dinner be, and what would be on the menu?" -  Unknown

Toby Considine
Chair, OASIS oBIX Technical Committee
OASIS Technical Advisory Board
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee 
Facilities Technology Office
University of North Carolina
Chapel Hill, NC
  
Email: Toby.Considine@ unc.edu
Phone: (919)962-9073 
http://www.oasis-open.org 
blog: www.NewDaedalus.com



-----Original Message-----
From: Horst, Gale [mailto:ghorst@epri.com] 
Sent: Thursday, May 20, 2010 12:24 PM
To: Considine, Toby (Campus Services IT); ws-calendar@lists.oasis-open.org
Subject: RE: [ws-calendar] Groups - WS-Calendar-1 0-spec-wd-06.pdf uploaded

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 

-----Original Message-----
From: toby.considine@unc.edu [mailto:toby.considine@unc.edu]
Sent: Wednesday, May 19, 2010 8:05 PM
To: ws-calendar@lists.oasis-open.org
Subject: [ws-calendar] Groups - WS-Calendar-1 0-spec-wd-06.pdf uploaded

Here is the version, at last, with monor revisions to allign better with calws work. The document also incldes a link to the CalConnect document, submitted for public review this week as well.

Here's the URL that will soon work to the document:

http://www.calconnect.org/pubcomment/CD1004 Cal-WS Web Services API V0.3.pdf

Here is information about CalConnect Public Review & Comment process

http://www.calconnect.org/publicreviewdocuments.shtml

This also provides a link to the document, and also to the review and comment mailing list info and signup page.

Thanks. I know it has been a push to get to this point, and I apreciate your comemnts on and off line.

tc

 -- Toby Considine

The document revision named WS-Calendar-1 0-spec-wd-06.pdf has been submitted by Toby Considine to the OASIS Web Services Calendar
(WS-Calendar) TC document repository.  This document is revision #2 of
WS-Calendar-1 0-spec-wd-06 with changes.doc.

Document Description:
Working draft for informal public comments

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=37888

Download Document:  
http://www.oasis-open.org/committees/download.php/37888/WS-Calendar-1%20
0-spec-wd-06.pdf

Revision:
This document is revision #2 of WS-Calendar-1 0-spec-wd-06 with changes.doc.  The document details page referenced above will show the complete revision history.


PLEASE NOTE:  If the above links do not work for you, your email application may be breaking the link into two pieces.  You may be able to copy and paste the entire link address into the address field of your web browser.

-OASIS Open Administration