DRAFT MINUTES Web Services Calendar (WS-Calendar) TC 15 February 2013, 12:00pm ET, 06:00pm CET NEW ACTION ITEMS: None. Scribe: Gershon Janssen 0. Roll Call, Agenda review Meeting Attendees Name Company Status ----- ------- ------ Toby Considine University of North Carolina Chair Gershon Janssen Individual Secretary David Thewlis CalConnect Member Michael Douglass Rensselaer Polytechnic Institute Member Benoit Lepeuple LonMark International Member William Cox Individual Member Jeremy Roberts LonMark International Member This meeting quorates. Jeremy Roberts is not a voting member in this meeting. Agenda adopted. 1. Approval of minutes Gershon moves to approve the following minutes: * 18 January 2013 https://www.oasis-open.org/committees/document.php?document_id=47944&wg_abbrev=ws-calendar Mike seconds. No discussion. Minutes approved by unanimous consent. 2. FYI / announcements from Chair, Secretary, Liaison * Chair (Toby) - No comments * Liaison (Dave) - CalConnect XXVI Roundtable was held January 28 - February 1, 2013, hosted by Oracle in Santa Clara, California - New workgroup Tasks started in CalConnect to extend the VTODO component of iCalendar in response to use cases for energy management, project management, work task scheduling, and so forth. URL: http://www.calconnect.org/tc-tasks.shtml * Secretary (Gershon) - No comments 3. Discussion * Moving the SOAP spec to Committtee Spec Motion that the Chair request a Special Majority Ballot to approve as a Committee Specification "WS-Calendar SOAP-based Services Version 1.0", as publicly reviewed at https://www.oasis-open.org/committees/document.php?document_id=47449&wg_abbrev=ws-calendar , and that the Chair and TC Administrator take any necessary actions to accomplish the requested ballot. We further state that the PDF is authoritative. Any references to OASIS work product in process should be updated to the current completed versions of the referenced documents. Bill moves, Mike seconds. No discussion. Roll call vote: --------------- Toby: y Dave: y Gershon: y Mike: y Bill: y Benoit: y 100% yes; motion carries. * Moving the REST Spec to PR Motion 1: Motion that the OASIS WS-Calendar TC issue WS-Calendar Calendar Update and Synchronization with REST-based Services Version 1.0 Working Draft 06 packaged together in the WS_Calendar archive at https://www.oasis-open.org/committees/document.php?document_id=48050&wg_abbrev=ws-calendar as WS-Calendar Calendar Update and Synchronization with REST-based Services Version 1.0 Committee Specification Draft 01 and further direct the Chair to perform any actions required by the TC Administrator, including but not limited to submission forms, to accomplish that issuance as soon as practicable. We further direct that the PDF version of the specification is authoritative. Dave moves, Mike seconds. No discussion. Roll call vote: --------------- Toby: y Dave: y Gershon: y Mike: y Bill: y Benoit: y 100% yes; motion carries. Motion 2: Motion that the OASIS WS-Calendar TC issue WS-Calendar Calendar Update and Synchronization with REST-based Services Version 1.0 Working Draft 06 approved as a Committee Specification Draft, and packaged together in the WS-Calendar archive at https://www.oasis-open.org/committees/document.php?document_id=48050&wg_abbrev=ws-calendar as WS-Calendar Calendar Update and Synchronization with REST-based Services Version 1.0 Committee Specification Draft 02, and further direct the Chair to perform any actions required by the TC Administrator, including but not limited to submission forms, to accomplish that issuance as soon as practicable for a fifteen-day Public Review, and direct the Chairs and TC Administrator to perform the necessary actions for that Public Review to start as soon as practicable. Bill moves, Gershon seconds. NO discussion. Roll call vote: --------------- Toby: y Dave: y Gershon: y Mike: y Bill: y Benoit: y 100% yes; motion carries. * Action item review 20121130-01 Toby: Resolve ambiguities at https://docs.oasis-open.org/ws-calendar/v1.0/ 20130118-01 Mike: Add REST conformance statements to the REST specification 20130118-10 Toby: Create a special majority ballot asking for the REST spec to move to PR -> All done, except 20121130-01 * PIM Review URL: https://www.oasis-open.org/apps/org/workgroup/ws-calendar/email/archives/201302/msg00008.html Bill talks the committee through the PIM document and changes. Area's of improvement the TC spoke about and actions: (1) Ensure that only necessary components are in the model (2) Align model component names to those in WS-Calendar (3) Ensure that there's a clear naming convention (see Setion 1.5, line 46) Bill and toby (4) Eliminate remaining XSD influences (e.g. "anyURI" in LinkType - see lines 276-283) Leave with footnote. Highlight the distinctions between this one, 8601, xsd (5) Write more clearly on the nature of WS-Calendar wrt parameters, properties, and value types (Section 5 line 350ff) WS-Cal has spec reqs for some things to be params which is required for interoperation not rep in PIM, as the distinction is not relevant for the PIM. (6) Clarify the unbound state and how that reflects in the UML model (see e.g. section 2.6 and 3.6.1) Section 2.5 line 160. Start only? Is Vavailability end? Start, or start+duration, or start-end. Nested availability components recurrence rules. Mike will check. General question dtstart and end versus duration. In many cases doesnt matter. Interval hard to float with start and end. OTOH important for a period to start at a given time, end at a given, whether or not DST transition in the middle. Does that matter here? If only allow duration have to be aware of the DST transition. (7) Consider ToleranceValueType and the apparent circularity with respect to DurationValueType (section 3.9) duration DurationType M duration value shouldnt have tolerance simply tolerance? B: Naming dangerous. M: noticed some changes in refs, typos, message in progress. ( Availability and Vavailability -- what is needed in the PIM? Should this be deferred until completion of Vavailability so that the abstraction doesn't need to change? Suggestions? Prefer to keep in, as needed. Update when completed? T: changes in latest? M: Few changes. No longer expired; added a priority value discussion about the algebra of availability. We pretended we thought about it. Cyrus came up with the idea of adding priority to layer in a certain order. Major change was to handle that. T: Earlier discussion apply Vavailability to Vpoll not sure of the word. Granularity and tolerance somewhat differently. Granularity available 3-5pm in 15 minute intervals. M: Divide time into slots granularity. Tolerance how small/accurate in your timing. T: Granularity mattersoffice hours 3-5, granularity 30 minutes, schedule me at 330, not 333. In Vpoll. Looking for a one hour meeting starting on a half hour, weekday aftenroons in the second half of the month. B: dont want to track Vav wait until clean. T: Conf with PIM are conf with WS-Calendar. (9) Conformance (Section 6 line 363ff): the changes aren't visible, but are minor and the same as the previous draft. All confomance non-normative because its a quote. Footnote for type differences. Normative (10) Thoughts on other elements of Intervals, line 452ff - not sure how relevant these conformance requirements are; partitions seem to be moving toward a streams representation in part, and the other elements (Description, Summary, Priority) aren't in the PIM. Should they be? Mike look. (11) Improved text for section 3.4 (line 188ff) on primitive types. Are the references and description right? All look. (12) Comments on all other YELLOW highlighted text All look. 4. Any Other Business? - 30 days review on strings is almost over; if you have comments; please post them to the list. 5. Adjourn Meeting Adjourned.