From 0e1dbae7d1666746df81d3a589bc450096f1c2cc Mon Sep 17 00:00:00 2001 From: anermina <55683568+anermina@users.noreply.github.com> Date: Fri, 20 Dec 2024 01:14:22 +0100 Subject: [PATCH] Remove the encodings named with csd --- sources/csd-report-conference-30.adoc | 292 -------------------- sources/csd-report-conference-31.adoc | 304 --------------------- sources/csd-report-conference-32.adoc | 343 ------------------------ sources/csd-report-conference-33.adoc | 287 -------------------- sources/csd-report-conference-34.adoc | 228 ---------------- sources/csd-report-conference-35.adoc | 199 -------------- sources/csd-report-conference-36.adoc | 238 ---------------- sources/csd-report-conference-37.adoc | 220 --------------- sources/csd-report-conference-38.adoc | 205 -------------- sources/csd-report-conference-39.adoc | 203 -------------- sources/csd-report-conference-40.adoc | 193 ------------- sources/csd-report-conference-41.adoc | 201 -------------- sources/csd-report-conference-42.adoc | 217 --------------- sources/csd-report-conference-43.adoc | 237 ---------------- sources/csd-report-conference-44.adoc | 218 --------------- sources/csd-report-conference-45.adoc | 204 -------------- sources/csd-report-conference-46.adoc | 261 ------------------ sources/csd-report-ioptestevent-26.adoc | 108 -------- sources/csd-report-ioptestevent-27.adoc | 119 -------- sources/csd-report-ioptestevent-28.adoc | 106 -------- sources/csd-report-ioptestevent-29.adoc | 103 ------- sources/csd-report-ioptestevent-30.adoc | 91 ------- sources/csd-report-ioptestevent-31.adoc | 85 ------ sources/csd-report-ioptestevent-32.adoc | 110 -------- sources/csd-report-ioptestevent-33.adoc | 92 ------- sources/csd-report-ioptestevent-34.adoc | 93 ------- sources/csd-report-ioptestevent-35.adoc | 77 ------ sources/csd-report-ioptestevent-36.adoc | 191 ------------- sources/csd-report-ioptestevent-37.adoc | 113 -------- sources/csd-report-ioptestevent-38.adoc | 95 ------- sources/csd-report-ioptestevent-39.adoc | 83 ------ sources/csd-report-ioptestevent-40.adoc | 119 -------- sources/csd-report-ioptestevent-41.adoc | 78 ------ sources/csd-report-ioptestevent-42.adoc | 79 ------ sources/csd-report-roundtable-1.adoc | 84 ------ sources/csd-report-roundtable-10.adoc | 172 ------------ sources/csd-report-roundtable-11.adoc | 163 ----------- sources/csd-report-roundtable-12.adoc | 140 ---------- sources/csd-report-roundtable-13.adoc | 160 ----------- sources/csd-report-roundtable-14.adoc | 123 --------- sources/csd-report-roundtable-15.adoc | 167 ------------ sources/csd-report-roundtable-16.adoc | 160 ----------- sources/csd-report-roundtable-17.adoc | 178 ------------ sources/csd-report-roundtable-18.adoc | 186 ------------- sources/csd-report-roundtable-19.adoc | 178 ------------ sources/csd-report-roundtable-2.adoc | 149 ---------- sources/csd-report-roundtable-20.adoc | 92 ------- sources/csd-report-roundtable-21.adoc | 107 -------- sources/csd-report-roundtable-22.adoc | 107 -------- sources/csd-report-roundtable-23.adoc | 98 ------- sources/csd-report-roundtable-24.adoc | 104 ------- sources/csd-report-roundtable-25.adoc | 121 --------- sources/csd-report-roundtable-26.adoc | 261 ------------------ sources/csd-report-roundtable-27.adoc | 266 ------------------ sources/csd-report-roundtable-28.adoc | 258 ------------------ sources/csd-report-roundtable-29.adoc | 230 ---------------- sources/csd-report-roundtable-3.adoc | 120 --------- sources/csd-report-roundtable-4.adoc | 111 -------- sources/csd-report-roundtable-5.adoc | 106 -------- sources/csd-report-roundtable-6.adoc | 110 -------- sources/csd-report-roundtable-7.adoc | 127 --------- sources/csd-report-roundtable-8.adoc | 169 ------------ sources/csd-report-roundtable-9.adoc | 146 ---------- 63 files changed, 10185 deletions(-) delete mode 100644 sources/csd-report-conference-30.adoc delete mode 100644 sources/csd-report-conference-31.adoc delete mode 100644 sources/csd-report-conference-32.adoc delete mode 100644 sources/csd-report-conference-33.adoc delete mode 100644 sources/csd-report-conference-34.adoc delete mode 100644 sources/csd-report-conference-35.adoc delete mode 100644 sources/csd-report-conference-36.adoc delete mode 100644 sources/csd-report-conference-37.adoc delete mode 100644 sources/csd-report-conference-38.adoc delete mode 100644 sources/csd-report-conference-39.adoc delete mode 100644 sources/csd-report-conference-40.adoc delete mode 100644 sources/csd-report-conference-41.adoc delete mode 100644 sources/csd-report-conference-42.adoc delete mode 100644 sources/csd-report-conference-43.adoc delete mode 100644 sources/csd-report-conference-44.adoc delete mode 100644 sources/csd-report-conference-45.adoc delete mode 100644 sources/csd-report-conference-46.adoc delete mode 100644 sources/csd-report-ioptestevent-26.adoc delete mode 100644 sources/csd-report-ioptestevent-27.adoc delete mode 100644 sources/csd-report-ioptestevent-28.adoc delete mode 100644 sources/csd-report-ioptestevent-29.adoc delete mode 100644 sources/csd-report-ioptestevent-30.adoc delete mode 100644 sources/csd-report-ioptestevent-31.adoc delete mode 100644 sources/csd-report-ioptestevent-32.adoc delete mode 100644 sources/csd-report-ioptestevent-33.adoc delete mode 100644 sources/csd-report-ioptestevent-34.adoc delete mode 100644 sources/csd-report-ioptestevent-35.adoc delete mode 100644 sources/csd-report-ioptestevent-36.adoc delete mode 100644 sources/csd-report-ioptestevent-37.adoc delete mode 100644 sources/csd-report-ioptestevent-38.adoc delete mode 100644 sources/csd-report-ioptestevent-39.adoc delete mode 100644 sources/csd-report-ioptestevent-40.adoc delete mode 100644 sources/csd-report-ioptestevent-41.adoc delete mode 100644 sources/csd-report-ioptestevent-42.adoc delete mode 100644 sources/csd-report-roundtable-1.adoc delete mode 100644 sources/csd-report-roundtable-10.adoc delete mode 100644 sources/csd-report-roundtable-11.adoc delete mode 100644 sources/csd-report-roundtable-12.adoc delete mode 100644 sources/csd-report-roundtable-13.adoc delete mode 100644 sources/csd-report-roundtable-14.adoc delete mode 100644 sources/csd-report-roundtable-15.adoc delete mode 100644 sources/csd-report-roundtable-16.adoc delete mode 100644 sources/csd-report-roundtable-17.adoc delete mode 100644 sources/csd-report-roundtable-18.adoc delete mode 100644 sources/csd-report-roundtable-19.adoc delete mode 100644 sources/csd-report-roundtable-2.adoc delete mode 100644 sources/csd-report-roundtable-20.adoc delete mode 100644 sources/csd-report-roundtable-21.adoc delete mode 100644 sources/csd-report-roundtable-22.adoc delete mode 100644 sources/csd-report-roundtable-23.adoc delete mode 100644 sources/csd-report-roundtable-24.adoc delete mode 100644 sources/csd-report-roundtable-25.adoc delete mode 100644 sources/csd-report-roundtable-26.adoc delete mode 100644 sources/csd-report-roundtable-27.adoc delete mode 100644 sources/csd-report-roundtable-28.adoc delete mode 100644 sources/csd-report-roundtable-29.adoc delete mode 100644 sources/csd-report-roundtable-3.adoc delete mode 100644 sources/csd-report-roundtable-4.adoc delete mode 100644 sources/csd-report-roundtable-5.adoc delete mode 100644 sources/csd-report-roundtable-6.adoc delete mode 100644 sources/csd-report-roundtable-7.adoc delete mode 100644 sources/csd-report-roundtable-8.adoc delete mode 100644 sources/csd-report-roundtable-9.adoc diff --git a/sources/csd-report-conference-30.adoc b/sources/csd-report-conference-30.adoc deleted file mode 100644 index 8669330..0000000 --- a/sources/csd-report-conference-30.adoc +++ /dev/null @@ -1,292 +0,0 @@ -= Report on CalConnect Conference XXX, May 21-23, 2014 -:docnumber: 1405 -:copyright-year: 2014 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2014-06-09 -:published-date: 2014-06-09 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-30 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -NOTE: Following CalConnect XXIX in February, the term "Roundtable" was replaced by "Conference" -or "CalConnect Conference". - -CalConnect Conference XXX took place on February 5-7, 2014, hosted by AOL in Dulles, -Virginia. The CalConnect Conference was attended by 28 people from 12 members and 8 nonmembers -(observers). The CalConnect Interoperability Test Event was held immediately prior to -the Roundtable on February 3-5, and had 12 participants onsite from 8 members and one nonmember, -plus two members testing remotely. An additional 21 people from 8 organizations -attended the Wednesday workshop (see below) and did not attend any part of the Conference. In -total, 49 people from 29 organizations attended some portion of the week. - -The Conference consisted primarily of technical committee sessions, workshops and BOFs. In -addition two live demonstrations of work under development were offered, as was a special -session reporting on the effort to restructure the CalConnect Steering Committee. The sessions -were as usual organized sequentially without competing parallel sessions, as is our standard -practice, to allow all attendees who wished to be involved in the discussions of each Technical -Committee the opportunity to do so. The Conference finished with the CalConnect Plenary -Session on Friday afternoon. - -== Special Events - -A public Workshop on the Veterans Administration Scheduling System Challenge was held -Wednesday afternoon and was attended by 47 people, 21 of whom came for the workshop alone. -Most Conference participants were present for the Workshop as well. A separate report on the -workshop can be found at -http://www.calconnect.org/vachallengeworkshopreport.shtml[VA Scheduling System Workshop Report]. - -A BoF on CalConnect and the IETF was held Thursday afternoon with the two Application Area -ADs from the IETF attending Thursday morning and through the BoF. The goal of the BoF was to -explore ways to better integrate IETF and CalConnect processes and allow for smoother -progression of drafts through the IETF once submitted. A formal liaison between the IETF and -CalConnect was suggested and will be explored. - -== Documents since Last Roundtable - -Much of the work in CalConnect is focused on specifications to become internet draft -submissions to the IETF and -ultimately be progressed to become RFCs (Proposed Standards), rather than be directly -published by CalConnect itself. - -=== Published Documents - -* Report on Roundtable XXIX -* Report on Interoperability Test Event XXIX -* 7 Things You Should Know About PUSH -* Starter List of CalDAV and CardDAV Standards and Specifications - -=== Updated Internet Drafts and Published RFCs - -* https://tools.ietf.org/html/rfc7265[jCal: The JSON Format for iCalendar] (RFC 7265) -* https://tools.ietf.org/html/draft-daboo-icalendar-rscale/[Non-Gregorian Recurrence Rules in iCalendar] -* https://tools.ietf.org/html/draft-daboo-caldav-attachments/[CalDAV Managed Attachments] -* https://datatracker.ietf.org/doc/draft-york-vpoll/[VPOLL: Consensus Scheduling Component for iCalendar] -* https://tools.ietf.org/html/draft-daboo-caldav-extensions[Collected Extensions to CalDAV] -* https://www.ietf.org/html/draft-daboo-caldav-timezone/[CalDAV: Timezones by Reference] - -== Update on Technical Committee Work and Initiatives Including BOFs and Workshops - -=== CALSCALE Ad Hoc - -No session was held for the CALSCALE Ad Hoc as the draft is now pending progression at the -IETF. The draft was updated following CalConnect XXIX: -https://tools.ietf.org/html/draft-daboo-icalendar-rscale/[Non-Gregorian Recurrence Rules in iCalendar]. -The Ad Hoc continues to explore ways of better explaining and documenting proper -RRULE RSCALE expansions for different non-Gregorian calendars. - -=== CONTACTS Provisional Committee - -The Contacts Sharing Provisional Committee demonstrated sharing models in use today including -Apple, BusyContacts, Fruux, Kerio and Zimbra. The current calendar sharing and notifications -draft specifications will be refactored into four or more focused specifications: Notification -framework, WebDAV collection sharing, CalDAV sharing, and CardDAV sharing. The Provisional -Committee will begin developing its Charter to become a Technical Committee. - -=== FSC (Federated Shared Calendars) Ad Hoc - -The Ad Hoc presented its work so far on calendars can be shared between different services and -users, and the points of intersection between the work of the Ad Hoc and the work begun in the -Contacts Sharing Provisional Committee. The draft Charter for the proposed TC FSC will be -circulated after the Conference and instantiation as a Technical Committee should happen next -month. - -=== Itinerary Ad Hoc - -No session was held at the conference. The goal is to improve the user experience with itinerary -info from travel sites by extending iCalendar to incorporated needed information; however, we -need input from travel industry experts on what is needed. The Ad Hoc continues to look for -experts to inform the work. - -=== TC API - -The TC discussed progress since the last Conference: a charter was developed and instantiation as -a Technical Committee was approved. The Technical Committee is making some progress on an -abstract API and believes it has a framework in which to work. The hardest issue to deal with -short-term is searching: we need to develop an abstract searching approach to provide much richer -capabilities than at present. The TC has begun work on a 7 Things document, somewhat -handicapped by the abstract nature of the topic and the work being done. - -=== TC AUTODISCOVERY - -No TC session was held at this conference. The TC has produced an initial draft of a mechanism -for multiple service discovery via a single protocol for client setup and submitted to the IETF: -https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-%20discovery/[Aggregated Service Discovery]. -We are waiting for an opportunity to move this forward at the IETF. - -=== TC CALDAV - -Several ongoing topics were presented and discussed, including - -* Rich Capabilities - the basic outline was discussed. Current issues including backwards -compatibility with the DAV header and efficient change notification will be considered by -the TC. - -* Storing encrypted data on a CalDAV server - input from the IETF was that it was important -to expose this work early, and the TC will look into creating a problem statement to take to -an appropriate IETF WAG. - -* Draft Events - an outline of a possible solution was presented and discussed, but the feeling -was that the approach was overly complex; the TC will work on a more streamlined -approach. - -* Group scheduling - a new topic from the interoperability test event earlier in the week. -Discussed how scheduling with groups and "self-invite" modes of scheduling could be -implemented in iCalendar and CardDAV; there is interest in the TC in working in this area. - -* New issue in the meeting - possibility of defining a simple HTTP-based iTIP response -option so that web services can implement a simple request/response scheduling feature -without having to implement an e-mail service. - -* REMOVED PARTSTAT - another issue from the interoperability testing, the addition of a -new REMOVED partstat to allow attendees (VPOLL) voters) to have themselves entirely -removed from an invite rather than just decline. This will probably be work on in TC -FREEBUSY. - -=== TC EVENTPUB - -TC EVENTPUB has not been active since shortly after the last Conference. We summarized the -state of the internet drafts (below) and are waiting for the first batch to progress. Some minor -modifications to the drafts may be required to handle issues raised in other TCs, especially -handling of referenced vCard data. The CONFERENCE property removed from one of the drafts -is now becoming of interest so we will have one or more EVENTPUB calls in the near future to -discuss adding it again. The current EVENTPUB drafts referenced above are -https://tools.ietf.org/html/draft-douglass-calendar-extension/[Event Publication Extensions to iCalendar] -and https://tools.ietf.org/html/draft-daboo-icalendar-extensions[New Properties for iCalendar]. - -=== TC FREEBUSY - -The TC reviewed the draft specification: -https://tools.ietf.org/html/draft-york-vpoll-00[VPOLL: Consensus Scheduling Component for iCalendar]. -Following the review a live demonstration was held of VPOLL via iSCHEDULE -between three implementations to show the technology and how it integrates different protocols. -The presentation was very well received especially by some of the observers from the Health Care -sector. We also discussed other ways of using VPOLL for bidding and assignments; a goal of the -TC going forward is to assemble use cases and develop alternative poll modes. - -=== TC IOPTEST - -The TC conducted a busy interoperability test event, with many basic CalDAV access issues -uncovered, and some fixed. Three servers tested and eventually demonstrated a combination of -VPOLL and iSCHEDULE (see the TC FREEBUSY entry above). The complete VPOLL and -subsequent meeting request sequence worked; there are still some issues with freebusy lookup. -Also conducted some testing go CalDAV scheduling and CardDAV sharing. The event report may -be found at -https://www.calconnect.org/events/event-reports#ioptestevents[CalConnect Interoperability Test Event Reports]. - -=== TC ISCHEDULE - -TC ISCHEDULE offered a brief overview of the iSchedule protocol followed by a discussion of -what we have termed the "identify crisis" problem and the proposed solution that the TC has been -working on. (The "identify crisis" is how to determine the actual calendar user address of an -invitee when the invitation is being managed via iSchedule.) The proposed solution involve three -new pieces (as far as iSchedule is concerned): Webfinger, a "scheduleto" URI and a SCHEDULEADDRESS -parameter. Following up on this the TC will review the current proposal and work on -moving the iSchedule work into the IETF as soon as possible to that we can get feedback on the -identity issues from other technical areas and experts within the IETF. - -=== TC PUSH - -TC PUSH presented the recent work of the Technical Committee. The first piece has been a -schema to allow servers to advertise supported push transports. A brief introduction was done into -some of th existing push concepts for those not familiar with some of the terms and technologies. -The TC presented three different scenarios for push and how they differ when it comes to -subscribing to change notifications for a resource. It was pointed out that vendors are unlikely to -change their (existing) push implementation, and we discussed the concept of a push gateway that -abstracts from the actual push transport and provides a standardized push interface to application -servers. - -=== TC RESOURCE - -A presentation on the resource schema work so far was followed by a discussion of resource -schemas for building management, etc. We need to look at ways to integrate or provide APIs for -information relevant to the calendaring and scheduling world. Information in the structured -location draft as to how to provide it so it is always available for users. The TC is now waiting on -its drafts to be processed so will be dormant unless an issue comes up that must be addressed by -the TC. - -=== TC TASKS - -The TC presented its work to date and is currently refining its overall draft for enhancing task -scheduling in iCalendar. The main issue for discussion was how to track or maintain a history of -changes occurring in an iCalendar object, in particular changes to status information and info -added to iTIP replies for tasks. In particular, the question of where to employ inline data versus -pointers to external message streams, versioning, etc. must be addressed; the next few TC calls -will be devoted to this topic, and the TC is asking interested people to participate. - -=== TC TIMEZONE - -The TC has been largely dormant since the last Conference. We briefly summarized the state of -the draft Timezone Service Protocol and Timezones by Reference drafts. We also discussed an -issue raised on the IETF CALDAV list related to MS timezones and server handling of them when -implicit timezones are enabled. It may be time to start pushing idea of an IANA registry as part of -the IETF process. The relevant drafts are -https://www.ietf.org/html/draft-daboo-caldav-timezone/[Timezone Service Protocol and CalDAV: Timezones by Reference]. - -=== VA Workshop Follow-up - -CalConnect extended its thanks to all who were invited and who participated. We will follow up -with more personal contacts, and will setting up short-lived mailing list for everyone who -attended. We learned that lots could be done in areas of scheduling and health care; our challenge -is to absorb expertise but the thing that will drive it is having a member or so in health care -industry (similar to DHL in tasks). We aren't ready to tackle the entire area but could cut out -tractable sections such as recurrences in prescription meds. Hopefully we will have a dialog and -one or more members with a business objective who see that CalConnect is where to realize that -objective. - -== Plenary Decisions - -The Federated Shared Calendars (FSC) Ad Hoc Committee and the CONTACTS Provisional -Committee will begin the process to establish themselves as full Technical Committees. - -The offer from Youcanbook.me to host the Autumn 2014 event in Bedford, England was -confirmed. - -== Future Events - -* CalConnect XXXI: September 29 - October 3, 2014, Youcanbookme, Bedford, England -* CalConnect XXXII: January 26-30, 2015, Kerio Technologies, San Jose, California -* CalConnect XXXIII: Spring, 2015, TBD -* CalConnect XXXIV: Autumn, 2015, Amsterdam, The Netherlands (tentative) - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Conference (presentations, TC sessions, -BOFs, networking, Plenary) -* The format for European events is to move TC sessions to the afternoon and offer symposia and -BOFs during Thursday and Friday mornings. diff --git a/sources/csd-report-conference-31.adoc b/sources/csd-report-conference-31.adoc deleted file mode 100644 index cfac235..0000000 --- a/sources/csd-report-conference-31.adoc +++ /dev/null @@ -1,304 +0,0 @@ -= Report on CalConnect Conference XXXI, October 1-3, 2014 -:docnumber: 1406 -:copyright-year: 2014 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2014-10-16 -:published-date: 2014-10-16 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-31 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -NOTE: Following CalConnect XXIX in February, the term "Roundtable" was replaced by "Conference" or -"CalConnect Conference". - -CalConnect Conference XXXI took place on October 1-3, 2014, hosted by Youcanbook.me in Bedford, -United Kingdom.. The CalConnect Conference was attended by 19 people from 13 members. The -Interoperability Test Event was held immediately prior to the Conference on September 29 - October 1, -February 3-5, and had 15 participants onsite from 9 members; an additional 4 people from 3 members -attended the test event remotely. In total, 21 people from 13 organizations attended some portion of the -week. - -The Conference consisted primarily of technical committee sessions, workshops and BOFs. In addition a -live demonstration of work under development was offered, plus a BoF (Birds of a Feather Session) and -two Workshops. The sessions were as usual organized sequentially without competing parallel sessions, -as is our standard practice, to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. The Conference finished with the CalConnect Plenary -Session on Friday afternoon. - -== Special Events - -Two Workshops were held on Thursday morning and Friday morning: Groups Scheduling and Sharing -and History and Comment Feeds in iCalendar. A Birds of a Feather session on developing a unified -Calendaring & Scheduling Architecture was also held on Friday. A retrospective presentation on the -Veterans' Administration Health Care Workshop held at CalConnect XXX in May was also offered on -Thursday. - -== Documents since Last Roundtable - -Much of the work in CalConnect is focused on specifications to become internet draft submissions to the IETF and ultimately be -progressed to become RFCs (Proposed Standards), rather than be directly published by CalConnect itself. - -=== Published Documents - -* Report on CalConnect Conference XXX -* Report on Interoperability Test Event XXX -* 7 Things You Should Know About the Abstract Calendaring API -* Updated Starter List of CalDAV and CardDAV Standards and Specifications - -=== CalConnect Internet Drafts Adopted for Progression via IETF Working Groups - -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[CalDAV: Timezones by Reference] -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[Time Zone Data Distribution Service] -* https://datatracker.ietf.org/doc/draft-ietf-calext-rscale[Non-Gregorian Recurrence Rules in iCalendar] - -=== Updated Internet Drafts and Published RFCs - -* http://tools.ietf.org/html/rfc7265[jCal: The JSON Format for iCalendar] (RFC 7265) -* https://datatracker.ietf.org/doc/draft-douglass-ical-relations/[Support for iCalendar Relationships] -* https://datatracker.ietf.org/doc/draft-york-vpoll/[VPOLL: Consensus Scheduling Component for iCalendar] -* http://tools.ietf.org/html/draft-daboo-icalendar-extensions[New Properties for iCalendar] -* https://datatracker.ietf.org/doc/draft-murchison-webdav-prefer/[Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)] - -== Update on Technical Committee Work and Initiatives Including BOFs and Workshops - -=== BOF on Calendaring & Scheduling Architecture - -The BOF discussed whether Tasks and Events are different concepts or simply the same thing with -different details. Tasks can but don't have to be time-based; Events might not have a start or end date -especially with VAVAILABILITY/VPOLL. Our architecture document should start with the model rather -than from the user perspective; an interactive diagram would be nice to avoid a too-rich diagram. The -architecture is currently under the auspices of TC API. - -=== CALSCALE Ad Hoc - -No session was held at the conference. The Ad Hoc is on hold pending progression of the RSCALE draft -now adopted as a -https://datatracker.ietf.org/doc/draft-ietf-calext-rscale/[CALEXT Working Group] -draft in the IETF for progression to become an RFC: -https://datatracker.ietf.org/doc/draft-ietf-calext-rscale/[Non-Gregorian Recurrence Rules in iCalendar]. - -=== ITINERARY Ad Hoc - -No session was held at the conference. The goal is to improve the user experience with itinerary info from -travel sites by extending iCalendar to incorporated needed information; however, we need input from -travel industry experts on what is needed. The Ad Hoc continues to look for experts to inform the work. - -=== TC API - -The TC offered an overview of work since the last conference, including data objects, relations and -operations. Details about the REST API we have been discussing were reviewed, and fruux gave a demo -on their REST API. YCBM (Youcanbook.me) provided a demo on Calligraph, a tool they have developed -to federate multiple calendar sources. - -=== TC AUTODISCOVERY - -No TC session was held at this conference. The TC has produced an initial draft of a mechanism for -multiple service discovery via a single protocol for client setup and submitted to the IETF: -https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery]. We are waiting for an opportunity to move this forward at the IETF. - -=== TC CALDAV - -Several topics were discussed in the session. - -* Server-Info document: The basic outline was presented and discussed. A discussion of where the -document should "live" ensued. The consensus is to define a WebDAV property and also use a Link -header in the OPTIONS response. Another discussion was about whether to include "constant" -properties. The TC will research current client PROPFINDs and then see what is best, but probably -scope it as close as possible to the impacted resources. - -* Scheduling Drafts: The basic outline of a solution was presented and discussed. The overall feeling -was to initially move forward with the approach for new drafts only. The TC will do more work on -how best to handle the "lost update" problem when creating drafts from existing resources. - -* Calendar Principal Searching: All agreed that DAV:principal-property-search is too structured and -something better is needed. The TC will look into whether the existing report can be augmented with -a custom property or a new report should be created (e.g. standardizing the calendarserverprincipal- -search report). - -* Discussion of the status of WebDAV Prefer Draft and whether return=representation should be -allowed on a precondition failure. The consensus was that it should be allowed to eliminate the need -for the client to fetch the new resource in a separate request. The draft will be refreshed, reviewed -and submitted to IETF. - -* Discussion on use of patch/diffs for client updates and whether ETag, Schedule-Tag is sufficient for -that. The TC will investigate formalizing a diff format for CalDAV with a preference for a JSON-based -solution. - -=== TC EVENTPUB - -TC EVENTPUB summarized the state of its current drafts; the TC has been dormant as we wait for the -backlog of drafts before the IETF to clear. There was some discussion about the new CONFERENCE -property and colors. The current EVENTPUB drafts referenced above are -http://tools.ietf.org/html/draft-douglass-calendar-extension/[Event Publication Extensions to iCalendar] -and https://datatracker.ietf.org/doc/html/draft-daboo-icalendar-extensions[New Properties for iCalendar]. - -=== TC FREEBUSY - -The TC reviewed the draft specification: https://tools.ietf.org/html/draft-york-vpoll-00[VPOLL: Consensus Scheduling Component for iCalendar] and -the BASIC poll mode, then presented some of the thoughts we have had in the TC and also in TC TASKS -about a new task assignment poll mode. We also talked about signup modes which could support -informal event planning, and discussed the possible use of VPOLL for simple resource management. The -TC also offered a quick demo of a VPOLL client. - -=== TC FSC - -TC FSC (Federated Shared Calendars) was formed from the FSC Ad Hoc Committee following -CalConnect XXX. The TC presented the current design for federated shared calendars. There was a lot of -discussion of enhancing subscribed calendar behavior versus using CalDAV, with the consensus moving -towards a more CalDAV-like approach via links to upgrade subscriptions directly into CalDAV -- used in -either a server-to-server or client-to-server mode. Ultimately we will use TC-API work for the sharing -protocol. The nature of invites (iCalendar or XML) still needs to be decided. We are leaning towards a -more generic TC SHARING type of sharing mode. - -=== TC IOPTEST - -A busy and productive session. As always much testing of various CalDAV features. Some new implicit -scheduling implementations testing against clients. Two participants were trying to get VPOLL up and -running across multiple servers but ran into some implementation issues and eventually ran out of time. -TC IOPTEST will start building a list of areas to test next time immediately -- starting early may help to -provide some specific implementation goals. Will be building this in the TESTING-NOTES etherpad. -Finally we hope to have PUSH implementations for testing in January. The event report may be found at -https://www.calconnect.org/events/event-reports#ioptestevents[CalConnect Interoperability Test Event Reports] once completed. - -=== TC ISCHEDULE - -The proposed solution to the "identity crisis" problem was presented; namely webfinger, SCHEDULE-TO -URI and SCHEDULE-ADDRESS property parameter. Lots of discussion about using SCHEDULEADDRESS -as opposed to setting the routing address as the value of the property. Major pushback for -changing the property value is that it may break existing clients which don't understand SCHEDULE-TO -URIs. The session ended without a clear consensus. The TC will investigate how clients will handle the -property value being changed. This will probably wait on IETF to start a Working Group to progress the -iSchedule draft, and we will leave it as as open issue in the draft. - -=== TC PUSH - -We presented the latest output of the TC, including the new architecture, discovery of push-transports and -a push protocol. There was a discussion about who defines what a topic is. Clients might want to be able -to define in more detail what they are interested in. We might add that as an extension later on. Also, we -briefly discussed the option to use an asynchronous call to the gateway-select URL and return an id the -client can use to check if the subscription is still valid. Finally, we discussed how to proceed in the matter -of the IETF webpush working group. There was consensus in that we should contact the WG and let them -know about our use cases and our work. - -=== TC RESOURCE - -A presentation on the resource schema work so far was followed by a discussion of resource schemas for -building management, etc. We need to look at ways to integrate or provide APIs for information relevant -to the calendaring and scheduling world. Information in the structured location draft as to how to provide it -so it is always available for users. The TC is now waiting on its drafts to begin progression at the IETF so -will be dormant unless an issue comes up that must be addressed by the TC. - -=== TC SHARING - -This TC was formed from the Contacts Sharing Provisional Committee following CalConnect XXX. The -TC presented a plan for the 4 specifications we'd like to release. There were lots of discussions around -semantics and general approach, such as: - -. Dropping UID from xml bodies -. CardDAV sharing collections. Is there only one sharee collection per sharer. -. Attaching principal information to notifications. -. Per-user and global properties for iCalendar. What should be the default? -. Requiring vCard 4. -. Sharing draft collections. - -No strong decisions have been made, will have to pick those up during the post-event TC calls going -forward. - -=== TC TASKS - -We discussed work done over the last few months: history/comments use cases, task assignment and -VPOLL, and changes to relationships draft. We had a detailed discussion on the use of RELATED-TO, -RELID/REFID, CATEGORIES. We decided we would use a URI value for REFID. We decided we needed -a new property for "formal" categories. We will continue to discuss the need for an event type registry. -Next up we will work on finishing the drafts, ongoing VPOLL work, and time planning. - -=== TC TIMEZONE - -No session was held at the conference. The TC is on hold pending the progression of its two drafts now -adopted as https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[TZDIST Working Group] -drafts in the IETF for progression to become RFCs: -https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[Time Zone Data Distribution Service] -and https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[CalDAV: Timezones by Reference]. - -=== Workshop on Groups Attendees and Sharing - -Reviewed proposals for server-side support. Attendees approach involved client-driven model, decided -right approach was for server to make decisions on expansions. Same would apply to sharing as well. Still -open questions as to how it would work, at this time decided to continue discussions within TC CALDAV -once it finishes current work, and discuss again at next conference either at another workshop or as part -of TC CALDAV. - -=== Workshop on History and Comments Streams in iCalendar Data - -Discussed general use cases; reached a general agreement on the need to address this in particular TC -TASKS has a requirement. Approaches using external feeds through existing protocols, links to photo -stream sites, etc.. The CONFERENCE property in EVENTPUB was driven by Google's interest in a PUT -to Google Hangout. Also discussed TC TASKS requirement by using VJOURNAL. Decision: we don't -have time before January to get into the topic in depth, and will return to it at the January event. In the -meantime, TC TASKS will evaluate whether VJOURNAl is sufficient for its needs and the requirement can -be met that way. - -== Plenary Decisions - -The offer from Gershon Janssen to host the Autumn 2015 event in Amsterdam, The Netherlands was -confirmed. - -A Planning Committee will be formed for CalConnect's Tenth Anniversary meeting, CalConnect XXXII, in -January 2015. - -== Future Events - -* CalConnect XXXII: January 26-30, 2015, Kerio Technologies, San Jose, California -* CalConnect XXXIII: Spring, 2015, TBD -* CalConnect XXXIV: Autumn, 2015, Gershon Janssen, Amsterdam, The Netherlands - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Conference (presentations, TC sessions, -BOFs, networking, Plenary) -* The format for European events is to move TC sessions to the afternoon and offer symposia and -BOFs during Thursday and Friday mornings, and continue through Friday afternoon. - -== Pictures from CalConnect XXXI - -.Photograph courtesy of Graham Wilson, www.grahamphotographer.co.uk -image::img01.png[] - -.The interoperability test event at http://www.thehigginsbedford.org.uk/[The Higgins], with attendent Sarcophagus -image::img02.png[] diff --git a/sources/csd-report-conference-32.adoc b/sources/csd-report-conference-32.adoc deleted file mode 100644 index 25c54e3..0000000 --- a/sources/csd-report-conference-32.adoc +++ /dev/null @@ -1,343 +0,0 @@ -= Report on CalConnect Conference XXXII, January 28-30, 2015 -:docnumber: 1501 -:copyright-year: 2015 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2015-02-18 -:published-date: 2015-02-18 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-32 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect Conference XXXII took place on January 28-30, 2015, hosted by Kerio -Technologies in San Jose, California. The CalConnect -Conference was attended by 37 people from 17 members, and two non-member observers. -The Conference also included our Tenth Anniversary -Celebration, which was held on Wednesday afternoon the 28th, with the regular -conference then on Thursday and Friday the 29th and 30th. The -Tenth Anniversary Celebration on Wednesday afternoon also attracted 12 additional -people who came only for the celebration. The Interoperability -Test Event was held immediately prior to the Conference on January 26-28, 2015, and -had 24 participants onsite from 13 members and 1 nonmember. -In total, 53 people from 20 organizations attended some portion of the week (not -counting organizations who came only for the -Celebration on Wednesday). - -At this Conference we also implemented our first effort at redesigning the CalConnect -Conference to provide sessions of broader interest. Instead -of our usual Technical Committee sessions, workshops and BOFs, several sessions on -broader topics and at a higher level were offered, with the -intent of providing more value to our participants. Some of the very detailed -discussions formerly part of a conference TC session were moved to -earlier in the week, during the Interoperability Test Event. The Conference finished -with the CalConnect Plenary Session on Friday afternoon. The -Conference agenda, with notes on the discussion topics, may be found at CalConnect -XXXII Schedule. - -== CalConnect Tenth Anniversary Celebration - -Wednesday afternoon was dedicated to our Tenth Anniversary Celebration; our first -real members' meeting was held in January of 2005 at the -University of Washington. We had a number of invited guests in addition to the -participants attending the regular CalConnect Conference. Special -session for the Celebration included the History of CalConnect; The Freebusy -Challenge; Calendaring as a Platform; and a panel discussion in the -Future of Calendaring, plus guest speakers Lisa Dusseault, the originator of CalDAV, -who spoke on committee standards development, and Steve -Allen from the University of California Lick Observatory, who spoke on "The Time -People Want", an exploration of the history and management of -time and time zones. More about the Tenth Anniversary Celebration may be found at -CalConnect Tenth Anniversary. - -== Documents since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications to become -internet draft submissions to the IETF and ultimately be progressed to become RFCs -(Proposed Standards), rather than be directly published by CalConnect itself. - -=== Published Documents - -* Report on CalConnect Conference XXXI in Bedford, United Kingdom -* Report on Interoperability Test Event XXXI - -=== CalConnect Drafts in IETF WG Last Call or AD Review - -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[Time Zone Data Distribution Service] -* https://datatracker.ietf.org/doc/draft-ietf-calext-rscale/[Non-Gregorian Recurrence Rules in iCalendar (RSCALE)] - -=== CalConnect Drafts Accepted by IETF Working Groups as WG Drafts - -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[CalDAV: Timezones by Reference] -* https://datatracker.ietf.org/doc/draft-daboo-calendar-availability/[Calendar Availability (VAVAILABILITY)] -* https://datatracker.ietf.org/doc/draft-daboo-icalendar-extensions/[New Properties for iCalendar] -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[CalDAV: Timezones by Reference] - -=== Updated Internet Drafts at IETF not yet Adopted by a Working Group - -* https://datatracker.ietf.org/doc/draft-douglass-ical-relations/[Improved Support for iCalendar Relations] -* https://datatracker.ietf.org/doc/draft-york-vpoll/[VPOLL: Consensus Scheduling Component for iCalendar] - -=== CalConnect Drafts Newly Submitted to the IETF - -* https://datatracker.ietf.org/doc/draft-apthorp-ical-tasks/[Task Extensions to iCalendar] -* https://datatracker.ietf.org/doc/draft-pot-webdav-notifications/[WebDAV User Notifications] -* https://datatracker.ietf.org/doc/draft-pot-webdav-resource-sharing/[WebDAV Resource Sharing] - -== Update on Technical Committee Work and Initiatives - -=== CALSCALE Ad Hoc - -The Ad Hoc is in abeyance while -https://datatracker.ietf.org/doc/draft-ietf-calext-rscale/[Non-Gregorian Recurrence Rules in iCalendar (RSCALE)] -completes progression through the IETF to become an -RFC; the document is undergoing AD Review prior to an IETF last call. The Ad Hoc will -disband when the document is accepted as a Proposed -Standard unless further work is identified. - -=== TC API - -TC API has been focused on developing generic calendaring API making it easy to -develop simple and more complex apps which access calendar -store via generic APIs. In addition to continuing with this work, TC API will sponsor -a discussion of creating a new activity to develop guidance for -developers and users of calendaring specifications, possibly including an iCalendar -data model, developers' guide for iCalendar or CalDAV, and so -forth. - -=== TC AUTODISCOVERY - -The TC has produced an initial draft of a mechanism for multiple service discovery -via a single protocol for client setup and submitted to the IETF: -https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery]. -The TC is now dormant waiting for an opportunity to move this forward at the IETF. -Some interoperability testing of -this specification occurred during the interoperability test event this week. - -=== TC CALDAV - -Work over last 4 months: - -* Scheduling Drafts - Worked designing on a mechanism for creating drafts of -scheduling objects which allows event/tasks to be created -without automatic scheduling operations being performed by the server until the -organizer "commits" the draft as ready for scheduling. The -current design is as follows: -** Drafts are stored as resources in calendar collections using a specific -DAV:resourcetype value (NOT in a single "drafts" collection) -** To create a draft: POST /;add-member - server returns location of created draft -** To "commit" a draft: POST //?action=create - server deletes the draft and adds a -new non-draft resource (it may use the same URI/UID -or a different one - location is returned) -** Open issue on how to specify draft DAV:resourcetype at creation time - three -possibilities: -... Use a query parameter on the POST URL, e.g. ?resourcetype=calendar-draft -... Use a header field in the POST request, e.g. DAV-resourcetype: calendar-draft -... Use a multipart media type for the POST body that combines PUT+PROPPATCH to do -atomic setting of WebDAV properties and -resource body all in one go, e.g. "multipart/webdav-resource" with the first part -being application/xml (WebDAV PROPPATCH -body) and the second part being the data for the resource body. -** A mechanism for creating drafts from existing events was discussed and tabled as -future work -* Server Information Document (Rich Capabilities) - Worked on designing a structured -resource to organize the DAV services and features -available on a server to replace the already bloated DAV response header field. The -current design is as follows: -** The resource will be an XML document containing elements describing one or more -"services", e.g. CalDAV, CardDAV, generic -WebDAV -** Each "service" element will contain elements describing one or more "features" of -that service, e.g. DAV level 1, calendar-access, -sharing, etc -** Open issue on how to list DAV features present in all services - two possibilities: -... List global "features" at the top of the XML document outside of any "services" -... List the global "features" inside a specially named "service", e.g. "*" -** A mechanism for including global/constant-valued DAV properties was discussed and -tabled as future work - -Work for the next four months: - -** How to handle visibility of drafts by non-draft-aware clients? Keep resource-type -as calendar? -** More ioptesting on managed attachments, especially attachments on recurrences -** Make managed attachments spec depend on server info document - probably requires -revisiting including global/static/constant -properties -** Move WebDAV Prefer through IETF -** Generate a client/server capability matrix for publication - -=== TC EVENTPUB - -The TC has been dormant as we wait for the backlog of drafts before the IETF to -clear. The current EVENTPUB drafts referenced above are -http://tools.ietf.org/html/draft-douglass-calendar-extension/[Event Publication Extensions to iCalendar] -and https://datatracker.ietf.org/doc/html/draft-daboo-icalendar-extensions[New Properties for iCalendar]. -Over the next few months the TC will be reactivated to consider -and develop a proposal to add QRCODES to Calendar URIs. - -=== TC FREEBUSY - -The TC has been working on the VPOLL specification: -https://tools.ietf.org/html/draft-york-vpoll-00[VPOLL: Consensus Scheduling Component for iCalendar]. The major change was the -introduction of a VVOTER component to carry more complex information about voters and -their choices, driven by the need to provide more -information for task assignment - e.g. cost, expected time, possible start times etc. -Over the next few months the TC will plan for -interoperability testing on how non-aware VPOLL clients handle VPOLL in a collection - -=== TC FSC - -TC FSC (Federated Shared Calendars) has been working on the invitation flow for -shared calendars and published calendars (e.g. enhanced -webcal) and will continue its work in this area. It is jointly working with TC -SHARING to resolve ambiguities in how invitations are managed -and sharing is handled in different circumstances. - -=== TC IOPTEST - -Conducted general CalDAV and CardDAV testing. Some testing started of CalDAV PUSH and -sharing. Much iMIP testing as Microsoft -participated in the test event. During the Interop, breakout sessions were held on -iMIP, PUSH, and QRCOCDES and the URI. A new -specification for the iMIP header will be developed and submitted to the IETF. The -event report may be found at -https://www.calconnect.org/events/event-reports#ioptestevents[CalConnect Interoperability Test Event Reports] once completed. - -=== TC ISCHEDULE - -iSchedule was dormant over the last four months but will be reactivated after this -conference. Its work for the next 4 months will be: - -* Define iSchedule: URL scheme (in lieu of mailto or other schemes) -* Postpone "identity crisis" issue for the time being -* Determine if we need a form of redirect/forward in the base iSchedule specification -* Get the current draft with these changes adopted as an IETF working group draft - -=== TC PUSH - -The TC has developed a first version of a push protocol. It provides methods to -subscribe to topics and to deliver push messages to a new -entity called push-gateway. The push gateway acts as an adapter to the actual push -delivery service and provides a standardized interface to -the application server. The TC also specified an extension to WebDAV to provide a way -for the client to discover supported push-gateways, -to discover push topics and to subscribe to topics and select a specific gateway. At -this time there is an initial implementation of a pushgateway -as well as server side and client side implementations. - -Work for next 4 months: - -* Finish the initial specs -* Get more clients & servers to implement the draft -* Plan for more Interop testing at the next event - -=== TC RESOURCE - -TC RESOURCE is dormant, waiting on its drafts to begin progression at the IETF. - -=== TC SHARING - -The base specifications for webdav resource sharing and webdav notifications have -been published to the IETF: -https://tools.ietf.org/doc/html/draft-pot-webdav-resource-sharing[WebDAV Resource Sharing] -and WebDAV Notifications. Work will now begin on CalDAV Calendar Sharing and CardDAV -Address Book Sharing. The calendar sharing -specification should be relatively straight-forward. Some unanswered questions remain -regarding address book sharing of Collections vs. -Groups. Will address private events in CalDAV sharing. - -Work for next 4 months: - -* Finish up CalDAV sharing -* Start CardDAV sharing - -=== TC TASKS - -Over the last four months the TC completed work on two specifications. The Tasks -Extensions draft was submitted to the IETF as an Internet -Draft; iCalendar Relationships was updated at the IETF to reflect the work of the TC. -The Task Extensions draft defines the actual -enhancements to VTODOs that are the primary goal of the TC. - -* https://datatracker.ietf.org/doc/draft-apthorp-ical-tasks/[Task Extensions to iCalendar] -* https://datatracker.ietf.org/doc/draft-douglass-ical-relations/[Improved Support for iCalendar Relations] - -Work for next 4 months: - -* Clarify issues with URI vs ID tokens -* Task recurrences? Regeneration? -* Time sensitive tasks? -* Interop planning - -=== TC TIMEZONE - -The TC is on hold pending the progression of its two drafts at the IETF via the -https://datatracker.ietf.org/doc/charter-ietf-tzdist/[TZDIST Working Group]: -https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[Time Zone Data Distribution Service] -and https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[CalDAV: Timezones by Reference]. -The Time Zone Data Distribution Service draft is now in working group last call; the -Time Zones by -Reference draft has been accepted as a working group draft. - -== Plenary Decisions - -== Future Events - -* CalConnect XXXIII: May 18-22, 2015, 1and1, Bucharest, Romania -* CalConnect XXXIV: September 28 - October 2, 2015, Gershon Janssen, Amsterdam, The -Netherlands -* CalConnect XXXV: January 25-29, 2016, AOL, Palo Alto, California - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Conference (presentations, TC -sessions, BOFs, networking, Plenary) -* The format for European events is to move TC sessions to the afternoon, offer -symposia and BOFs during Thursday and Friday mornings, -and continue through Friday afternoon. - -== Pictures from CalConnect XXXII - -.The Interoperability Testing at Kerio Technologies HQ -image::img01.png[] - -.CalConnect XXXII Conference Opening at the De Anza Hotel -image::img02.png[] - -.Facilitating a group discussion at CalConnect XXXII -image::img03.png[] diff --git a/sources/csd-report-conference-33.adoc b/sources/csd-report-conference-33.adoc deleted file mode 100644 index e73b216..0000000 --- a/sources/csd-report-conference-33.adoc +++ /dev/null @@ -1,287 +0,0 @@ -= Report on CalConnect Conference XXXIII, May 20-22, 2015 -:docnumber: 1503 -:copyright-year: 2015 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2015-02-18 -:published-date: 2015-02-18 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-33 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect Conference XXXIII took place on May 20-22, 2015, hosted by 1&1 in Buchares, Romania. -The CalConnect Conference was -attended by 21 people from 9 members, and two non-member observers. The Interoperability Test -Event was held immediately prior to the -Conference on May 18-20, 2015, and had 12 participants onsite from 6 members, respectable -attendance numbers for our first event in -eastern Europe. - -At this Conference we again used our redesigned CalConnect Conference format, originally tried at -the January 2015 Conference, to provide -sessions of broader interest. Instead of our usual Technical Committee sessions, workshops and -BOFs, several sessions on broader topics -and at a higher level were offered, with the intent of providing more value to our participants. -Some of the very detailed discussions formerly -part of a conference TC session were moved to earlier in the week, during the Interoperability -Test Event. The Conference finished with the -CalConnect Plenary Session on Friday afternoon. The Conference agenda, with notes on the -discussion topics, may be found at CalConnect -XXXIII Schedule. - -== Documents since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications to become internet draft -submissions to the IETF and -ultimately be progressed to become RFCs -(Proposed Standards), rather than be directly published by CalConnect itself. - -=== Published Documents - -* Report on CalConnect Conference XXXII in San Jose, California -* Report on Interoperability Test Event XXXII - -=== CalConnect Drafts Published as RFCs by the IETF - -* RFC 7529, https://tools.ietf.org/doc/html/rfc7529[Non-Gregorian Recurrence Rules in iCalendar (RSCALE)]. - -=== CalConnect Drafts in IETF Last Call or AD Review - -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-service/[Time Zone Data Distribution Service] -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[CalDAV: Timezones by Reference] - -=== CalConnect Drafts Accepted by IETF Working Groups as WG Drafts - -* https://datatracker.ietf.org/doc/draft-daboo-calendar-availability/[Calendar Availability (VAVAILABILITY)] -* https://datatracker.ietf.org/doc/draft-daboo-icalendar-extensions/[New Properties for iCalendar] - -=== Updated Internet Drafts at IETF not yet Adopted by a Working Group - -* https://datatracker.ietf.org/doc/draft-douglass-ical-relations/[Improved Support for iCalendar Relations] -* https://datatracker.ietf.org/doc/draft-york-vpoll/[VPOLL: Consensus Scheduling Component for iCalendar] - -=== CalConnect Drafts Newly Submitted to the IETF - -* https://datatracker.ietf.org/doc/draft-douglass-server-info/[DAV Server Information Object] -* https://datatracker.ietf.org/doc/draft-apthorp-ical-tasks/[Task Extensions to iCalendar] -* https://datatracker.ietf.org/doc/draft-pot-webdav-notifications/[WebDAV User Notifications] -* https://datatracker.ietf.org/doc/draft-pot-webdav-resource-sharing/[WebDAV Resource Sharing] - -== Update on Technical Committee Work and Initiatives - -=== CALSCALE Ad Hoc - -The Ad Hoc was closed upon the publication of RFC 7529, -https://datatracker.ietf.org/doc/draft-ietf-calext-rscale/[Non-Gregorian Recurrence Rules in iCalendar (RSCALE)] - -=== TC API - -TC API spun off its data model discussion to TC DEVGUIDE. Much of the discussion has been on -simplified JSON data formats and -benefits/issues with REST APIs, and the need for a media type that defines a JSON document that -describes collection contents. Going -forward the TC will focus on mapping WebDAV multistatus to a JSON data format with its own media type. - -=== TC AUTODISCOVERY - -The TC has produced an initial draft of a mechanism for multiple service discovery via a single -protocol for client setup and submitted to the -IETF: https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery]. -The protocol has been implemented in at least one server and one client. The TC is now dormant -waiting for an opportunity to move this forward at the IETF. - -=== TC CALDAV - -Work over last 4 months: - -Shelved calendar resource drafts until/unless we see more client interest. We will refactor -Managed Attachments to use Server Info -Document once it stabilizes. Focused primarily on Server Info Document which now has an initial -draft: https://datatracker.ietf.org/doc/draft-douglass-server-info/[draft-douglass-server-info]. - -* Decisions: -** Initial spec will probably punt on including per-service DAV properties/values -** Define a Server-Info-Token response header that servers can use to notify clients of a change -to server capabilities (rather than relying on clients to poll) -** Need a way for clients to specifically request that the server return Server-Info-Token -response header - currently If-Not-Server-Info-Token request header -* Open Issues: -** Should we use Server-Info-Token as both a request and response header or use a -If-Not-Server-Info-Token request header as in current draft? -Should we include "features" that are currently only discoverable via DAV properties, e.g. -sync-collection, add-member, current-user-principal -** Should we include a Link header with server-info-href and newly defined reltype in OPTIONS -responses? Some investigation into -a small number of clients yields that clients typically do a PROPFIND on .well-known before ever -doing an OPTIONS, so a client -could fetch server-info-href property in initial PROPFIND and potentially bypass OPTIONS completely -** Should server-info-href be available on ALL resources or limited to just a sub-set of resources -(e.g. .well-known, calendar-homeset, user principals) - -Work for next 4 months: - -Finish up the serverinfo document. Work on a public version of the CalDAV server matrix. Plan on a -client version of the matrix. - -=== TC DEVGUIDE - -The TC was established as a spin-off from TC API. Over the last four months it has had initial -discussions on topics that need to be covered -in the Developer's Guide. Over the next four months we will pick three high level topics and -create a detailed description of each. Additionally -alternative publication means such as github will be evaluated. - -=== TC EVENTPUB - -The TC became active to work on using QRCODE and data-uris to distribute events without the need -for network connections. An initial draft -was created for discussion. Over the next four months the TC will continue with the QRCODE work -and clarify the use case for embedded -data. Additionally a decision must be made as to whether a new URI scheme is the best way forward. - -=== TC FREEBUSY - -The TC has been working on the VPOLL specification: -https://tools.ietf.org/html/draft-york-vpoll-00[VPOLL: Consensus Scheduling Component for iCalendar]. The basic specification is -mostly complete and the TC started work on other poll-modes such as task assignment and signup -mode. Task assignment would be -associated with project management. Signup would, for example, allow a simple signup to (probably -social) events, perhaps indicating what the signee would bring to the event. - -Over the next four months the TC will continue work on defining the sign-up poll mode and work on -restructuring the draft. - -=== TC FSC - -TC FSC (Federated Shared Calendars) has been working on the invitation flow for shared calendars -and published calendars (e.g. enhanced -webcal) and will continue its work in this area, and has run into some issues on how to deliver -the invites over a secure connection without reinventing iSchedule. - -Over the next four months the TC will mock up the invitation flow and upgrade process, make more -progress on authentication flows, and -plan for interop testing. It is jointly working with TC SHARING to resolve ambiguities in how -invitations are managed and sharing is handled in different circumstances. - -=== TC IOPTEST - -The TC planned for and conducted the interop testing event at CalConnect XXXIII, reported on at -https://www.calconnect.org/events/event-reports#ioptestevents[CalConnect Interoperability Test Event Reports] -Reports once completed. The TC will now begin planning for the testing at CalConnect XXXIV this autumn. - -=== TC ISCHEDULE - -TC ISCHEDULE discussed the relationship to TC FSC and whether the DKIM model used in iSchedule -migth be applicable to TC FSC, or -whether a different security model could be used for both FSC and iSchedule. Over the nexgt four -months, the TC will wait for the IETF -TZDIST working group to conclude, then update the iSchedule draft to use the scheduleto: URI -scheme and start encouraging the IETF to -initiate a working group to take the iSchedule draft forward. - -=== TC PUSH - -The TC has finished an initial specification of the Push Discovery and Push NOtificaiton Dispatch -Protocol, thought the draft still requires -updating. Members have implemented the application server portion, Push Gateways, and a client -that supports Push on Android. Over the -next four months the TC will continue to work on the spec. - -=== TC RESOURCE - -TC RESOURCE is dormant, waiting on its drafts to begin progression at the IETF. - -=== TC SHARING - -The base specifications for webdav resource sharing and webdav notifications have been published to the IETF: -https://tools.ietf.org/doc/html/draft-pot-webdav-resource-sharing[WebDAV Resource Sharing] -and WebDAV Notifications. CalDAV sharing is almost complete. Over the next four months the TC will -continue to wor on the CalDAV sharing spec and continue discussions of contacts sharing. - -=== TC TASKS - -Over the last four months the TC looked into what is necessary to get client support for the new -properties, etc. A thorough review was -completed of all thenew items that might need to be included in interop testing. The TC also -reviewed time tracking aplications, and decided -the first step would be a new duration property to allow a record of time spent on a task. Also -looked at various ways task assignment is -being done, and how overdue tasks might be presented to users. - -Over the next four months the TC will work on an event type taxonomy and continue working on tests -for the new drafts. - -* https://datatracker.ietf.org/doc/draft-apthorp-ical-tasks/[Task Extensions to iCalendar] -* https://datatracker.ietf.org/doc/draft-douglass-ical-relations/[Improved Support for iCalendar Relations] - -=== TC TIMEZONE - -The TC is on hold pending the progression of its two drafts at the IETF via the https://datatracker.ietf.org/doc/charter-ietf-tzdist/[TZDIST Working Group]: -https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[Time Zone Data Distribution Service] -and https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref/[CalDAV: Timezones by Reference]. -The Time Zone Data Distribution Service draft is now in last call, and the Time Zones by Reference -draft has completed working group last call. - -== Plenary Decisions - -== Future Events - -* CalConnect XXXIV: September 28 - October 2, 2015, Gershon Janssen, Amsterdam, The Netherlands -* CalConnect XXXV: January 25-29, 2016, AOL, Palo Alto, California -* CalConnect XXXVI: Spring 2015, TBA - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Conference (presentations, TC sessions, -BOFs, networking, Plenary) -* The format for European events is to move TC sessions to the afternoon, offer symposia and BOFs -during Thursday and Friday mornings, and continue through Friday afternoon. - -== Pictures from CalConnect XXXIII - -.The Skytower in Bucharest; CalConnect was on the 34th floor -image::img01.png[] - -.View from the 34th floor of the Skytower -image::img02.png[] - -.CalConnect XXXIII Conference -image::img03.png[] - -.The Conference dinner at Caru' cu bere -image::img04.png[] diff --git a/sources/csd-report-conference-34.adoc b/sources/csd-report-conference-34.adoc deleted file mode 100644 index 5828f19..0000000 --- a/sources/csd-report-conference-34.adoc +++ /dev/null @@ -1,228 +0,0 @@ -= Report on CalConnect Conference XXXIV, September 30 - October 2, 2015 -:docnumber: 1506 -:copyright-year: 2015 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2015-10-23 -:published-date: 2015-10-23 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-34 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect Conference XXXIV took place on September 30 - October 2, 2015, hosted by Gershon -Janssen in Amsterdam, The Netherlands. -The CalConnect Conference was attended by 30 people from 17 members and one non-member observer. -The Interoperability Test Event -was held immediately prior to the Conference on September 28-30, 2015, and had 13 participants -onsite from 10 members. - -At this Conference we again used our redesigned CalConnect Conference format, originally tried at -the January 2015 Conference, to provide -sessions of broader interest. Instead of our usual Technical Committee sessions, workshops and -BOFs, several sessions on broader topics -and at a higher level were offered, with the intent of providing more value to our participants. -Some of the very detailed discussions formerly -part of a conference TC session were moved to earlier in the week, during the Interoperability -Test Event. The Conference finished with the -CalConnect Plenary Session on Friday afternoon. The Conference agenda, with notes on the -discussion topics, may be found at CalConnect XXXIV Schedule. - -== Documents since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications to become internet draft -submissions to the IETF and ultimately be progressed to become RFCs -(Proposed Standards), rather than be directly published by CalConnect itself. - -=== Published Documents - -* Report on CalConnect Conference XXXIII in Bucharest, Romania -* Report on Interoperability Test Event XXXIII - -=== CalConnect Drafts Published as RFCs by the IETF - -* RFC 7529, https://tools.ietf.org/doc/html/rfc7529[Non-Gregorian Recurrence Rules in iCalendar (RSCALE)]. - -=== CalConnect Drafts in IETF Editor Queue to be Published as RFCs - -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-service/[Time Zone Data Distribution Service] -* https://datatracker.ietf.org/doc/draft-ietf-tzdist-caldav-timezone-ref//[CalDAV: Timezones by Reference] - -=== CalConnect Drafts in Progress at IETF Working Groups - -* https://datatracker.ietf.org/doc/draft-ietf-calext-availability/[Calendar Availability (VAVAILABILITY)] -* https://datatracker.ietf.org/doc/draft-ietf-calext-extensions/[New Properties for iCalendar] - -=== Updated CalConnect Drafts Pending Adoption by IETF Working Groups - -* https://datatracker.ietf.org/doc/draft-douglass-server-info/[DAV Server Information Object] -* https://datatracker.ietf.org/doc/draft-apthorp-ical-tasks/[Task Extensions to iCalendar] - -NOTE: Please note that CalConnect documents at the IETF are mentioned only if their status has -changed or they have been updated since the last CalConnect event - -== Update on Technical Committee Work and Initiatives - -=== TC API - -Discussed various API formats and attempted to come to an agreement on how a such API would look. -The group is split on using a slightly -more stream based API like JMAP and using a REST based API. Possible formats for the data exchange -are JMAP and HAL among others. -Now comparing various data formats already in use (Caligrah vs JMAP vs iCalendar vs Microsoft) to -detect similarities. During the next -period the TC will develop the "simple" JSON data model specification and look at models for -scheduling and recurrences. - -=== TC CALDAV - -Focused mainly on server-info-document -https://datatracker.ietf.org/doc/draft-douglass-server-info/[DAV Server Information Object] -and we seem to be getting close to something that is fully baked. -Format has been solid for a while. We now have a mechanism for the client to detect a change in -the server-info-token via HTTP responses. -Ken has uploaded his server capabilities spreadsheet for our GitHub repository as a staring point -for accumulating this info from our -members/vendors. During the next months the server-info document will be finalized. The TC will -work on the server/client features matrix -and integration with DEVGUIDE. The icalendar-patch draft will be reviewed. - -=== TC DEVGUIDE - -Talked about the format of the guide, agreed on using gollum wiki and set it up with the new -CalConnect github account. Some initial content -has been added. During the next months the TC will work on "examples" content, formatting and -layout, and X-properties descriptions. - -=== TC EVENTPUB - -The TC completed work on the QRCODE/Data URI proposal and a draft specification is being -developed, to be submitted to the IETF when ready. - -=== TC FREEBUSY - -Mostly on hold as we try to get other specifications through the IETF. VAVAILABILITY is ready and -VPOLL needs more work but is -implementable, much interest from the SmartGrid and from LegalXML. Had some discussions on other -poll modes, in particular signup (for social calendaring). Task assignment is also on the list. - -=== TC FSC - -TC FSC (Federated Shared Calendars) reviewed the invite process taking into consideration that -federated sharing involves not just -calendars but at least contacts and possibly more. The issue of security is becoming more -important and there is more interest in end-to-end -signing and encryption. This obviously has implications for server side services that need access -to the content to function - for example -scheduling and alarms. The issue of key escrow was raised - in some circumstances (companies and -their employees) it is a requirement -that the employer has a copy of the keys. This would allow encryption services to run with server -side decryption. Planning to hold joint calls -with TC ISCHEDULE as we are talkking about some of the same issues. - -=== TC IOPTEST - -The TC planned for and conducted the interop testing event at CalConnect XXXIV, reported on at -https://www.calconnect.org/events/event-reports#ioptestevents[CalConnect Interoperability Test Event Reports]. -The TC will now begin planning for the testing at CalConnect XXXV in January. - -=== TC ISCHEDULE - -TC ISCHEDULE is waiting for the IETF TZDIST working group to conclude, then propose rechartering -it to deal with the iSchedule draft. Joint -calls between TC ISCHEDULE and TC FSC will be initiated as the two TCs are dealing with some of -the same issues. - -=== TC PUSH - -We clarified a few open issues with the protocol and discussed how to proceed with the submission -to the IETF. The TC is also waiting for more implementations to begin more extensive testing. - -=== TC RESOURCE - -TC RESOURCE is dormant, waiting on its drafts to begin progression at the IETF. - -=== TC SHARING - -The base specifications for webdav resource sharing and webdav notifications have been published to the IETF: https://tools.ietf.org/doc/html/draft-pot-webdav-resource-sharing[WebDAV Resource Sharing] -and -https://tools.ietf.org/html/draft-pot-webdav-notifications[WebDAV Notifications]. -The TC has been working on getting an implementation ready to go, and the first two specs have -been partially -implemented. Working through this allowed us to find a number of issues with the spec, so we've -published new drafts. We added a -{DAV:}share-mode property and removed the {DAV:}resourcetype semantics. - -=== TC TASKS - -The Task Extensions draft has been updated, and the TC is looking at some form of tasks taxonomy. - -* https://datatracker.ietf.org/doc/draft-apthorp-ical-tasks/[Task Extensions to iCalendar] -* https://datatracker.ietf.org/doc/draft-douglass-ical-relations/[Improved Support for iCalendar Relations] - -=== TC TIMEZONE - -The TC is on hold pending the progression of its two drafts at the IETF, both of which have -completed IETF Last Call and are now in the -Editor Queue pending publications as RFCs. The TC will reactivate to discuss the promotion of the -Timezone Data Distribution Service and its incorporation into production systems. - -== Future Events - -* CalConnect XXXV: January 25-29, 2016, AOL, Palo Alto, California -* CalConnect XXXVI: April 18-22, 2016, Ribose/OGCIO, Hong Kong - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Conference (presentations, TC sessions, -BOFs, networking, Plenary) -* The format for European events is to move TC sessions to the afternoon, offer symposia and BOFs -during Thursday and Friday mornings, and continue through Friday afternoon. - -== Pictures from CalConnect XXXIV - -.The Rosarium in Amsterdam, venue for CalConnect XXXIV -image::img01.png[] - -.Just prior to opening CalConnect XXXIV on Wednesday -image::img02.png[] - -.TC DEVGUIDE presentation at CalConnect XXXIV -image::img03.png[] - -.Panel discussion Wednesday afternoon at CalConnect XXIV -image::img04.png[] diff --git a/sources/csd-report-conference-35.adoc b/sources/csd-report-conference-35.adoc deleted file mode 100644 index 01ecbf6..0000000 --- a/sources/csd-report-conference-35.adoc +++ /dev/null @@ -1,199 +0,0 @@ -= Report on CalConnect Conference XXXV, January 11-15, 2016 -:docnumber: 1601 -:copyright-year: 2016 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2016-02-03 -:published-date: 2016-02-03 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-35 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect Conference XXXV took place on January 13-15, 2016, hosted by AOL in -Palo Alto, California. The CalConnect Conference was attended by 21 people from 12 -members and one non-member observer. The Interoperability Test Event was held -immediately prior to the Conference on January 11-13, 2016\5, and had 9 participants -onsite from 6 members. - -The CalConnect Conference focused on sessions on strategic and possible work items -more than ongoing work, in accordance with our new format, and finished with the -CalConnect Plenary Session on Friday afternoon. The Conference agenda, with notes -on the discussion topics, may be found at CalConnect XXXV Schedule. - -== Status of documents since last conference - -Much of the ongoing work in CalConnect is focused on specifications to become -internet draft submissions to the IETF and ultimately be progressed to become RFCs -(Proposed Standards), rather than be directly published by CalConnect itself. - -=== Published Documents - -* Report on CalConnect Conference XXXIV in Amsterdam, The Netherlands -* Report on Interoperability Test Event XXXIV - -=== CalConnect Drafts in IETF Editor Queue to be Published as RFCs - -* Time Zone Data Distribution Service -* CalDAV: Timezones by Reference - -=== CalConnect Drafts in Progress at IETF Working Groups - -* https://datatracker.ietf.org/doc/draft-ietf-calext-availability/[Calendar Availability (VAVAILABILITY)] -* New Properties for iCalendar - -=== CalConnect Drafts Pending Adoption by IETF Working Groups - -* DAV Server Information Object -* Task Extensions to iCalendar - -=== New and Updated CalConnect Drafts Submitted to the IETF - -* https://tools.ietf.org/html/draft-menderico-v-event-uri-00[v-event URI: An URI scheme for events] -* https://www.apple.com/[WebDAV: User Notifications] -* https://tools.ietf.org/html/draft-pot-webdav-resource-sharing-03[WebDAV Resource Sharing] -* https://tools.ietf.org/html/draft-pot-caldav-sharing-00[CalDAV Calendar Sharing] - -== Technical Committee Work and Initiatives Going Forward - -=== TC API - -Work for Calconnect XXXVI includes an overall event object model and a new -"participant" model. Locations and alarms will be reviewed again. The goal is a public -release of the event model at CalConnect XXXVI. - -=== TC AUTODISCOVERY - -Dormant pending progression of documents - -=== TC CALDAV - -* Move forward with iCalendar patch, focusing on "VPATCH" format rather than pathbased -format. Want to be able to use same format for all of patch/diff/compact use -cases. -* Write an I-D for new STRUCTURED-DATA iCalendar property -* Take direction from TC-API on how to implement multiple ORGANIZERs in iCalendar -* Work on private/protected/public properties - -=== TC DEVGUIDE - -* Create code examples to go along with Simple Event page -* Aim to publish a public version of the DEVGUIDE at CalConnect XXXVI and announce -the developer wiki -* See if the wiki can be hosted on the new CalConnect site -* Annotated version of RFC 5545 (iCalendar) - -=== TC EVENTPUB - -Rough consensus for CalConnect to create github-based schema set. Have concrete -set of categories to move forward with by next conference. Perhaps promote this for -CalConnect XXXVI and announce on CalDeveloper list. - -=== TC FREEBUSY - -Dormant - -=== TC FSC - -Define protocol for sharing (read-only and read-write) a single CalDAV calendar via an -"opaque" URL. - -=== TC IOPTEST - -Planning for CalConnect XXXVI. - -=== TC ISCHEDULE - -* Refresh current iSchedule draft as-is, punting on identity crisis and focusing on -enterprise-to-enterprise use -* Focus on improving iMIP - maybe in a new TC - -=== TC PUSH - -Dormant pending draft progression; interop testing ongoing - -=== TC RESOURCE - -Dormant pending draft progression at IETF - -=== TC SHARING - -* Determine what to do about scheduling/sharing interaction for caldav sharing -* Write a doc explaining differences between new sharing and Apple sharing and how to -be compatible with both -* Look again at contacts sharing - -=== TC TASKS - -Dormant pending draft progression at IETF - -=== TC TIMEZONE - -Dormant pending publication of drafts as RFCs. The TC may reactivate thereafter to -consider promotion of implementations of the TZ data distribution service. - -== Plenary Decisions - -TC IMIP will be established to pursue improving interoperability with iMIP and -enhancing the user experience, as extending iSchedule for general usage has proven -improbable due to the "identity crisis". - -== Future Events - -* CalConnect XXXVI: April 18-22, 2016, Ribose/OGCIO, Hong Kong -* CalConnect XXXVII: September 12-16 2016, SmoothSync, Dresden, Germany -* CalConnect XXXVIII: Winter 2017 TBD -* CalConnect XXXIX: May 2017, Tandem, Seattle, Washington - -The general format of the CalConnect Week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Conference (presentations, TC -sessions, BOFs, networking, Plenary) - -== Pictures from CalConnect XXXV - -[%unnumbered,cols="a,a"] -|=== -| [%unnumbered] -image::img01.png[] -| [%unnumbered] -image::img02.png[] -| [%unnumbered] -image::img03.png[] -| [%unnumbered] -image::img04.png[] -|=== diff --git a/sources/csd-report-conference-36.adoc b/sources/csd-report-conference-36.adoc deleted file mode 100644 index 3592e4f..0000000 --- a/sources/csd-report-conference-36.adoc +++ /dev/null @@ -1,238 +0,0 @@ -= Report on CalConnect Conference XXXVI, April 21-22, 2016 -:docnumber: 1603 -:copyright-year: 2016 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2016-05-11 -:published-date: 2016-05-11 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-36 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XXXVI took place on April 18-22, 2016, hosted by Ribose and OGCIO in Hong Kong, -as part of a larger event, the Hong Kong 2016 ITFEST. In addition to our regular conference -and test event, we held a seminar at Hong Kong University, and a Public Day at the -Hong Kong Convention Center on Wednesday. The CalConnect Test Event (Monday and -Tuesday) and Conference (Thursday and Friday) were held at the Cyberport, about 20 -minutes from central Hong Kong. - -The CalConnect Conference was attended by 22 people from 15 members, plus 7 -observers. The Test Event was held on April 18-19, 2016, and had 13 participants from -9 members, plus 2 observers. - -The Conference focussed on strategic and possible work items more than ongoing work, -in accordance with our new format, and finished with the CalConnect Plenary Session -on Friday afternoon. The Conference agenda with notes on the discussion topics may be -found at CalConnect XXXVI Conference Schedule. - -== Status of documents since last conference - -Much of the ongoing work in CalConnect is focused on specifications to become -internet draft submissions to the IEETF and ultimately be progressed to publication -as RFCs (Proposed Standards), rather than directly published by CalConnect itself. - -=== Published Documents -* Report on CalConnect Conference XXXV in Palo Alto, California -* Report on Interoperability Test Event XXXV - -=== CalConnect Specifications Published as RFCs -* RFC 7808 Time Zone Data Distribution Service -* RFC 7809 CalDAV: Time Zones By Reference - -=== CalConnect Drafts completed IETF WG Last Call -* New Properties for iCalendar -* Calendar Availability (VAVAILABILITY) - -=== New and Updated CalConnect Drafts at the IETF -* v-event URI: A URI scheme for events -* WebDAV User Notifications -* WebDAV Resource Sharing -* CalCOnnect Calendar Sharing - -== Technical Committee Work and Initiatives Going Forward - -=== TC API - -Working on a new key/value based data model. Much of the work is done and the -remainder will continue. - -=== TC AUTODISCOVERY - -Will be reactivated to consider authorization issues. - -=== TC CALDAV - -* Created initial draft of STRUCTURED-DATA iCalendar property - allows schema-based -data to be included with an event/task - -* Created rough draft for scoped attendee parameters - allows control of which -parameter(s) are sent in scheduling messages - initial draft in progress - -* Working on iCalendar-based patch/diff format - initial draft in progress - -=== TC DEVGUIDE - -Basic content for a single event is complete along with some other material. -DEVGUIDE has been styled to fit with he CalConnect web site in appearance. - -=== TC EVENTPUB - -Reviewed DMOZ directory service as source of categorization but it doesn't provide -all the needed info. Will continue with editing approach of providing a web service -to search and retrieve categories, but not invent something ourselves. - -=== TC FREEBUSY - -Dormant - -=== TC FSC - -To be merged into TC SHARING. - -=== TC IMIP - -Investigating how/why particular MIME formats are used by vendors, in particular -application/ics content-type. - -=== TC IOPTEST - -Conducted Interoperability Testing at CalConnect XXXVI. Looking at rebranding the -test event as Developer's Forum. - -=== TC ISCHEDULE - -Dormant. Specification is essentially complete but pending on other specs at the IETF -which have a higher priority. - -=== TC PUSH - -Draft to be published to the IETF after CalConnect XXXVI. - -=== TC RESOURCE - -Dormant - -=== TC SHARING - -Specifications completed over the last few weeks. Need to get some implementations -and do some testing. New CalDAV tester tests would help. TC-Sharing will take on the -work of coming up with a subscription model. How to upgrade subscriptions to -something more efficient than periodic polling of an ics file. - -=== TC TASKS - -Dormant - -=== TC TIMEZONE - -RFCs 7808 and 7809 published. Closed by decision of CalConnect Plenary XXXVI. - -== Special Events - -On Tuesday evening, CalConnect offered a 2-hour seminar at Hong Kong University. On -Wednesday, CalConnect held an all-day Public Day as part of the Hong Kong 2016 -ITFEST, at the Hong Kong Convention Centre. More about these events may be found at -https://www.calconnect.org/events/calconnect-public-day-hong-kong-it-fest[Public Day] -and https://www.calconnect.org/events/calconnect-seminar-hong-kong-university[Seminar]. - -== Plenary Decisions - -* Developer's Guide announcement to be done after How to Contribute and Introduction -sections added - -* Rebrand Interoperability Test Event as Developer's Forum to reflect model of both -testing and in-depth technical discussions - -* Close TC TIMEZONE - -* Provisional Committees PC QR (QRCODE include vCard info) and PC SEC (Security and -Encryption) established, to report out at CalConnect XXXVII - -* TC AUTODISCOVERY will be reactivated - -== Future Events - -* CalConnect XXXVII: September 12-16, 2016 - dmfs, Dresden, Germany -* CalConnect XXXVIII: February 13-17, 2017 - University of California, Irvine, -California -* CalConnect XXXIX: May 2017 - Tandem, Seattle, Washington -* CalConnect XXXX - Autumn 2017 - TBD - -The general format of the CalConnect Week is: - -* Monday morning through Wednesday noon, Developer's Forum (testing, tech discussions) -* Wednesday noon through Friday afternoon, Conference - -== Pictures from CalConnect XXXVI - -Pictures courtesy of Thomas Schäfer, 1&1 - -[%unnumbered,cols="a,a"] -|=== - -2+| [%unnumbered] -.Cyberport -==== -[%unnumbered] -image::DSCN1245-19.jpg[width=20%] - -[%unnumbered] -image::DSCN1312-21.jpg[width=20%] - -[%unnumbered] -image::DSCN1316-15.jpg[width=22%] - -[%unnumbered] -image::20160418_185556-17.jpg[width=25%] -==== -2+| [%unnumbered] -.Public Day -==== -[%unnumbered] -image::DSCN1273-23.jpg[width=20%] - -[%unnumbered] -image::20160420_141647-25.jpg[width=20%] -==== -| [%unnumbered] -.Conference Dinner -image::20160421_205610-27.jpg[width=18%] -| [%unnumbered] -.Saturday Tour -image::IMG_7980-29.jpg[width=18%] - -|=== diff --git a/sources/csd-report-conference-37.adoc b/sources/csd-report-conference-37.adoc deleted file mode 100644 index 098e1cc..0000000 --- a/sources/csd-report-conference-37.adoc +++ /dev/null @@ -1,220 +0,0 @@ -= Report on CalConnect Conference XXXVII, September 14-16, 2016 -:docnumber: 1605 -:copyright-year: 2016 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2016-09-30 -:published-date: 2016-09-30 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-37 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XXXVII took place on September 14-16, 2016, hosted by dmfs in Dresden, Germany. The -CalConnect Test Event (Monday, Tuesday, and Wednesday morning) and Conference (Wednesday -afternoon, Thursday and Friday) were held at Schloss Eckberg on the Elbe River. - -The CalConnect Conference was attended by 22 people from 10 members, plus 3 observers and a -representative from the IETF. The Test Event had 12 participants from 7 members. - -The Conference focussed on strategic and possible work items in addition to ongoing work, and -finished with the CalConnect Plenary Session on Friday afternoon. The Conference agenda with notes -on the discussion topics may be found at -https://www.calconnect.org/events/calconnect-xxxvii-september-12-16-2016#conference-schedule[CalConnect XXXVII Conference Schedule]. - -== Status of Documents since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications to become internet draft -submissions to the IETF and ultimately be progressed to publication as RFCs (Proposed Standards), -rather than directly published by CalConnect itself. - -=== Published Documents - -* Report on CalConnect Conference XXXVI in Hong Kong -* Report on Interoperability Test Event XXXVI - -=== CalConnect Specifications Published as RFCs - -* RFC 7953 Calendar Availability (VAVAILABILITY) -* RFC ???? New Properties for iCalendar (publication imminent) - -=== CalConnect Drafts accepted by CALEXT WG at IETF for progression - -* Event Publishing Extensions to iCalendar -* Improved Support for iCalendar Relationships -* CalDAV Managed Attachments - -=== New and Updated CalConnect Drafts at the IETF - -* WebDAV User Notifications -* WebDAV Resource Sharing -* CalDAV Calendar Sharing -* CardDAV Address Book Sharing - -== Technical Committee Work and Initiatives Going Forward - -=== TC API - -Working on a new key/value based data model. Much of the work is done and the remainder will -continue. Next steps are implementations, find a suitable name for the API. document the -iCalendar/JSON Format, develop specification and submit to IETF. - -=== TC AUTODISCOVERY - -Draft update in progress - -=== TC CALDAV - -Reviewed issues with recurrence splitting, and new VPATCH and VINSTANCE drafts-in-progress. - -Interest in either expanding TC Charter or initiating a new TC to cover broader issues than -CalDAV-specific. - -=== TC DEVGUIDE - -Significant additions during Test Event including porting the independent CalDAV and CardDAV -Implementations websites to the Developer's Guide. Will continue to push for external -contributions and additional content. Interest in documenting libraries such as ical4j and libical -in the Developer's Guide. - -=== TC EVENTPUB - -Review of DMOZ directory service as source of categorization and event types. - -=== TC FREEBUSY - -Dormant, current work item VPOLL waiting at IETF to be adopted into Working Group. - -=== TC FSC - -To be merged into TC SHARING. - -=== TC IMIP - -Documenting best practices on how iTIP over e-Mail (iMIP) should be structured to match existing -practice; developing server feature matrix. Expect to put best practices in DEVGUIDE. - -=== TC IOPTEST - -Conducted Interoperability Testing and Developer's Forum event at CalConnect XXXVII. -(Interoperability Test Event has been rebranded as Test Event and Developers' Forum; significant -technical discussions now taking place during the forum.) - -Lots of work on CalDAV Tester "Wrapper" developed by Ralf Becker; decided to initiate new TC -TESTER specifically to carry this tool forward to provide a black box test of standard appliances, -improve server testing. In particular lack of clients at test events make this tool extremely -valuable, potentially provides equivalent to reference implementation. - -=== TC ISCHEDULE - -Definite interest in moving forward with the draft at the IETF. "Identify Problem" will not apply -for most likely users including large organizations. - -=== TC PUSH - -Draft to be published to the IETF after minor updates. - -=== TC RESOURCE - -Dormant pending resource drafts adoption at IETF into a working group. - -=== TC SHARING - -Reviewed four drafts, some question as to where in IETF is best place to progress as. Drafts are -essentially ready to move forward when adopted. Next steps are subscription models and federated -sharing. - -=== TC TASKS - -Dormant pending adoption of draft by IETF WG - -=== PC-QR - -Formed at CalConnect XXXVI to explore interest in expanding vCard to contain visual data, support -non-North American address formats. Will become TC VCARD. - -=== PC-SEC - -Formed at CalConnect XXXVI to examine security issues with calendaring data and explore possible -ways forward. Will continue as PC until next event. - -== Plenary Decisions - -* TC TESTER to be created to carry forward work on CalDAV Tester -* TC VCARD to be created to move forward with PC QR issues - -== Future Events - -* CalConnect XXXVIII: February 13-17, 2017 - University of California, Irvine, California -* CalConnect XXXIX: June 5-9, 2017 - Tandem, Seattle, Washington -* CalConnect XXXX - September 25-29, 2017, Open-Xchange, Cologne, Germany - -The general format of the CalConnect Week is: - -* Monday morning through Wednesday noon, Developer's Forum (testing, tech discussions) -* Wednesday noon through Friday afternoon, Conference - -== Pictures from CalConnect XXXVII - -Pictures courtesy of Thomas Schäfer, 1&1 - -[%unnumbered,cols="a,a"] -|=== - -| [%unnumbered] -.Schloss Eckberg -image::Schloss-Eckberg-31.jpg[] -| [%unnumbered] -.Hotel and Meeting Venue -image::Signage-33.jpg[] -| [%unnumbered] -.Meeting Room -image::Meeting-Room-35.jpg[] -| [%unnumbered] -.Welcome Reception -image::Welcome-reception-37.jpg[] -| [%unnumbered] -.Conference Dinner Menu -image::Thursday-dinner-menu-39.jpg[] -| [%unnumbered] -.Group Picture -image::Group-picture-41.jpg[] -| [%unnumbered] -image::Conference-sketch-45.jpg[] -| [%unnumbered] -image::Developers-Forum-Sketch-43.jpg[] - -|=== diff --git a/sources/csd-report-conference-38.adoc b/sources/csd-report-conference-38.adoc deleted file mode 100644 index dd58b3a..0000000 --- a/sources/csd-report-conference-38.adoc +++ /dev/null @@ -1,205 +0,0 @@ -= Report on CalConnect Conference XXXVIII, February 15-17, 2017 -:docnumber: 1701 -:copyright-year: 2017 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2017-03-08 -:published-date: 2017-03-08 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-38 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XXXVIiI took place on February 15-17, 2017, hosted by the University of California, -Irvine, in Irvine, California The CalConnect Test Event (Monday, Tuesday, and Wednesday morning) -and Conference (Wednesday afternoon, Thursday and Friday) were held at the UC Irvine campus. - -The CalConnect Conference was attended by 21 people from 13 members The Test Event had 13 -participants from 8 members. - -The Conference focussed on strategic and possible work items in addition to ongoing work, and -finished with the CalConnect Plenary Session on Friday afternoon. The Conference agenda with notes -on the discussion topics may be found at -https://www.calconnect.org/events/calconnect-xxxviii-february-13-17-2017#conference-schedule[CalConnect XXXVIII Conference Schedule]. - -== Status of documents since last conference - -Much of the ongoing work in CalConnect is focused on specifications to become -internet draft submissions to the IETF and ultimately be progressed to publication as -RFCs (Proposed Standards), rather than directly published by CalConnect itself. - -Specifications in progress and not yet published are generally resident on GitHub either -in our public or private areas. - -=== Published Documents -* Report on CalConnect Conference XXXVII in Dresden -* Report on Interoperability Test Event XXXVII in Dresden - -=== CalConnect Specifications Published as Internet Standards (RFCs) -* RFC 7986 New Properties for iCalendar - -=== CalConnect Specifications Accepted for Publication as Internet Standards -* Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV) - -=== CalConnect Drafts in progress by CALEXT WG at IETF -* Event Publishing Extensions to iCalendar (TC CALENDAR) -* Improved Support for iCalendar Relationships (TC CALENDAR -* CalDAV Managed Attachments (TC CALENDAR) - -=== New and Updated CalConnect Drafts at the IETF -* Internet Calendar Scheduling Protocol (iSchedule) ((TC CALENDAR) -* Calendar Subscription Upgrades (TC SHARING) -* Support for Series in iCalendar (TC CALENDAR) - -== Technical Committee Work and Initiatives Going Forward - -NOTE: Several dormant TCs were closed at the CalConnect XXXVIII Plenary and their work program (if -any outstanding) and outstanding drafts if any merged into other TCs. - -=== TC API - -Working on a new key/value based data model. Much of the work is done and the remainder will -continue. Work will be expanded to include VTODOs (i.e. Tasks Extensions to iCalendar) and perhaps -contacts. Next steps are implementations, develop specification and submit to IETF. - -=== TC AUTODISCOVERY - -Draft update in progress - -=== TC CALDAV - -VPATCH and VINSTANCE are mature enough to begin implementation and testing. Enhanced Sync draft -starting to stabilize. Closed and merged into TC CALENDAR. - -TC CALENDAR established to further work across iCalendar, iMIP, iTIP, CalDAV, etc. and outstanding -work merged to TC CALENDAR. Will initially focus on iSchedule, VPATCH, VINSTANCE, Enhanced Synd. - -=== TC DEVGUIDE - -New iMIP section being developed. Established tracking with Google Analytics and implemented the -CNAME change for devguide.calconnect.org. - -=== TC EVENTPUB - -Closed and merged into TC CALENDAR. - -=== TC FREEBUSY - -Closed and merged into TC CALENDAR. - -=== TC FSC - -Closed and merged into TC SHARING. - -=== TC IMIP - -Closed and merged into TC CALENDAR. - -=== TC IOPTEST - -Conducted Interoperability Testing and Developer's Forum event at CalConnect XXXVIII. -(Interoperability Test Event has been rebranded as Test Event and Developers' Forum; significant -technical discussions now taking place during the forum.) See separate report on Test Event at -CalConnect XXXVIII. - -=== TC ISCHEDULE - -Closed and merged into TC CALENDAR. - -=== TC PUSH - -Draft to be published to the IETF after minor updates. - -=== TC RESOURCE - -Closed and merged into TC SHARING. - -=== TC SHARING - -Published new draft of Calendar Subscription Upgrades. Substantial interest from several members. - -=== TC TASKS - -Closed and merged into TC CALENDAR. - -=== PC-SEC - -Closed; program of work added to TC VCARD. - -== Plenary Decisions - -* TC CALENDAR created to carry on work across iCalendar, iMIP, iTIP, CalDAV areas. - -* Dormant TCs closed and merged into TC CALENDAR (EVENTPUB, FREEBUSY, IMIP, ISCHEDULE, TASKS), TC -SHARING (FSC), TC VCARD (RESOURCE). - -* ical4j adhoc will continue as active ad hoc committee; no expectation of becoming TC as should -be short-lived. - -* CalConnect XXXIX in Seattle will be moved a week later to June 12-16 due to schedule conflicts. - -== Future Events - -* CalConnect XXXIX: June 5-9, 2017 - Tandem, Seattle, Washington -* CalConnect XL- September 25-29, 2017, Open-Xchange, Cologne, Germany -* CalConnect XLI and later - TBD - -The general format of the CalConnect Week is: - -* Monday morning through Wednesday noon, Developer's Forum (testing, tech discussions) -* Wednesday noon through Friday afternoon, Conference - -== Pictures from CalConnect XXXVIII - -All pictures courtesy of Thomas Schäfer, 1&1 - -[%unnumbered,cols="a,a"] -|=== - -| [%unnumbered] -image::CC38_Sketchnote_Conference-49.jpg[] -| [%unnumbered] -image::img_5104-55.jpg[] -| [%unnumbered] -image::img_5109-47.jpg[] -| [%unnumbered] -image::img_5110-57.jpg[] -| [%unnumbered] -image::img_5161-53.jpg[] -| [%unnumbered] -image::img_5280-51.jpg[] - -|=== diff --git a/sources/csd-report-conference-39.adoc b/sources/csd-report-conference-39.adoc deleted file mode 100644 index 8613e0c..0000000 --- a/sources/csd-report-conference-39.adoc +++ /dev/null @@ -1,203 +0,0 @@ -= Report on CalConnect Conference XXXIX, June 14-16, 2017 -:docnumber: 1703 -:copyright-year: 2017 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2017-07-18 -:published-date: 2017-07-18 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-39 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XXXIX took place on June 12-16, 2017, hosted by Tandem in Seattle, Washington. The -CalConnect Test Event (Monday, Tuesday, and Wednesday morning) and Conference (Wednesday -afternoon, Thursday and Friday) were held at Tandem's headquarters at Galvanize in Seattle. - -The CalConnect Conference was attended by 16 people from 9 members plus a representative from the -IETF. The Test Event/Developers Forum had 8 participants from 5 members and was largely devoted to -the forum rather than specific testing. - -The Conference focussed on strategic and possible work items in addition to ongoing work, and -finished with the CalConnect Plenary Session on Friday afternoon. The Conference agenda with notes -on the discussion topics may be found at -https://www.calconnect.org/events/calconnect-xxxix-june-12-16-2017%23conference-schedule[CalConnect XXXIX Conference Schedule]. - -== Status of documents since last conference - -Much of the ongoing work in CalConnect is focused on specifications to become internet draft -submissions to the IEETF and ultimately be progressed to publication as RFCs (Proposed Standards), -rather than directly published by CalConnect itself. - -Specifications in progress and not yet published are generally resident on GitHub either in our -public or private areas. - -=== Published Documents - -* Report on CalConnect Conference XXXVIII in Irvine, California -* Report on Interoperability Test Event XXXVIII in Irvine, California - -=== CalConnect Specifications Published as Internet Standards (RFCs) - -* RFC 8144 Use of the Prefer Header Field in Web Distributed Authoring and Versioning - -=== CalConnect Specifications Accepted for Publication as Internet Standards - -* Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV) - -=== CalConnect Drafts to be Published as Informational RFCs -* CalDAV Managed Attachments (TC CALENDAR) - -=== CalConnect Drafts in progress by CALEXT WG at IETF -* Event Publishing Extensions to iCalendar (TC CALENDAR) -* Improved Support for iCalendar Relationships (TC CALENDAR - -=== New and Updated CalConnect Drafts at the IETF -* Push Discovery and Notification Dispatch Protocol (TC CALENDAR) - -== Technical Committee and Related Work - -=== TC API - -Robert Stepanek is the new Chair of TC API. Work on iCalendar is complete; work on Tasks has -begun. Holding on contacts for TC VCARD to move forward. - -=== TC AUTODISCOVERY - -Draft update in progress - -=== TC CALENDAR - -VPATCH and VINSTANCE are mature enough to begin implementation and testing. Work continues on the -VALARM Extensions draft. - -=== TC DEVGUIDE - -New content includes bootstrapping, vCard information. Improved content: link section dates and -times information. Looking for assistance to edit selected Wikipedia entries related to CalConnect. - -=== TC IOPTEST - -See separate report on Test Event at CalConnect XXXIX. - -=== TC PUSH - -Draft has been submitted to the IETF. - -=== TC SHARING - -Calendar Subscription Upgrades decided on a new status (not cancelled) and adding time range query. - -=== TC TESTER - -Brief report on the status of the work. - -=== TC VCARD - -Several presentations on status in TC VCARD and progress at the ISO/TC 211 meeting in Stockholm -earlier this month. TC 211/WG 7 has accepted a proposal from CalConnect TC VCARD to submit a New -Work Item Proposal on a machine-readable address profile data format. - -=== ICAL4J - -Building a CalConnect version of iCal4J merging 1&1 and SCG implementations. Ultimate goal is to -merge it with the original version from Ben Fortuna when new standards supported by this version -have been published. - -=== Calendar Spam - -Feedback from M3WAAG Thursday. Discussion about subscription/content providers also being -affected. Also discussed whether it is possible or desirable to establish a liaison with M3WAAG. - -== TC Directions for Period to CalConnect XL - -TC API: Create initial version of draft for standard, follow up on tasks - -TC CALENDAR: Convert Managed Attachments to informational RFC, reshape VALARM extensions, finish -calendar Relations, look at Task Extensions, continue VPATCH work - -TC DEVGUIDE: Feedback button, new content, wikipedia updates - -TC PUSH: Finish up Push specification - -TC SHARING: Subscription update draft will include time rate queries, use delete, header templating. - -TC TESTER: Increase tests, decide how to maintain - -== Plenary Decisions - -* Jorte's offer to host CalConnect XLII (June, 2018) in Tokyo, Japan was approved. -* 1&1's offer to host CalConnect XXLIII (September, 2018) in Karlsruhe, Germany was approved. - -== Future Events - -* CalConnect XL- September 25-29, 2017, Open-Xchange, Cologne, Germany -* CalConnect XLI - Winter, 2018 - TBD -* CalConnect XLII - June 4-8, 2018 - Jorte, Tokyo, Japan -* CalConnect XLIII - September, 2018 - 1&1, Karlsruhe, Germany - -The general format of the CalConnect Week is: - -* Monday morning through Wednesday noon, Test Event and Developer's Forum (testing, tech -discussions) -* Wednesday noon through Friday afternoon, Conference - -Oath (combined AOL and Yahoo) will host the Winter 2018 CalConnect XLI in -Sunnyvale, California. - -Specific dates were set for CalConnect XLI and CalConnect XLIII (see below). - -== Pictures from CalConnect XL - -Pictures courtesy of Thomas Schäfer, 1&1 - -[%unnumbered,cols="a,a"] -|=== - -| [%unnumbered] -image::img_6848-17.jpg[] -| [%unnumbered] -image::img_6859-19.jpg[] -| [%unnumbered] -image::img_6872-21.jpg[] -| [%unnumbered] -image::img_6876-25.jpg[] -| [%unnumbered] -image::img_6890-23.jpg[] -| [%unnumbered] -image::img_7252-27.jpg[] - -|=== diff --git a/sources/csd-report-conference-40.adoc b/sources/csd-report-conference-40.adoc deleted file mode 100644 index 1826acc..0000000 --- a/sources/csd-report-conference-40.adoc +++ /dev/null @@ -1,193 +0,0 @@ -= Report on CalConnect Conference XL, September 27-29, 2017 -:docnumber: 1705 -:copyright-year: 2017 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2017-10-23 -:published-date: 2017-10-23 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-40 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XL took place September 27-29, 2017, hosted by Open-Xchange in -Cologne, Germany. The CalConnect Test Event (Monday, Tuesday, and Wednesday -morning) and Conference (Wednesday afternoon, Thursday and Friday) were held at -Komed House, a conference facility in the Cologne Media Park. - -The CalConnect Conference was attended by 20 people from 12 members plus a -guest from GFI. The Test Event/Developers Forum had 10 participants from 7 -members and was largely devoted to the forum and CalDAV Tester rather than specific -testing. - -The Conference focussed on strategic and possible work items in addition to ongoing -work, and finished with the CalConnect Plenary Session on Friday afternoon. The -Conference agenda with notes on the discussion topics may be found at -https://www.calconnect.org/events/calconnect-xl-september-25-29-2017#conference-schedule[CalConnect XL Conference Schedule]. - -== Status of Documents since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications to become -internet draft submissions to the IETF and ultimately be progressed to publication as -RFCs (Proposed Standards), rather than directly published by CalConnect itself. - -Specifications in progress and not yet published are generally resident on GitHub either -in our public or private areas. - -=== CalConnect Drafts to be Published as Informational RFCs - -* CalDAV Managed Attachments (TC CALENDAR) - -=== CalConnect Drafts in CALEXT Working Group Last Call at IETF - -* Event Publishing Extensions to iCalendar (TC CALENDAR) - -=== CalConnect Drafts in Progressing at CALEXT Working Group at IETF - -* Improved Support for iCalendar Relationships (TC CALENDAR - -=== New and Updated CalConnect Drafts at the IETF - -* Push Discovery and Notification Dispatch Protocol (TC CALENDAR) -* Calendar Subscription Upgrades -* JSCalendar: A JSON representation of calendar data - -== General Status and Announcements - -Ronald Tse of Ribose was elected the sixth CalConnect Director, and was appointed -Director, External Relationships. - -CalConnect has established a formal Category A Liaison with ISO/TC 211 and is -exploring a similar liaison with ISO/TC 154. We are also exploring a joint liaison with -M3AAWG. - -== Status of Technical Committee and Related Work; Plans for Future Work - -=== TC API - -Work on JSCalendar is progressing, accommodating contacts and tasks as well as -events. - -=== TC AUTODISCOVERY - -Pending; Draft update in progress - -=== TC CALENDAR - -Work continues on categorization and event types, consistent handling of per-user -data in events, support for series in iCalendar (as an alternative to recurrences), alarms -and transparency in JSCalendar, generic notification systems for alarms, calendar -subscription upgrades, extensions for improved grouping of properties, and a -CalConnect version of ical4j. - -=== TC DEVGUIDE - -Service has been migrated of open shift to the Google App engine. We are looking for -help with the wikipedia article on CalConnect and related articles. Discussion of -additional areas to be added to the Developers Guide including CalDAV Tester. - -=== TC IOPTEST - -See separate report on Test Event at CalConnect XL. TC IOPTEST calls have been -integrated into the Event Planning calls and no separate IOPTEST calls were held since -the previous event in June. - -=== TC PUSH - -Draft has been submitted to the IETF; we are exploring which working group should -handle it. Looking for more implementations. - -=== TC SHARING - -Calendar Subscription Upgrades decided on a new status (not cancelled) and adding -time range query. Working on how to advertise which timezone server is used. - -=== TC TESTER - -Brief report on the status of the work. - -=== TC VCARD - -Several presentations on status in TC VCARD and progress at ISO/TC 211. TC VCARD -is working on the New Work Item Proposal on a machine-readable address profile data -format for TC 211 and expects to submit it soon, perhaps by the next TC 211 Plenary. - -=== BOF Sessions - -Birds of a Feather sessions were held on security and on streaming for iCalendar data. - -Work will continue on a security model starting from VCARD security, via mailing list -and slack. Proposed an initial call for an Ad Hoc on Streaming. - -== Plenary Meeting - -Oath (combined AOL and Yahoo) will host the Winter 2018 CalConnect XLI in -Sunnyvale, California. - -Specific dates were set for CalConnect XLI and CalConnect XLIII (see below). - -== Future Events - -* CalConnect XLI - January 28 - February 2, 2018 - Oath, Sunnyvale, California -* CalConnect XLII - June 4-8, 2018 - Jorte, Tokyo, Japan -* CalConnect XLIII - September 24028, 2018 - 1&1, Karlsruhe, Germany - -The general format of the CalConnect Week is: - -* Monday morning through Wednesday noon, Test Event and Developer's Forum -(testing, tech discussions) -* Wednesday noon through Friday afternoon, Conference - -== Pictures from CalConnect XL - -Pictures courtesy of Thomas Schäfer, 1&1 - -[%unnumbered,cols="a,a"] -|=== - -2+| [%unnumbered] -image::img_7795-29.jpg[] - -| [%unnumbered] -image::22092477_10155728420429347_1097884688_o-37.jpg[] -| [%unnumbered] -image::img_7821-31.jpg[] -| [%unnumbered] -image::img_7827-33.jpg[] -| [%unnumbered] -image::img_7830-35.jpg[] - -|=== diff --git a/sources/csd-report-conference-41.adoc b/sources/csd-report-conference-41.adoc deleted file mode 100644 index a65ce9a..0000000 --- a/sources/csd-report-conference-41.adoc +++ /dev/null @@ -1,201 +0,0 @@ -= Report on CalConnect Conference XLI, January 31 - February 2, 2018 -:docnumber: 1801 -:copyright-year: 2018 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2018-03-02 -:published-date: 2018-03-02 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-41 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XLI took place January 31 - February 2, 2018, hosted by Oath in -Sunnyvale, California. The CalConnect Test Event (Monday, Tuesday, and Wednesday -morning) and Conference (Wednesday afternoon, Thursday and Friday) were held at -Oath's Sunnyvale campus. - -The CalConnect Conference was attended by 19 people from 11 members, plus two -CalConnect Directors for a total of 21 The Test Event/Developers Forum had 7 -participants from 6 members and was largely devoted to the forum and CalDAV Tester -rather than specific testing. - -The Conference focussed on strategic and possible work items in addition to ongoing -work, and finished with the CalConnect Plenary Session on Friday afternoon. The -Conference agenda with notes on the discussion topics may be found at -https://www.calconnect.org/events/calconnect-xli-winter-2018#conference-schedule[CalConnect XLI Conference Schedule]. - -== Status of Documents Since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications to become -internet draft submissions to the IEETF and ultimately be progressed to publication as -RFCs (Proposed Standards), rather than directly published by CalConnect itself. - -Specifications in progress and not yet published are generally resident on GitHub either -in our public or private areas. - -=== CalConnect Drafts to be Published as Informational RFCs - -* CalDAV Managed Attachments (TC CALENDAR) - -=== CalConnect Drafts in CALEXT Working Group Last Call at IETF - -* Event Publishing Extensions to iCalendar (TC CALENDAR) -* Improved Support for iCalendar Relationships (TC CALENDAR - -=== CalConnect Drafts in Progress at CALEXT Working Group at IETF - -* JSCalendar: A JSON representation of Calendar data - -=== New and Updated CalConnect Drafts at the IETF - -* Calendar Subscription Upgrades -* The Time Zone Data Distribution Service (TZDIST) Geolocate Extension -* The Time Zone Information Format (TZif) - -== General Status and Items - -CalConnect has established a formal Category A Liaison with ISO/TC 154 and is -exploring a similar liaison with ISO/TC 46. We have also established a reciprocal -membership liaison with M3AAWG. - -IETF is considering reopening the TZDIST working group to deal with the new Time -Zone drafts we have submitted. - -CalConnect is discussing whether or not it would be a provider of services (such as a -registry) or not. Alternatively we might act as the steward of an effort if not the service -provider. - -Some discussion on a new TC USECASE to try and help developers understand what -is not fit for the purpose. - -Will initiate a new TC CALSPAM to work on calendar spam best practices, a joint effort -with M3AAWG. - -== Future Work - -=== Ad Hoc on Streaming - -Work on goals, ideas, objectives - -=== TC API - -Work on JSCalendar is progressing, accommodating contacts and tasks as well as -events. - -=== TC AUTODISCOVERY - -Pending; Draft update in progress - -=== TC CALENDAR - -New Time Zone drafts on a geolocate extension and information formats. - -Informational RFC on 5545 listing all RFCs connected to calendaring and needed to -understand, including acknowledging CalConnect. - -IMIP extensions to better support calendaring invites and responses. - -CalConnect be steward of possible time zone distribution service, but not actual -service provider. Google may be interested in providing such a service. - -=== TC DEVGUIDE - -Fill in gaps in current information, look at use cases. Do we need a TC USECASE? - -=== TC IOPTEST - -Support Tokyo event. - -See separate report on Test Event at CalConnect XLI. TC IOPTEST calls have been -integrated into the Event Planning calls and no separate TC IOPTEST calls were held. - -=== TC PUSH - -Draft has been submitted to the IETF; we are exploring which working group should -handle it. Looking for more implementations. - -=== TC SHARING - -Annotation, subscription, server side subscription - -=== TC TESTER - -Brief report on the status of the work. - -=== TC VCARD - -Maintain liaison with ISO TC 211, progress work - - -== Plenary Meeting - -* Jorte will host CalConnect XLII on June 4-8, 2018, in Tokyo, Japan. -* 1&1 will host CalConnect XLIII on September 24-28, 2018, in Karlsruhe, Germany. -* A request for volunteers to host Winter 2019 and beyond was issued. - -== Future Events - -* CalConnect XLII - June 4-8, 2018 - Jorte, Tokyo, Japan -* CalConnect XLIII - September 24-28, 2018 - 1&1, Karlsruhe, Germany - -The general format of the CalConnect Week has been as below. This will be modified -significantly for Tokyo and an entirely new format brought in for Karlsruhe in -September. - -* Monday morning through Wednesday noon, Test Event and Developer's Forum -(testing, tech discussions) -* Wednesday noon through Friday afternoon, Conference - -== Pictures from CalConnect XLI - -Pictures courtesy of Thomas Schäfer, 1&1, and Gary Schwartz. - -[%unnumbered,cols="a,a"] -|=== - -2+| [%unnumbered] -image::img_9074-31.jpg[] -| [%unnumbered] -image::img_9073-35.jpg[] -| [%unnumbered] -image::img_9077-41.jpg[] -| [%unnumbered] -image::img_9102-33.jpg[] -| [%unnumbered] -image::Yahoo-Hallway-1-37.jpg[] - -|=== diff --git a/sources/csd-report-conference-42.adoc b/sources/csd-report-conference-42.adoc deleted file mode 100644 index aff27b8..0000000 --- a/sources/csd-report-conference-42.adoc +++ /dev/null @@ -1,217 +0,0 @@ -= Report on CalConnect Conference XLII, June 4 - June 8, 2018 -:docnumber: 1803 -:copyright-year: 2018 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2018-06-25 -:published-date: 2018-06-25 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-42 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XLII took place June 4-8, 2018, hosted by Jorte in Tokyo, Japan. The Developers Forum -(Monday, Tuesday, and Wednesday morning), Data Event Summit with JEDC (the Japan Data Event -Committee) (Wednesday afternoon), and Conference (late Wednesday afternoon, Thursday and Friday) -were held at Jorte's offices in Tokyo or in conference rooms in the same building. - -The CalConnect Conference was attended by a total of 12 people from 8 members. The Developers -Forum had 7 participants from 4 members and was largely devoted to the forum rather than specific -testing. -The Conference focussed on strategic and possible work items in addition to ongoing work, and -finished with the CalConnect Plenary Session on Friday afternoon. The Conference agenda with notes -on the discussion topics may be found at -https://www.calconnect.org/events/.calconnect-xlii-june-04-08-2018#conference-schedule[CalConnect XLII Conference Schedule]. - -The Data Event Summit was attended by a total of 26 people, all CalConnect participants for the -conference plus 15 people from JEDC, and featured presentations from two government agencies, -Sharp, and our hosts. The primary focus was Japan's efforts to ensure open data is available from -their local governments (about 1800) in a common data format, and our encouragement for them to -adopt the international calendaring and scheduling standards, which would require some -enhancements and joint work between us. - -== Status of Documents since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications and standards, many of which -will become internet draft submissions to the IETF and ultimately be progressed to publication as -RFCs (Proposed Standards), rather than directly published by CalConnect itself. CalConnect will -also co-publish standards with other standards organizations, or self-publish as needed. - -Specifications in progress and not yet published are generally resident on GitHub either in our -public or private areas. - -=== CalConnect Drafts to be Published as Informational RFCs - -* CalDAV Managed Attachments (TC CALENDAR) - -=== CalConnect Drafts in CALEXT Working Group Last Call at IETF - -* Event Publishing Extensions to iCalendar (TC CALENDAR) -* Improved Support for iCalendar Relationships (TC CALENDAR - -=== CalConnect Drafts in Progress at CALEXT Working Group at IETF - -* JSCalendar: A JSON representation of Calendar data - -=== CalConnect Drafts in Progress at TZDIST-BIS Working Group at IETF - -* The Time Zone Information Format (TZif) -* The Time Zone Data Distribution Service (TZDIST) Geolocate Extension - -=== New and Updated CalConnect Drafts at the IETF -* Calendar Subscription Upgrades -* Support for Series in iCalendar - -== CalConnect Liaisons - -CalConnect has established a formal reciprocal membership liaison with M3AAWG. - -CalConnect has established formal Category A Liaisons with the folllowing ISO Committees: - -* ISO PC 317 -* ISO TC 154 -* ISO TC 211 -* ISO TC 46 -* ISO JTC 1 SC 27 -* ISO TC 37 - -IETF is considering reopening the TZDIST working group to deal with the new Time Zone drafts we -have submitted. - -== General Status and Items - -A new TC CALSPAM has been created to work on calendar spam best practices, a joint effort with -M3AAWG, and is actively working on a best practices document. The work has been at both the latest -M3AAWG conference and our Tokyo conference. - -A new TC STREAMING has been created from the Ad Hoc previously set up. Its first task will be the -devleopment of the specification. - -TC IOPTEST was closed as its function has been subsumed into the Event Planning committee and -process. - -CalConnect is planning to resume its practice of self-publishing standards, which hasn't been done -for some time as much of its work has focused on extensions to existing IETF specifications (many -of which were also developed by CalConnect). A new Ad Hoc on Publishing has been set up to review -the obsolete processes and establish new ones. CalConnect also intends to begin co-publishing some -documents with other organizations with which we have liaisons. - -The TC CHAIRS committee has been renamed the Technical Coordination Commitee to better reflect the -role and responsibilities of this group. - -A new work area has been proposed on "Party Crashing" - event invitations can be forwarded to -uninvited persons who then can spoof the the systems to gain an invitation. - -The work on CALSPAM has proposed a new work item on establishing a mechanism whereby users can -determine where an event on their calendar came from. - -More discussion was held on a proposal for a completely revised conference format for CalConnect, -which would offer both the Conference Track and a Technical Track as a single event with a single -fee. This matter is being proposed for a one-time test at the next (Karlsruhe) event. - -Status provided on synchronization (time to draft a spec?), server-side subscriptions, series as -an alternative to recurrences. - -== Future Work - -=== TC API - -Work on JSCalendar is progressing, accommodating contacts and tasks as well as events. - -=== TC AUTODISCOVERY - -Pending; Draft update in progress - -=== TC CALENDAR - -* Response tokens for Party Crashing (NWI proposal from Google) -* CALSPAM's proposal for storing information about how events ended up in iCalendar. - -=== TC DEVGUIDE - -* Review approach on standards -* Move page content from Drupal to DevGuide where appropriate -* Looking into GitHub pages (layout first, CNAME second) - -=== TC PUSH - -Draft has been submitted to the IETF; we are exploring which working group should handle it. -Looking for more implementations. - -=== TC SHARING - -Annotation, subscription, server side subscription - -=== TC STREAMING - -Streaming specification - -=== TC TESTER - -Work at Karlsruhe conference. - -=== TC VCARD - -Maintain liaison with ISO TC 211, progress work - -== Plenary Meeting - Confirmed Future Events - -* 1&1 will host CalConnect XLIII on September 24-28, 2018, in Karlsruhe, Germany. -* Google will host CalConnect XLIV on February 4-8, 2019, in Zürich, Switzerland. -* You Can Book Me (YCBM) will host CalConnect XLV on June 307, 2019 in Bedford, -England. - -== Pictures from CalConnect XLII - -Pictures courtesy of Thomas Schäfer, 1&1. - -[%unnumbered,cols="a,a"] -|=== - -| [%unnumbered] -image::img_0409-43.jpg[] -| [%unnumbered] -image::img_0415-51.jpg[] -| [%unnumbered] -image::img_0498-45.jpg[] -| [%unnumbered] -image::img_0504-49.jpg[] -| [%unnumbered] -image::img_0590-53.jpg[] -| [%unnumbered] -image::img_0608-55.jpg[] - -|=== diff --git a/sources/csd-report-conference-43.adoc b/sources/csd-report-conference-43.adoc deleted file mode 100644 index a97832c..0000000 --- a/sources/csd-report-conference-43.adoc +++ /dev/null @@ -1,237 +0,0 @@ -= Report on CalConnect Conference XLIII, September 24 - September 27, 2018 -:docnumber: 1805 -:copyright-year: 2018 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2018-10-23 -:published-date: 2018-10-23 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-43 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XLIII took place September 24-27, 2018, hosted by 1&1 in Karlsruhe, Germany. The -conference was held on 1&1's premises. The conference was attended by a total of 20 people from 10 -member organizations. - -This conference was a one-time experiment with a new conference format, technical and conference -tracks alternating each day, and a single fee rather than the previous separate fees for the test -event and conference. It was also a 4-day event, Monday through Thursday, rather than the 5 days -that the previous format required to attend both the test event and the conference. The new format -was based on recommendations from a working group set up by the CalConnect Board at the beginning -of the year, to examine the current formats and make recommendations for future changes. - -The Conference focussed on strategic and possible work items in addition to ongoing work, and -finished with the CalConnect Plenary Session prior to lunch on Thursday. Thursday afternoon was -open time for working sessions. The schedule was rearranged during the week based on input from -participants. The final Conference agenda with notes on the discussion topics may be found at -https://www.calconnect.org/events/calconnect-xliii-september-2018#conference-schedule[CalConnect XLIII Conference Schedule]. - -== Status of Documents Since Last Conference - -Much of the ongoing work in CalConnect is focused on specifications and standards, many of which -will become internet draft submissions to the IETF and ultimately be progressed to publication as -RFCs (Proposed Standards), rather than directly published by CalConnect itself. CalConnect will -also co-publish standards with other standards organizations, or self-publish as needed. - -Specifications in progress and not yet published are generally resident on GitHub either in our -public or private areas. - -=== CalConnect Drafts to be Published as Informational RFCs - -* CalDAV Managed Attachments (TC CALENDAR) - -=== CalConnect Drafts in CALEXT Working Group Last Call at IETF - -* Event Publishing Extensions to iCalendar (TC CALENDAR) -* Improved Support for iCalendar Relationships (TC CALENDAR - -=== CalConnect Drafts in Last Call at CALEXT Working Group at IETF - -* JSCalendar: A JSON representation of Calendar data - -=== CalConnect Drafts in Last Call at IESG - -* The Time Zone Information Format (TZif) - -=== CalConnect Drafts in Progress at TZDIST-BIS Working Group at IETF - -* The Time Zone Data Distribution Service (TZDIST) Geolocate Extension - -== Calconnect Liaisons - -CalConnect has formal reciprocal membership liaisons with M3AAWG and OASIS and a strong working -relationship with the IETF. - -CalConnect has established formal Category A Liaisons with the following ISO Committees: - -* ISO PC 317 -* ISO TC 154 -* ISO TC 211 -* ISO TC 46 -* ISO JTC 1 SC 27 -* ISO TC 37 - -== General Status and Items - -An Adhoc Committee on the EU Time proposal to discontinue Summer Time has been created to submit -an Advisory Report to the EU. We anticipate holding a workshop on this subject at CalConnect XLIV -in February 2019. - -TC DATETIME has been created to further CalConnect work on date and time formats and related -issues, and to provide a "home" for our liaison with ISO TC 211 and ISO TC 154 and the drafts on -ISO 8601-1 and 8601-2 on date and time formats and recurrences. Also timezone data model and how -to announce TZ changes (management standard?) - -TC LOCALIZATION has been created to further CalConnect work on localization of calendaring and -schedule event information and related work such as address formats, -and to provide a home for our liaison with ISO TC 37 in the area of naming and addressing. - -CalConnect is planning to resume its practice of self-publishing standards, which hasn't been done -for some time as much of its work has focused on extensions to existing IETF specifications (many -of which were also developed by CalConnect). To further this work, new CalConnect Standards -Directives have been written to bring our document requirement and progression and publishing -policies and procedures in line with ISO and other international standards organizations. The -Plenary meeting approved a recommendation to the CalConnect Board of Directors to adopt the draft -directives. - -Feedback was obtained on the new conference format being tried at this event (as a one-time trial) -as noted above. In general the format is well thought of, several adjustments were made to the -schedule as the week progressed. - -Formal testing was not done as part of the program at this event, although individuals are welcome -to test as desired during the course of the meeting. - -== Future Work - -=== TC API - -JSCalendar is in working group last call at the IETF. Work continues with JSContacts and JSTasks. - -=== TC AUTODISCOVERY - -Interest in reactivating the group and moving forward with open issues and new items brought up in -discussion. ICalConnect can publish this draft as a CalConnect Standard. Possibly have a call to -follow up on discussion. - -=== TC CALENDAR - -* Discussion about DTSTART being part first instance of a recurrence but not part of the RRULE, -file erratum on the RFC - -* Interest in party-crashing draft, will encourage Google to write the drat and perhaps implement -and test the feedback from clients - -* Presentations on both JSCalendar and JMAP. - -* Discussion on what to do about e-Tag, create a best practice document. - -* Discussion on public calendars and how to move forward, perhaps another paper. - -* Server side Subscription. - -=== TC CALSPAM - -Best current practices document is nearly ready for public review. Discussion of the abuse audit -draft. - -=== TC DEVGUIDE - -* Continue Move page content from Drupal to Devguide where appropriate - -* Looking into GitHub pages (layout first, CNAME second) - -* Relocated the DevGuide to a Google offering in support of future requirements - -=== TC PUSH - -Prof-of-concept implementation exists; definite interest from FastMail. Still looking for a home -for the draft; if necessary CalConnect can publish it. Possibly have a call to follow up on -discussion. Need to develop error conditions. - -=== TC SHARING - -Annotation, subscription, server side subscription - -=== TC STREAMING - -Plan finalize the specification without a specific protocol as it should be a generalized approach. - -=== TC TESTER - -Work done at Karlsruhe conference, will have a post-conference review and level-set call. - -=== TC VCARD - -Set up call on the contact data model with FastMail participants, review charter. Need to adjust -rights for Date & Time. - -== Plenary Meeting - -Recommendation to Board of Directors to approve the new CalConnect Standards Directives and the -Partner Standards Development Organization. - -TC DATETIME and TC LOCALIZATION approved; co-chairs at to develop Charters and submit to TCC. - -== Confirmed Future Events - -* Google will host CalConnect XLIV on February 4-8, 2019, in Zürich, Switzerland. -* You Can Book Me (YCBM) will host CalConnect XLV on June 3-7, 2019 in Bedford, -England. -* Possible interest by FastMail in hosting CalConnect XLVI in Autumn 2019 in -Philadelphia. - -== Pictures from Calconnect XLIII - -Pictures courtesy of Thomas Schäfer, 1&1 - -[%unnumbered,cols="a,a"] -|=== - -| [%unnumbered] -image::img_1888-59.jpg[] -| [%unnumbered] -image::img_1892-61.jpg[] -| [%unnumbered] -image::img_1919-63.jpg[] -| [%unnumbered] -image::img_1930-65.jpg[] -| [%unnumbered] -image::img_7653-57.jpg[] -| [%unnumbered] -image::IMG_7980-29.jpg[] - -|=== diff --git a/sources/csd-report-conference-44.adoc b/sources/csd-report-conference-44.adoc deleted file mode 100644 index 525f6bf..0000000 --- a/sources/csd-report-conference-44.adoc +++ /dev/null @@ -1,218 +0,0 @@ -= Report on CalConnect Conference XLIV, February 5 - February 8, 2019 -:docnumber: 1901 -:copyright-year: 2019 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2019-03-07T00:00:00Z -:published-date: 2019-03-07T00:00:00Z -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:toc: -:stem: -:imagesdir: images/conference-44 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - - -:sectnums!: -== Introduction - -CalConnect XLIV took place February 5-8, 2019, hosted by Google in -Zürich, Switzerland. A Time Zone Workshop was held Tuesday -afternoon during the conference. The conference was held on -Google's premises, and was attended by a total of 31 people from 11 -member organizations, and 5 external invitations to the workshop. - -This conference was organized along the guidelines from the -previous conference in Karlsruhe; however, separate technical and -general tracks were eliminated. Instead sessions were identified by -session type. A single fee for the entire four-day conference was -charged. Additionally, we schedule a "codefest" for Monday, 4 -February, with open attendance. - -The Conference focused on strategic and possible work items in -addition to ongoing work, and finished with the CalConnect Plenary -Session prior to lunch on Friday. Friday afternoon was scheduled -for working sessions. The schedule was rearranged during the week -based on input from participants. The final pre-event Conference -agenda with notes on the discussion topics may be found at -https://www.calconnect.org/events/calconnect-xliv-february-4-8-2019#conference-schedule[CalConnect XLIIV Conference Schedule]. - - -:sectnums: -== Status of documents since last conference - -Specifications in progress and not yet published are generally resident on GitHub either in our public or private areas. - -=== Documents at CalConnect - -==== Published - -* CC/R 18003:2019 Calendar operator practices - Guidelines to protect against calendar abuse (TC CALSPAM) -* CC/DIR/FDS 10001:2018 CalConnect Directive: Standardization and publication -* CC/DIR/FDS 10002:3028 CalConnect Directive: Standard document requirements -* CC/DIR/DS 10003:02018 CalConnect Directive: Patent policy - -==== Committee Drafts - -* CC/CD 51003 Series in iCalendar -* CC/CD 51004 iCalendar Relationships -* CC/CD 51005 Calendar Subscription Upgrades -* CC/CD 51006 Consensus scheduling - iCalendar vPoll component - -=== Documents at ISO - -* ISO/CC 19160-1 "Addressing -- Digital addresses" in working draft at ISO/TC 211 -* ISO/CC 34000 "Date and time -- Concepts and vocabulary" is under -NWIP ballot at ISO/TC 154, ballot opened Feb 4 will end on April 29. - -=== Documents at the IETF - -==== Published as Proposed Standard - -* The Time Zone Information Format (TZif) RFC 8536 - -==== Too be Published as Informational RFCs - -* CalDAV Managed Attachments (TC CALENDAR) - -==== CalConnect Drafts in Working Group Last Call - -* Event Publishing Extensions to iCalendar (TC CALENDAR) -* Improved Support for iCalendar Relationships (TC CALENDAR) -* JSCalendar: A JSON representation of Calendar data -* The Time Zone Data Distribution Service (TZDIST) Geolocate Extension - -==== CalConnect Drafts submitted not assigned to WG - -* CalDAV extension for scheduling controls - -== CalConnect Liaisons as of February 04 - -CalConnect has formal reciprocal membership liaisons with M3AAWG -and OASIS and a strong working relationship with the IETF. - -CalConnect has established formal Category A Liaisons with the following ISO Committees: - -* ISO/IEC JTC 1/SC 27 IT Security Techniques -* ISO/PC 317 Consumer protection: privacy by design for consumer goods and services -* ISO/TC 37 Language and terminology -* ISO/TC 37/SC 4 Language resource management -* ISO/TC 37/SC 5 Translation, interpreting and related technology -* ISO/TC 46 Information and documentation -* ISO/TC 46/SC 4 Technical interoperability -* ISO/TC 46/SC 9 Identification and description -* ISO/TC 154 Processes, data elements and documents in commerce, industry and administration -* ISO/TC 211 Geographic information/Geomatics - -== General Status and Items from Conference XLIV - -The Time Zone Workshop planned by TC DATETIME was held on Tuesday afternoon. -Subsequent steps will be determined for TC DATETIME. - -* Summary of event to timezonediscuss public mailing list. -* Press release writeup for news feed. -* Modify a system to fetch time zone data from a TZDIST server -* Investigate whether IANA could/would operate a TZDIST server -* Learn more about ISO TC 154 work to establish registry for time zone data - -An Ad Hoc Committee on Rich Text (in Calendar events) was formed -and will conduct several calls over February and early March; the -committee is due to finish by mid-March. - -An Ad Hoc Committee on Use Cases was formed to consider UI issues -for displaying multiple time zones and develop best practice advice -for UI developers. - -The committee will develop a Charter for a new TC USECASE to be -considered at the next CalConnect event. - -TC CALSPAM finished its work and will be closed following any -updates from the next M3AAWG conference in late February. Open -issues will be transferred to TC CALENDAR. - -CalConnect has approved the new Standards Directives. Work -continues with related items such as revised IPR and Copyright -policies, and a co-publishing agreement with ISO and other -organizations. - -Feedback was obtained on the new conference format as used at this -meeting. The consensus was that identifying sessions by category -was not as important as early descriptions of the planned sessions. - -Plan for a 1-day hackathon on the Monday of the event week, with -the conference itself Tuesday-Friday. Establish a small charge to -give those who signed up some stake in actually coming. - -Start to build in more testing time as JSCalendar gets more -traction. Way to involve non-members (perhaps via hackathon?) - -Advertise events (and hackathon) more to non-members. - -== Plenary Meeting - -Ad Hoc Committees on Rich Text and Use Cases approved and will -start work immediately. Need charter for proposed TC USECASE asap. - -TC PUSH to be reactivated. - -TC CALSPAM will be closed. - -TC LOCALIZATION has not moved forward at this point. - -== Confirmed Future Events - -* You Can Book Me (YCBM) will host CalConnect XLV on June 3-7, 2019 in Bedford, England. - -* FastMail will host CalConnect XLVI on October 7-11, 2019 in Philadelphia, USA. - -== Pictures from CalConnect XLIV - -Pictures courtesy of Thomas Schäfer, 1&1. - -[%unnumbered,cols="a,a"] -|=== - -| [%unnumbered] -image::img_2611.jpg[] -| [%unnumbered] -image::img_2653.jpg[] -| [%unnumbered] -image::img_2656.jpg[] -| [%unnumbered] -image::img_2682.jpg[] -| [%unnumbered] -image::img_2685.jpg[] -| - -|=== diff --git a/sources/csd-report-conference-45.adoc b/sources/csd-report-conference-45.adoc deleted file mode 100644 index 72ecea9..0000000 --- a/sources/csd-report-conference-45.adoc +++ /dev/null @@ -1,204 +0,0 @@ -= Report on CalConnect Conference XLV, June 3 - June 7, 2019 -:docnumber: 1902 -:copyright-year: 2019 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2019-07-10 -:published-date: 2019-07-10 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/conference-45 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -CalConnect XLV took place June 3-6, 2019, hosted by You Can Book Me in Bedford, United Kingdom. -The conference was held on Google's premises, and was attended by a total of 13 people from 7 -member organizations, plus attendees to a joint virtual working group session with the IETF CALEXT -working group. Friday morning, June 7, was also available as a working session for attendees. - -The Conference focused on strategic and possible work items in addition to ongoing work, and -finished with the CalConnect Plenary Session on Thursday. The schedule was rearranged during the -week based on input from participants. The final pre-event Conference agenda with notes on the -discussion topics may be found at -https://www.calconnect.org/events/calconnect-xlv-june-3-7-2019#conference-schedule[CalConnect XLV Conference Schedule]. - -== Status of documents since last conference - -Specifications in progress and not yet published are generally resident on GitHub either in our -public or private areas. - -=== Documents at CalConnect - -==== Published - -* CC/DIR 1005:2019 Guidelines for the implementation of the CalConnect Patent Policy - -* CC/R 18003:2019 Calendar operator practices - Guidelines to protect against calendar abuse (TC CALSPAM) - -* CC/DIR 10001:2019 CalConnect Directive: Standardization and publication - -* CC/DIR 10002:2019 CalConnect Directive: Standard document requirements - -* CC/DIR 10003:2018 CalConnect Directive: Patent policy - -==== Committee Drafts - -* CC/CD 51003 Series in iCalendar - -* CC/CD 51004 iCalendar Relationships - -* CC/CD 51005 Calendar Subscription Upgrades - -* CC/CD 51006 Consensus scheduling - iCalendar vPoll component - -==== Documents at ISO - -* ISO/CC 19160-1 "Addressing -- Digital addresses" in working draft at ISO/TC 211 - -* ISO/CC 34000 "Date and time -- Concepts and vocabulary" is under NWIP - -=== Documents at the IETF - -==== Published as Proposed Standard - -* CalDAV Managed Attachments RFC 8607 - -==== Drafts in Final Review - -* Event Publishing Extensions to iCalendar (TC CALENDAR) - -==== Drafts in CALEXT Working Group Last Call - -* Improved Support for iCalendar Relationships (TC CALENDAR -* JSCalendar: A JSON representation of Calendar data - -==== Assigned to CALEXT WG - -* CalDAV extension for scheduling controls -* VLARM Extensions for iCalendar -* Calendar Subscription Upgrades - -==== Pending Assignment to CALEXT WG - -* VPOLL: Consensus Scheduling Component for iCalendar -* Support for Series in iCalendar - -== CalConnect Liaisons as of February 04 2019 - -CalConnect has formal reciprocal membership liaisons with M3AAWG -and OASIS and a strong working relationship with the IETF. - -CalConnect has established formal Category A Liaisons with the ITU, and with the following ISO -Committees: - -* ISO/IEC JTC 1/SC 27 IT Security Techniques -* ISO/PC 317 Consumer protection: privacy by design for consumer goods and services -* ISO/TC 37 Language and terminology -* ISO/TC 37/SC 4 Language resource management -* ISO/TC 37/SC 5 Translation, interpreting and related technology -* ISO/TC 46 Information and documentation -* ISO/TC 46/SC 4 Technical interoperability -* ISO/TC 46/SC 9 Identification and description -* ISO/TC 154 Processes, data elements and documents in commerce, industry and administration -* ISO/TC 211 Geographic information/Geomatics - -== General status and items from Conference XLV - -The Ad Hoc Committee on Rich Text (in Calendar events) formed at CalConnect XLIV completed its -work and disbanded prior to CalConnect XLV. - -A provisional Charter for a new TC USECASE was developed and will be completed this summer. - -The Charter for TC LOCALIZATION is nearly complete and should be reviewed and adopted in the near -future. - -CalConnect has approved as revised the IPR and Copyright policies and will formally adopt them -following this event. - -Feedback on the new conference format is very positive and we will continue with this model. - -TC PUSH has been reactivated to support movement of the specifications; the draft(s) will be -updated and resubmitted. - -TC-AUTODISCOVERY has been reactivated. A new draft will be published following the work on TC-PUSH. - -== Detailed Session Notes - -CalConnect Member Representatives should refer to the CalConnect XLV Conference Notes in the -Conferences/CalConnect XLV folder on the CalConnect Document Repository for detailed session notes -and information. - -== Plenary meeting - -CalConnect will hold two rather than three events in 2020: a spring event in April and an autumn -event in late September/early October. Several participants noted that this would definitely help -planning for an attending CalConnect events going forward. - -Strong interest in using Zoom in place of regular conference calls for committee calls; will try -with TCC and TC-DEVGUIDE calls following the event. - -Joint Working Group meeting with IETF CALEXT was successful. Plan to do another in conjunction -with CalConnect XLVI in October. Also plan on doing Working Group meeting with ISO/TC 154 working -group. - -Recommend referring to ourselves as "CalConnect" and not always add "The Calendaring and -Scheduling Consortium" as the latter doesn't reflect our full scope and future interests. - -== Confirmed Future Events - -* FastMail will host CalConnect XLVI on October 7-11, 2019 in Philadelphia, USA. - -* Cronofy will host CalConnect XLVII on April 20-24, 2020 in Nottingham, United -Kingdom. - -* CalConnect XLVIII will be in Autumn 2020, host, location and exact dates TBD. - -== Pictures from CalConnect XLV - -Pictures courtesy of Thomas Schäfer, 1&1. - -[%unnumbered,cols="a,a"] -|=== - -| [%unnumbered] -image::cc_45_hotel.jpg[] -| [%unnumbered] -image::cc_45_marten.jpg[] -| [%unnumbered] -image::cc_45_zoom.jpg[] -| [%unnumbered] -image::cc_45_dinner.jpg[] - -|=== diff --git a/sources/csd-report-conference-46.adoc b/sources/csd-report-conference-46.adoc deleted file mode 100644 index 2da963a..0000000 --- a/sources/csd-report-conference-46.adoc +++ /dev/null @@ -1,261 +0,0 @@ -= Report on CalConnect Conference XLVI, October 7-10 2019 -:docnumber: 1903 -:copyright-year: 2019 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2019-11-07 -:published-date: 2019-11-07 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:toc: -:stem: -:imagesdir: images/conference-46 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - - -:sectnums!: -== Introduction - -CalConnect XLVI took place October 7-10, 2019, hosted by Fastmail in Philadelphia, -Pennsylvania. The conference was held on Fastmail's premises, and was attended by -a total of 10 people from 7 member organizations, plus 7 attendees to joint virtual -working group sessions with the IETF CALEXT working group and with ISO/TC 154/ -WG 5. attendees. -The Conference focused on strategic and possible work items in addition to ongoing -work, and finished with the CalConnect Plenary Session on Thursday. The schedule -was rearranged during the week based on input from participants. The final pre-event -Conference agenda with notes on the discussion topics may be found at https://www.calconnect.org/events/calconnect-xlvi-october-7-11-2019#conference-schedule[CalConnect XLVI Conference Schedule]. - - -:sectnums: -== Status of Documents since Last Conference - -This is the status of documents as of June 2019 as more recent information was not -available when this report was prepared. There are no substantial changes at this point. - -Specifications in progress and not yet published are generally resident on GitHub either -in our public or private areas. - -=== Documents at CalConnect - -==== Published - -* CC/DIR 1005:2019 Guidelines for the implementation of the CalConnect Patent -Policy -* CC/R 18003:2019 Calendar operator practices - Guidelines to protect against -calendar abuse (TC CALSPAM) -* CC/DIR 10001:2019 CalConnect Directive: Standardization and publication -* CC/DIR 10002:2019 CalConnect Directive: Standard document requirements -* CC/DIR 10003:2018 CalConnect Directive: Patent policy - -==== Committee Drafts - -* CC/CD 51003 Series in iCalendar -* CC/CD 51004 iCalendar Relationships -* CC/CD 51005 Calendar Subscription Upgrades -* CC/CD 51006 Consensus scheduling - iCalendar vPoll component - -=== Documents at ISO - -* ISO/CC 19160-1 "Addressing -- Digital addresses" in working draft at ISO/TC 211 -* ISO/CC 34000 "Date and time -- Concepts and vocabulary" is under NWIP - -=== Documents at the IETF - -==== Published as Informational RFC - -* CalDAV Managed Attachments RFC 8607 - -==== Drafts in Final Review - -* Event Publishing Extensions to iCalendar (TC CALENDAR) - -==== Drafts in CALEXT Working Group Last Call - -* Improved Support for iCalendar Relationships (TC CALENDAR -* JSCalendar: A JSON representation of Calendar data - -==== Assigned to CALEXT WG - -* CalDAV extension for scheduling controls -* VLARM Extensions for iCalendar -* Calendar Subscription Upgrades - -==== Pending Assignment to CALEXT WG - -* VPOLL: Consensus Scheduling Component for iCalendar -* Support for Series in iCalendar - -== CalConnect Liaisons as of October 2019 - -CalConnect has formal reciprocal membership liaisons with M3AAWG and OASIS, a -strong working relationship with the IETF, and an External Cooperation Agreement with -the ITU-T. - -CalConnect has established formal Category A Liaisons with the following ISO -Committees: - -* ISO/IEC JTC 1/SC 27 IT Security Techniques -* ISO/PC 317 Consumer protection: privacy by design for consumer goods and -services -* ISO/TC 37 Language and terminology -* ISO/TC 37/SC 4 Language resource management -* ISO/TC 37/SC 5 Translation, interpreting and related technology -* ISO/TC 46 Information and documentation -* ISO/TC 46/SC 4 Technical interoperability -* ISO/TC 46/SC 9 Identification and description -* ISO/TC 154 Processes, data elements and documents in commerce, industry and -administration -* ISO/TC 211 Geographic information/Geomatics - -== General Status and Items from Conference XLIV - -=== TC-API - -Work on JSCalendar and related JSxxx documents is progressing very well. Work on -contact-related stuff in TC 211 and vCard has to be kept aligned and moving forward,, -probably via JSContacts. See references under other TCs to JMAP and JSCalendar/ -Contacts/etc. - -=== TC-AUTODISCOVERY - -Register MIME-type so a config could be email/etc and opening the attachment -triggers the client(s) to be configured. Others are very interested in the work. - -=== TC-CALENDAR - -Scheduling on Shared Calendars: We believe that Apple use Calendar User Proxy -(calendar-proxy capability) for handling secretary mode. Team sharing mode simply -acts on behalf of the principal associated with that instance of the calendar - -JMAP Calendars: Several edits to be made based on discussions. - -VPOLL: Update draft using PARTICIPANT component rather than VVOTER component. -Split BASIC mode specific bits into their own section describing BASIC mode. Publish -this draft ASAP unless we think we can add new poll mode(s) quickly. - -Second poll mode would be SIGNUP mode where a bunch of tasks need to be -handled and voters choose 1 or more that they are willing to complete (e.g. preparing -for and/or bringing items for a dinner party) - -Third poll mode would be the case of asking dentist office (or hairdresser or automotive -garage) for available time slots for a procedure - -Server-side subscriptions: Compare/contrast current draft with Apple telemetry. - -VALARM Extensions: Add RELATED-TO back in. Add text on security considerations -of proximity alarms. - -=== TC-DATETIME - -Working on developing a relative date/time notation based on ISO grammar. -Also would like to come up with a way to tag date/time values with calendar system, -time system, and time zone id. Working on human representation. Decide to create -proposals for ISO/TC 154 plenary. - -=== TC-LOCALIZATION - -Writing conversion system codes. Moving forward, will be the third pillar of the trio of -ISO 639 (language codes), ISO 15924 (script codes) and ISO 24229 (writing conversion -system codes). Romanization of Cantonese will be re-balloted for participation. Name -model proceeding in ISO/TC 37 pending ballot. Will accelerate solicitation/completion -of cultural profiles - -=== TC-PUSH - -Ask Chair to do the split of the draft and update with RFC 8030 references where -needed. Interest in writing a server implementations, but is there any realistic chance of -more client support? Need someone to review authentication/security. Align with -Open-Xchange work on IMAP WebPush. - -=== TC-USECASE - -Define 'client' early in charter. Deal with interoperability issues - more work on caldav -tester. Links to client libraries.. - -There was some discussion on incentives (reduced participant fee) for Open Source -developers at Zürich conference. Also an interesting point regarding to try draw -audience from the scientific community (e.g., inviting for scientific/industry paper -submissions related to CalConnect topics) -Decided to rename TC to TC-CLIENT - -=== TC-VCARD - -JSContacts: Discussion about how best to do localizations. 2 different approaches. -This will probably be hashed out in IETF JMAP WG once accepted - -No support for non-Westernized addresses yet. Specification of Groups needs more -work - -Document models: Lightweight document model for Markdown, AsciiDoc, RTF as -interchangeable rich text' - -Location vCard: Metadata for a location. vCard already contains "kind: location", and -defined STRUCTURED-LOCATION in resource vCard work. - -TC VCARD agreed to take over the joint work of OGC, ECCMA, W3C and ISO's work -on POI (point of interest) and develop with them as partners - -Enumerate use cases for industries: maps, navigation, travel, theme parks - -Will define method of place identification, including ISO 19155 (place identifier), -ECCMA/OGC NLI (ECCMA 1 standard) - -Find additional collaborators: IATA, UN (for LOCODE). - -Standardized profile and digital addresses proceeding. - -== Joint Working Group Calls - -The joint working group calls with IETF CALEXT and ISO/TC 154/WG 5 went very well. - -== Plenary Meeting - -CalConnect will hold two rather than three events in 2020: a spring event in April and -an autumn event in late September/early October. - -Interest in being involved in creating the scheduling agenda for future events; we plan -to distribute the calls to meeting for Event Planning to the general calconnect-l mailing -list and post event reports etc. on that list as well to try and get additional and early -involvement, beginning with Event Planning calls in November for CalConnect XLVII. - -== Confirmed Future Events - -* Cronofy will host CalConnect XLVII on April 20-24, 2020 in Nottingham, United -Kingdom. -* CalConnect XLVIII will be in Autumn 2020, host, location and exact dates TBD. - -== Pictures from CalConnect XLVI - -There were no pictures available from CalConnect XLVI. diff --git a/sources/csd-report-ioptestevent-26.adoc b/sources/csd-report-ioptestevent-26.adoc deleted file mode 100644 index a86f74d..0000000 --- a/sources/csd-report-ioptestevent-26.adoc +++ /dev/null @@ -1,108 +0,0 @@ -= Report on Interoperability Test Event XXVI, January 28-30, 2013 -:docnumber: 1303 -:copyright-year: 2013 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2013-02-20 -:published-date: 2013-02-20 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -NOTE: Incorporates material formerly distributed via the CalConnect _Minutes_ newsletter, now -discontinued. - -The Interoperability Test Event at CalConnect XXVI took place on January 28-30, 2013, hosted -by Oracle in Santa Clara, California. Nineteen people from 9 members were present onsite, -including 2 from Europe, 1 from India, and 1 from New Zealand. In addition 2 members -participated remotely. - -The interoperability testing sessions once again were busy and successful. Participants in person at -the event and their particular testing interests were: - -* Andrew McMillan (primarily aCal, some DAViCal) -* AOL (basic CardDAV and CalDAV functionality) -* Apple (CalDAV server testing iSchedule and IOS) -* Carnegie Mellon University (CMU testing iSchedule) -* Google (calendar auto-schedule, collection synchronization) -* Mozilla (basic CalDAV support in FirefoxOS, jCal being returned from CalDAV servers, -help with any jCal related interoperability) -* Oracle (test suite) -* Bedework (Rensselaer Polytechnic testing iSchedule) -* Yahoo! (CalDAV and CardDAV testing related to basic sync) - -There were two external participants: - -* Marten Gajda (basic CalDAV and CardDAV operation) -* Ralf Becker (testing iSchedule) - -As always many attendees were testing the basic and scheduling functions of CalDAV. Some were -working on new CalDAV implementations, others were dealing with known interoperability issues -or bringing their server up to date with the specifications. At least one production server was -updated as a result of the testing. - -A group of participants spent most of their time working on iSchedule. This protocol allows -scheduling of meetings across domains and includes service discovery and a security model based -on DKIM. This time there was a new DKIM canonicalization to test. The test was successful with -events and freebusy being transferred in both directions. Most problems encountered were related -to the non-standard disposition of the servers and self-signed certificates. There are now at least -four implementations up to the latest draft which are capable of working with each other. - -There was some work in getting the Apple CalDAV test and performance suites running against -servers. The test suite is invaluable for discovering basic CalDAV problems but requires some -configuration to handle the server details. The developer was present to help get this running. - -A new timezone service draft specification has been released which switches from an XML based -protocol to JSON. At least one server tested updating its data against the Bedework timezone -server and a version of aCal successfully retrieved timezones from the Bedework server. - -A useful feature of the sessions was the occasional informal discussions which involved most of -the participants. This time we covered some of the detailed issues related to calendar sharing and -notifications. - -In future events we hope to be testing at least the following: - -* The usual CalDAV testing -* More iSchedule -* Implementations of the CalWS protocols being developed in conjunction with OASIS -* Different representations of calendar data such as JSON and XML -* Calendar sharing -* Notifications -* Managed attachments - -Additionally we are investigating the possibility of bringing a portable virtual network which will -provide a more standard setup for servers in regard to ports and certificates and allow participants -to test without significant changes to their network settings. diff --git a/sources/csd-report-ioptestevent-27.adoc b/sources/csd-report-ioptestevent-27.adoc deleted file mode 100644 index 38fbb5e..0000000 --- a/sources/csd-report-ioptestevent-27.adoc +++ /dev/null @@ -1,119 +0,0 @@ -= Report on Interoperability Test Event XXVII, June 3-5, 2013 -:docnumber: 1305 -:copyright-year: 2013 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2013-07-10 -:published-date: 2013-07-10 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The interoperability test event at Calconnect XXVII, hosted by The University of Wisconsin, -Madison, Wisconsin took place on Monday June 3rd through Wednesday morning June 5th. - -There were 6 organizations participating and 1 observing represented by 13 attendees. Those -participating were: - -* AOL - mostly CalDAV related -* Apple - mostly CalDAV and VPOLL -* RPI with Bedework testing VPOLL support -* Andrew MacMillan mainly aCal -* Carnegie Mellon University - CalDAV and iSchedule -* Mozilla - FirefoxOS - -Our host, the University of Wisconsin, weres present as observers. - -All of the participants have CalDAV working to a greater or lesser extent and some of the focus is -shifting to the newer extensions to CalDAV such as calendar sharing and notifications. While these -specifications have not yet been finalized and published as standards they are sufficiently -interesting and valuable that vendors and developers want to work on them now - perhaps -influencing the final standardized form of the features. - -CalDAV calendar sharing allows CalDAV users to share their calendar collections with other users -on the system and notifications provide a mechanism for informing clients of changes to -collections and invitations to share collections. - -VPOLL is a new calendaring specification which standardizes data for consensus scheduling -(voting on alternatives) - the type of service provided by Doodle and others. VPOLL will allow -these external services to interact with calendaring systems in a more standardized manner and -also enables the support of such services within existing systems. So far there are implementations -working on CalDAV servers which distribute the VPOLL component to voters and handle the -responses. - -Some of the participants worked on getting the Apple test suite (which tests mostly CalDAV -conformance) and the Apple performance test suite (which emulates the load caused by existing -clients) running against their own servers. - -There was also some testing which revealed issues with timezones - mostly related to the -particular aliases being used. This has some implications for the provision of aliases by timezone -servers. - -A newer feature of the event is the planned discussion sessions - putting aside time to discuss -features at a level interesting to developers. - -Calendar sharing is one such feature which kept reappearing at different times throughout the -testing session and into the round table. - -Calendar user addresses was another issue which caused much discussion, which also spilled over -into the Roundtable. Service suppliers are concerned about the issues raised by the use of a single -identifier, usually an email address, for services not supported at that email domain. When sending -invitations to attendees it is not clear where the invitation should go and the fallback of using -email is not altogether satisfactory. This topic has significant implications for iSchedule. - -We also had some discussions on the form of the interoperability test event itself and will be -discussing this leading up to the next event in Prague this fall. At the very least we expect that we -will spend more time at the start of the event, and perhaps each morning, discussing participants -needs and pairing them up with other participants to help get them off to a fast productive start. - -The technical discussions which took place reinforced our understanding that these events are -valuable, not just for the opportunity to test servers, clients and libraries but also for the -opportunity for extended discussions on implementation details with those who are further down -the development path or running deployed features. - -In future events we hope to be testing at least the following: - -* The usual CalDAV testing -* More iSchedule -* Implementations of the CalWS protocols being developed in conjunction with OASIS -* Different representations of calendar data such as JSON and XML -* Calendar sharing -* Notifications -* Managed attachments -* VPOLL -* Basic iCalendar/iTIIP/iMIP as needed - -Mike Douglass, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-28.adoc b/sources/csd-report-ioptestevent-28.adoc deleted file mode 100644 index 4dad355..0000000 --- a/sources/csd-report-ioptestevent-28.adoc +++ /dev/null @@ -1,106 +0,0 @@ -= Report on Interoperability Test Event XXVIII, September 23-25, 2013 -:docnumber: 1307 -:copyright-year: 2013 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2013-10-24 -:published-date: 2013-10-24 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The interoperability test event at CalConnect XXVIII, hosted by DHL, Prague, Czech Republic -took place on Monday September 23 through Wednesday morning September 25. - -There were 10 members participating and 1 non-member represented by 14 individuals onsite; one -member tested remotely. Participating were: - -* Andrew McMillan - mostly aCal -* Apple - Prefer, JSON, new VTODO/TC-Tasks stuff, CalDAV Tester tweaks -* BusyMac (BusyCal) - managed attachments, timezones by reference, general compatibility -* fruux (SabreDav) - Calendar-auto-schedule and jCal -* Marten Gajda - basic CalDAV and CardDAV operation -* Oracle - tasks, timezones, iMIP -* Softly Software (WhenIsGood/YouCanBookMe) - primarily Google Calendar APIs -* Stylite - eGroupware data synchronization and managed attachments -* RPI (Bedework) - iSchedule, CalDAV, VPOLL, JSON -* Mozilla (Lightning) - jCal, jCard -* Zimbra - CalDAV and iMIP server-server - -A major area of interest was testing the new jCal specification (and jCard). The development -version of Mozilla Lightning has support for jCal and was tested against a number of CalDAV -server implementations. This tested not only the representation but the CalDAV extensions to -handle different formats. Add, Modify, Delete and Freebusy requests worked well with most -servers. - -Cyrus Daboo headed a session in which he demonstrated setup and use of Apple's CalDAV tester. -This tester sends sequences of requests to the server and analyzes the responses and the resulting -state of the server. It offers many test suites which test from the most basic of CalDAV interactions -through to complex recurrences and scheduling of meetings. It is very configurable, and will work -to some extent with any CalDAV server. The testing at the event revealed a few changes that -would be useful. - -Managed attachments is a new CalDAV feature. A number of servers and clients have -implementations and there was a certain amount of testing. This triggered some further discussion -about the specification. - -The TIMEZONE Technical Committee committee has been looking at the possibility of dropping -the timezone specification from the iCalendar data (i.e. "timezones by reference"). The advantage -is a significant reduction in data size. It appears that most implementations ignore the specification -sent to them. A number of us tested the effects of dropping the specification, both on clients and -servers. We did this as part of testing the new CalDAV extensions which allow clients and servers -to indicate whether or not they need or will send the timezone. The tests were mostly successful in -that there was no apparent differences in behavior. There was one case of a validation error. - -There was some VPOLL testing which included testing of a javascript client for consensus -scheduling. This client revealed some issues in the use of cross-domain requests with CalDAV and -may result in some renewed interest in a RESTful API. - -As usual, we had a certain amount of testing of basic calendaring including CalDAV and iMIP. -There was some further testing of the PREFER header and alarms. Some long standing issues with -working with Google were resolved for one of the attendees and turned out to be a stray CR/LF in -RRULEs. - -As usual there was a significant amount of discussion taking place reinforcing the view that these -events are not just for testing but for reaching a better understanding of protocols and their -implementations. These discussions can also lead to changes to specifications and are a useful -adjunct to the usual technical committee calls. - -For the next session in February we expect to be testing many of these features again. We expect -more implementations of jCal, VPOLL and managed attachments. There is also likely to be some -testing of notifications and sharing. - -Mike Douglass, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-29.adoc b/sources/csd-report-ioptestevent-29.adoc deleted file mode 100644 index 83eaa74..0000000 --- a/sources/csd-report-ioptestevent-29.adoc +++ /dev/null @@ -1,103 +0,0 @@ -= Report on Interoperability Test Event XXIX, February 3-5, 2014 -:docnumber: 1402 -:copyright-year: 2014 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2014-02-28 -:published-date: 2014-02-28 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The interoperability test event at CalConnect XXIX, hosted by Mozilla, San Francisco, California -took place on Monday February 3 through Wednesday morning February 5. - -There were 11 members participating onsite represented by 20 individuals; two members -participated remotely. Participating were: - -* AOL - CalDAV Scheduling -* Apple - iCloud, iCal Client, Calendar Server -* BusyMac - remote testing -* CMU - CalDav Scheduling, timezone service, jCal/xCal, test suite (load testing) -* Marten Gajda - remote testing - sync-collection CalDAV & CardDAV, managed -attachments, PUSH notification -* Milton.io - general testing, CardDAV with clients -* Mozilla - Firefox OS/CalDAV -* Oracle - CalDAV Scheduling, iMIP, CardDAV -* Ribose - CalDAV access and scheduling, CalDAV sharing, CalDAV Tester -* RPI - VPOLL - test suite - sharing and notifications -* Softly Software - Basic CalDAV and iCalendar -* University of Wisconsin - mostly observing -* Yahoo! - CardDAV, CalDAV - -As usual there was a lot of testing of basic CalDAV features. Some client applications are -developing CalDAV support and there are some newer server implementations that need to test. - -As we did at the last event we had a session led by Cyrus Daboo describing the CalDAV test suite -and updates he had recently made to address some issues raised. Newer issues are related to using -the test suite in an automated test environment and defining a subset of the tests which check the -basic functions of CalDAV and CalDAV scheduling. The full test suite checks out many obscure -issues, often related to recurrences. The session helped get some of the server implementors -successfully running the test suite. It is expected that we will do more work on developing this -suite during the next event. - -There was some more testing of the timezone server specification which has had some minor -updates since the last interoperability test event. This resulted in some further changes to the -specification. A new feature of the specification is the ability to request and deliver truncated -timezone specifications, allowing for much smaller sets of data to be transferred. There was some -testing of this feature and some minor fixes resulted. - -There was some further testing of the new JSON jCal and JCard specifications and some parsing -problems were resolved - mostly in recurrence rules. - -Some of the client developers tested some of the more awkward calendar issues such as uploads of -medium to large sets of data which revealed problems in a number of server implementations. - -The tests revealed many issues relating to the parsing and delivering of iCalendar data which are -difficult to spot in production systems, such as: - -* Incorrect escaping of GEO values causing server exceptions -* Clients generating invalid end dates and server not handling them correctly -* Events with attendees but no ORGANIZER -* Failures during calendar creation due to unsupported properties - -The testing and resulting fixes generally result in more robust systems that react better to invalid -data being presented - as well as, we hope, less invalid data. - -Some of the new clients were able to test against a range of the servers available and reassure -themselves that the clients were able to deal with most of the basic CalDAV features. - -Mike Douglass, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-30.adoc b/sources/csd-report-ioptestevent-30.adoc deleted file mode 100644 index a25849e..0000000 --- a/sources/csd-report-ioptestevent-30.adoc +++ /dev/null @@ -1,91 +0,0 @@ -= Report on Interoperability Test Event XXX, May 19-21, 2014 -:docnumber: 1404 -:copyright-year: 2014 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2014-06-09 -:published-date: 2014-06-09 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The interoperability test event at CalConnect XXX, hosted by AOL in Dulles, Virginia took place -on Monday May 19 through Wednesday noon May 21. - -There were 8 members and one non-member participating onsite represented by 12 individuals. In -addition two members participated remotely. Participating organizations and primary testing -interests were: - -* 1and1 - basic CalDAV testing -* AOL - Calendar sharing, basic caldav and carddav -* Apple - iCloud, iCal Client, Calendar Server - VPOLL and iSchedule -* BusyMac - CardDAV Sharing, SCHEDULE-AGENT=CLIENT, General CalDAV and -* CardDAV client compatibility testing with multiple servers -* CMU - VPOLL and iSchedule -* fruux - SabreDAV -* Marten Gajda - CalDAVSync and CardDAVsyncGeneral CalDAV & CardDAV, service -discovery -* Mozilla - Firefox OS/CalDAV basic features for laptop and phone -* Ribose (remote) -* RPI - Bedework iSchedule and VPOLL -* Zimbra (remote) - -Once again there was the usual testing of basic CalDAV features. Some client applications are -developing CalDAV support and there are newer server implementations that need to test. Most -errors found are minor and were generally fixed during testing. - -Three of the server implementations (Apple, CMU and RPI/Bedework) worked on setting up a -demonstration of a combination of VPOLL, iSchedule and jCal. All used a javascript client which -communicates with the server using CalDAV and the new jCal calendar representation. Each -server communicated with the other server(s) via iSchedule. There were changes to all servers as a -result and there was a successful demonstration of all 3 servers working together as part of the TC -FREEBUSY session on Thursday. - -Some of the later features of DAV and CalDAV were tested: - -* Sharing - more clients and servers are developing support for this feature. Issues such as the -interaction with supported component sets were discovered and fixed. There has been more -interest lately in address-book sharing and there was some testing in this area -* Synch - more testing of this feature as clients and servers add support -* Scheduling - general testing of this - some servers and clients are adding support - -The testing was fairly intensive after the initial pairing off of clients and servers. Once again the -result is enhanced interoperability across many systems. - -Many thanks to AOL for hosting this event. The configuration of the room and networks was -trouble-free allowing all participants to make an immediate start. - -Mike Douglass, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-31.adoc b/sources/csd-report-ioptestevent-31.adoc deleted file mode 100644 index d5208ed..0000000 --- a/sources/csd-report-ioptestevent-31.adoc +++ /dev/null @@ -1,85 +0,0 @@ -= Report on Interoperability Test Event XXXI, September 29 - October 1, 2014 -:docnumber: 1407 -:copyright-year: 2014 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2014-10-31 -:published-date: 2014-10-31 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The interoperability test event at CalConnect XXXI, hosted by Youcanbook.me in Bedford, -United Kingdom took place on Monday September 29 through Wednesday noon October 1. - -There were 10 members participating onsite represented by 14 individuals. In addition two -members participated remotely. Participating entities and primary testing interests were: - -* 1and1 - basic CalDAV testing -* Apple - Calendar Server: timezone distribution, VPOLL and iSchedule; IOS8 -* Bedework - VPOLL and timezone distribution -* CMU - VPOLL and iSchedule -* fruux - SabreDAV -* Helge Hess - individual testing support -* Mozilla - Lightning CalDAV, jCal and jCard -* SmoothSync - CalDAVSync and CardDAVsync, General CalDAV and CardDAV, service -discovery -* Youcanbook.me - Google Calendar and general CalDAV -* Zimbra - CalDAV auto scheduling - -As always, many were testing basic CalDAV features with some starting to test their -implementations of CalDAV implicit scheduling. A number of errors were found and fixed and in -some cases discussions resolved misunderstandings of the protocols. - -Three of the server implementations attempted to set up a demonstration of a combination of -VPOLL, iSchedule and jCal between them. Ultimately this wasn't achieved - mostly due to the -problems of setting up remore servers with certificates and getting DKIM to work correctly. There -were changes to all servers as a result and there was a local demonstration of the current state of -the Bedework VPOLL client during the TC FREEBUSY session. We hope to have a full working -demonstration with multiple servers by CalConnect XXXII. - -The testing was fairly intensive after the initial pairing off. Testers were busy throughout the -event. - -Once again we had some BOF sessions -- this time we discussed the issues around task assignment -in VPOLL and providing server information to clients as a fetchable document. These discussions, -usually at the developer and implementor level, have become a valuable part of the experience. - -Many thanks to Youcanbookme for hosting this event. The configuration of the room and -networks gave no trouble allowing all participants to make an immediate start. The catering for -this event was excellent. - -Mike Douglass, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-32.adoc b/sources/csd-report-ioptestevent-32.adoc deleted file mode 100644 index 10187f3..0000000 --- a/sources/csd-report-ioptestevent-32.adoc +++ /dev/null @@ -1,110 +0,0 @@ -= Report on Interoperability Test Event XXXII, January 26-28, 2015 -:docnumber: 1502 -:copyright-year: 2015 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2015-02-18 -:published-date: 2015-02-18 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The interoperability test event at CalConnect XXXII, hosted by Kerio Technologies in San Jose, -California took place on Monday January 26 through Wednesday noon January 28. - -There were 13 members and 1 non-member participating onsite represented by 24 individuals. -Participating entities were: - -* 1and1 -* AOL -* Apple -* BusyMac -* CMU -* fruux -* Google -* Kerio Technologies -* Microsoft -* Novell -* Oracle -* RPI (Bedework) -* SmoothSync -* Zimbra - -This included a good range of participants, with some mature client and server implementations -and new clients and servers. - -As usual there was a significant amount of testing basic features of CalDAV, and this time there -was increased interest in testing CardDAV. The topics tested included - -* General CalDAV and CalDAV scheduling -* Basic CardDav -* auto discovery -* sharing of calendars and contacts -* Server information document -* server test suite -* iTip and iMip -* extended-mkcol support -* VAVAILABILITY -* RSCALE - enable recurrences in different calendar scales -* VPOLL -* TZdist - the timezone distribution protocol -* Timezones by reference -* iSchedule -* jCal -* Push Notifications - -A number of server implementors worked on getting the CalDAV Tester test suite running. This -suite tests most of the features of CalDAV and CardDAV. - -Three of the attendees tested implementations of VPOLL, a new standard for consensus -scheduling, both clients and servers and were later able to demonstrate three servers and clients -interacting through iSchedule. All three clients use javascript CalDAV implementations and the -jCal (iCalendar in JSON) format. - -There was a significant amount of testing iMip between Exchange and various other servers and -clients. A number of issues were identified which may lead to better interoperability in the future. - -Once again we featured a number of discussions on various topics. These discussions may take -place in the main room if sufficient attendees are interested or as smaller breakout sessions and -usually cover lower-level protocol and implementation issues. Topics covered this time included: - -* managed attachments -* the new push notification specification -* delivering events through other means - e.g qrcodes -* iMip and how to improve it -* open source issues - -Mike Douglass, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-33.adoc b/sources/csd-report-ioptestevent-33.adoc deleted file mode 100644 index b865d6e..0000000 --- a/sources/csd-report-ioptestevent-33.adoc +++ /dev/null @@ -1,92 +0,0 @@ -= Report on Interoperability Test Event XXXIII, May 18-20, 2015 -:docnumber: 1504 -:copyright-year: 2015 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2015-06-23 -:published-date: 2015-06-23 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The interoperability test event at CalConnect I, hosted by 1&1 in their Bucharest, Romania office, -took place on Monday May 18 through Wednesday noon May 20. The facilities were excellent -and allowed all participants to begin testing immediately. - -There were 6 members participating onsite represented by 12 individuals. Participating entities -were: - -* 1&1 (the hosts) -* Apple -* fruux -* Google -* RPI (Bedework) -* YouCanBook.me - -As is usual we spent some time on discussions - during the interoperability event these are often of -a more technical and protocol oriented nature. These can involve the group as a whole or take the -form of small break out discussions with a subset of the attendees. A brief discussion on API -issues led to the decision that Evert Pot of fruux would produce some proposals for us to look at -during the conference. - -Following on from some previous testing there was a discussion on iMIP issues. Cyrus Daboo of -Apple talked about his proposed mail header to identify calendar content in mail messages. - -There were also some discussions about the overall approach of CardDAV and in particular how to -implement groups and how this would affect sharing. There was also some discussion about the -CardDAV tests available in the Darwin calendar server test suite. - -YouCanBook.me felt this was "a really valuable session of testing". Their service effectively acts -as a client to a number of online calendar services and they carried out a significant amount of -testing against those services. In particular they were carrying out final testing of their new -CalDAV link which is now working well with fruux, iCloud and 1&1. Additionally: - -* They improved their detection of the primary calendar status through CalDAV and are now -filtering out non-VEVENT calendar collections properly -* They fixed a number of URL illegal character bugs and worked with fruux to signal their -fruux interface -* They tuned the PROPFIND calls for 1&1 and identified a missing slash issue -* They built a new link through to iCloud and logged a bug to do with descriptions on -MKCALENDAR calls - -The other big step forward for YouCanBook.me was talking to everyone about the main status -property at the VEVENT level - in particular for "tentative" status. This is something they hope to -use, but need more support from clients. They expect to file bug reports or feature requests on this -topic in the coming months. This, of course, is a feature which will be of use to many others. - -As always, the result for many of the server developers were a number of bug fixes. - -Mike Douglass, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-34.adoc b/sources/csd-report-ioptestevent-34.adoc deleted file mode 100644 index 35c4b59..0000000 --- a/sources/csd-report-ioptestevent-34.adoc +++ /dev/null @@ -1,93 +0,0 @@ -= Report on Interoperability Test Event XXXIV, Sep 28-30, 2015 -:docnumber: 1505 -:copyright-year: 2015 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2015-10-19 -:published-date: 2015-10-19 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The September 2015 Calendar Interoperability event took place in Amsterdam, Netherlands -hosted by Gershon Janssen. - -There were 9 members participating onsite represented by 12 individuals. Participating entities -were: - -* 1&1 (the hosts) -* Apple -* Mozilla -* Oracle -* Spherical Cow Group (Bedework) -* SmoothSync -* Stylite -* YouCanBook.me -* Zimbra - -Additionally present were Gershon Janssen, the host, and as ever Dave Thewlis, Executive -Director. - -There was the usual testing of CalDAV as a number of participants continue to implement features -of that protocol. There were a number of client implementations at the event which allowed for -fairly extensive testng. - -In addition to the usual testing of protocols we had other items which occupied our time: - -There was a lot of interest in the new WebDAV server info document -(https://tools.ietf.org/html/draft-douglass-server-info). This allows clients to determine what -features are available from a service and to cache the information. It allows us to reduce the -number of headers being transferred and also allows for more complex information and a way for -servers to indicate the feature set has changed. We had implementations from 3 servers and 2 -clients - all done during the meeting. The specification went through a number of rapid iterations -as we built the code. - -We had planned for some work on the Apple CalDAV test suite to try to improve its usability in -continuous testing environments. Ralf Becker of Stylite developed at the meeting a php tool which -creates a SQLite database of test results and also provides a number of querying options. This -work will probably continue between meetings and we will revisit it at the next event. - -There were a number of discussions that took place during the event. For previous sessions we had -tried to move these discussions to a separate room away from the main testing venue. However, -we have come to realize that these discussions are of some interest to all participants and that they -often provide unexpected insights. For the near future at least we will probably have these -discussions as part of the main event. Topics covered the server information document, the new -devguide work and possible extensions. - -Once again, this has been a useful event for the participants. Our thanks go to Gershon Janssen for -hosting the event and his attentiveness during the testing. - -Mike Douglass, Spherical Cow Group, CalConnect Interoperability Test Manager diff --git a/sources/csd-report-ioptestevent-35.adoc b/sources/csd-report-ioptestevent-35.adoc deleted file mode 100644 index 512f1bc..0000000 --- a/sources/csd-report-ioptestevent-35.adoc +++ /dev/null @@ -1,77 +0,0 @@ -= Report on CalConnect Interoperability Test Event XXXV, January 11-13, 2016 -:docnumber: 1602 -:copyright-year: 2016 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2016-02-17 -:published-date: 2016-02-17 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The Calconnect interoperability event was hosted by AOL at their Palo Alto site on -January 11th through the morning of the 13th. - -While it was a smaller than usual event much valuable work took place. There was the -usual mix of in-depth discussions and actual testing of implementations. - -On the testing front there was: - -* Work on the server-info document -* CalDav Tester -* Ralph Beckers caldav tester scripts -* General CalDAV - -The server-info document is a new specification being developed to provide cacheable -server information for use by clients, detailing services available and some limits. -This has been implemented by a number of servers and some clients. Each -interoperability event has led to changes in the specification. The general feeling -is that it is now ready for wider testing and use. - -The CalDAV tester is associated with Apple's Darwin open source server offering and -provides many tests of CardDAV, CalDAV and related features. It is very configurable. -Ralph Becker's tool helps to run the tests and store results. - -While historically, this has been an event focusing on interoperability testing we -have been moving towards having more in-depth, developer-centric discussions on -topics of interest. - -This event was no exception with discussions on all of the above topics as well as -how best to move forward with the new developers guide. - -We are looking forward to being back to our usual larger attendance at Hong Kong in -April. Check the website over the coming weeks as we will be updating the schedule to -reflect the specific interests of the attendees. diff --git a/sources/csd-report-ioptestevent-36.adoc b/sources/csd-report-ioptestevent-36.adoc deleted file mode 100644 index 395112d..0000000 --- a/sources/csd-report-ioptestevent-36.adoc +++ /dev/null @@ -1,191 +0,0 @@ -= Report on CalConnect Interoperability Test Event XXXVI, April 18-19, 2016 -:docnumber: 1604 -:copyright-year: 2016 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2016-05-31 -:published-date: 2016-05-31 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The Calconnect interoperability event was hosted by Ribose and OGCIO at Cyberport in -Hong Kong on April 18 and 19, 2016. - -The event at HongKong continued our move to a more forum like approach, combining -testing of new and standard calendar features with a number of in-depth discussions. - -The following organizations were attending - -* dmfs GmbH (formerly SmoothSync) -* FastMail -* Fruux -* Google -* Open-change -* Philipp Gewischt -* Ribose -* Spherical Cow Group - -A major topic for this event - as for the last one - is trying to make iMip more -reliable. In some cases it is the representation of the data which is the issue, -other times it is incorrect handling of iTip. - -Another topic which keeps coming back is dealing with differing interpretations of -the iCalendar specification regarding recurrences. - -== Discussions and issues raised - -During discussions a number of issues were raised. These included: - -=== Timezones - -Do servers handle timezone definition changes - e.g. recalculate recurrences based on -new timezone: the answer is usually not. - -=== VJOURNAL - -There was a proposal for adding an additional status to indicate "ARCHIVED" - -Suggested alternatives: use different collection, or perhaps a structured category -(this is also backwards-compatible, as opposed to a new status) - -There is also a lack of rich text support - but that's also true for events and tasks -- this should also be addressed - see "Styled-Description" in -https://www.ietf.org/archive/id/draft-douglass-calendar-extension-04.txt - -The general feeling is that JOURNAL is not heavily used. - -=== Managed attachments - -Problem: we cannot add an attachment right away together with an event with managed -attachments - we would have to first add an event, than once it synced and we know -the uid we can add an attachment. - -=== Support for wiping devices (Raised by Marten from dmfs) - -Do we need a special operation? - -The way to go is to use per-device passwords (or OAuth to get device-specific -markers) and return empty collections on the first sync. - -This last point led to a discussion on client authentication and whether we could -perhaps support open connect. See - -* https://tools.ietf.org/html/rfc7591 -* http://openid.net/connect/ - -== New API discussion - -There is a new format proposal: https://github.com/CalConnect/API/blob/master/CalendarEvent.mdwn - -Some of the api issues that were discussed were - -* Structured location & structured data - -* Alerts and defaults support, have a separate field for defaults - -* isAcknowledged - as currently is it would cause gradual expansion of alerts on the -instances; solution: make isAcknowledged store not boolean but the last recurrence -instance for which the alert was acknowledged, and only store it on the base range, -not on the instances (unless the instance has override alerts). - -* Attachments - -* Multi-language support - to group localizations under a "localize" component - -* Custom properties representation - -** Should we use a special prefix (like the X-)? The problem is that once use of a -property is widespread enough a property's custom name is "cut in stone", since -everyone's using it. - -** Maybe a special string namespace/registry with easy way of claiming? - -** URLs (with domain names)? - -On recurrences there was a discussion on the idea of excluding certain instances -based on another event(s) - -The start and end timezones are expressed through locations: first one corresponds to -start, last - to end. The event timezone is independent. - -== Issues found during testing - -These included: - -Missing timezones in ICS for single events. - -When the recurrence rule doesn't match the first start then some services silently -move the first start to the first actual occurrence (which seems reasonable) - -Moving a recurring instance into a different day did not work correctly. - -Timezone customization is not set for events (at least recurring) sent through iMIP -(although the timezone is saved). - -Some clients were mishandling sequence numbers - -Create a recurring event in the future, save and send invitations - -* "Add to Calendar" set a response, e.g. Yes -* Move an exception to a different time (again, send updates) -* "Update Calendar" set a response, e.g. Maybe -* Result: the response is discarded as outdated - -Some servers don't send invitations for past events even when the user is explicitly -asked whether to send or not and says yes. - -There were problems with autodiscovery - -Some issues discovered and questions about Android clients: - -* may only sync 1 year of data -* attachments first appear and then disappear again -* Is CalDAV syncing support in the future? -* Android is missing new features or bugs, e.g.: -** bad recurrence expansions -** empty recurring events (when all instances are cancelled) - -Client iMip bug: invitations to single instances of a recurring event are not handled -properly - -Server iMip bug: -Have a recurring event with one exception moved, then invite an attendee - the -invitation only contains the series but not the exception - -An interesting fact was noted: for recurring events where the recurrence doesn't -match the start date - between Apple, FastMail, Google and Open-Xchange these are all -expanded differently (3 different behaviors). diff --git a/sources/csd-report-ioptestevent-37.adoc b/sources/csd-report-ioptestevent-37.adoc deleted file mode 100644 index 8536874..0000000 --- a/sources/csd-report-ioptestevent-37.adoc +++ /dev/null @@ -1,113 +0,0 @@ -= Report on CalConnect Test Event and Developers Forum XXXVII, September 12-14, 2016 -:docnumber: 1606 -:copyright-year: 2016 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2016-10-07 -:published-date: 2016-10-07 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The event was hosted by dmfs in Dresden, Germany, on September 12-14, 2016. - -The participants in this event were: - -* 1and1 with 5 attendees -* dmfs - Marten Gajda - the hosts -* FastMail with 3 attendees -* Google -* Ralf Becker -* SCG -* Zimbra - -While interoperability testing is still an important part of the proceedings, this -event provides an opportunity for developers to discuss issues at depth. Some of the -major discussions are detailed below but the event provides an opportunity for -developers to ask questions of each other and often resolve their problems. - -CalDAV has usually been a major part of our testing. New CalDAV clients and servers -continue to appear and we hope the work we are doing on a version of the CalDAV -tester will promote interoperability. Of late there has been an increased interest in -other issues such as iMIP and there was some work on interchanging iMIP messages. - -There was a significant amount of work on versions of ical4j to incorporate changes -to support VPOLL. There was some discussion on how to merge the many different forks -of that library and this may lead to some future calls. - -The new JSON format being developed by TC-API was discussed. There were a number of -outstanding issues that needed resolving. These were all dealt with so that we are -ready to move forward with an implementable specification. Additionally a tool for -converting between iCalendar and the new JSON format developed by FastMail was made -available. This allowed us to see how events would look in the new representation. - -We talked about the latest draft of the icalendar patch document. This allows changes -to iCalendar objects to be expressed as a patch which may be much smaller than -sending the entire entity. We spent some time discussing issues around selecting -components, especially for icalendar streams and ultimately felt that we were ready -to move forward with implementations. - -We also took a look at the new VINSTANCE component which allows for a much more -compact representation of overrides - essentially only showing the difference between -the generated instance and the overridden form. This again should be much more -compact than the current approach. This proposal led to a further proposal - that we -bump the iCalendar version number which has been at 2.0 since RFC2445. VINSTANCE -introduces a change which may cause clients and servers to lose overrides if they -don't support it. Incrementing the version number - along with a possible use of -feature negotiation - would allow us to ensure that new features are supported. - -Marten Gajda presented some thoughts on Autodiscovery and we intend moving along with -that specification in some future calls. - -There was more discussion on iMIP and this should lead to some documentation in the -developers guide on how to format iMip messages to avoid problems. - -There was also some work on the developers guide. We have been merging in older -sources of information. caldav.calconnect.org and carddav.calconnect.org were 2 such -targets and all the information from those sites is now represented as pages in the -devguide. - -We spent some time talking about how to make the Apple CalDAV Tester testing suite -more accessible to developers. There are very many tests available but it is -currently a daunting prospect to get this running and many tests fail because of -Apple specific issues. We decided to fork a version into the calconnect repository -and try to come up with a subset of test newer developers can use. Additionally we -talked about the ability to disable specific tests. To help with this Ralf Becker has -implemented a wrapper which keeps track of the tests run and the results. This now -has a gui interface. This wrapper is also in the calconnect repository. - -Looking forward we hope that a combination of the developers guide and the test suite -will lower the bar for application developers. diff --git a/sources/csd-report-ioptestevent-38.adoc b/sources/csd-report-ioptestevent-38.adoc deleted file mode 100644 index c1c9d9b..0000000 --- a/sources/csd-report-ioptestevent-38.adoc +++ /dev/null @@ -1,95 +0,0 @@ -= Report on Test Event and Developers Forum XXXVIII, February 13-15, 2017 -:docnumber: 1702 -:copyright-year: 2017 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2017-03-10 -:published-date: 2017-03-10 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The event was hosted by the University of California, Irvine, in Irvine California on -February 13-15, 2017 - -The participants in this event were: - -* 1and1 -* AOL -* Apple -* FastMail -* Google -* SCG (Bedework) -* Zimbra - -There were a number of areas some or all of us were interested in pursuing. These -included: - -* For the Java people bringing ourselves up to date with the latest ical4j -* Coming up with a way of handling updates to the caldav tester suite. -* Discussions on developer guide directions - -There were the usual crop of issues that attendees wanted to address. iMIP has been a -major topic lately and the forum provided an opportunity for some members to deal -with problems they had been experiencing. - -Ical4j has been the topic of much discussion for some months. We used this session as -an opportunity to work on bringing ourselves up to date with the latest version - or -at least investigating how much work it would be. 1&1, Bedework, Zimbra and AOL were -present and are users of iCal4j. In the coming months we will discuss what changes we -would like to see made to that library. - -At the Dresden meeting we decided to create a CalConnect fork of the Darwin CalDAV -tester and work on some of the tests to make them more usable for non-Apple servers. -In the intervening period some changes were proposed and we spent some time this -meeting discussing how we might get these changes merged back into the CalConnect -fork. The intent is to come up with a subset of tests that any server developer -should be able to run and expect to get a 100% success rate. A number of us have -localized versions of the tester and we would like to merge many of these changes -into the CalConnect version so that they can benefit everybody. - -The meeting was a chance to carry out some of the internal changes to the developer -guide that had been contemplated. These should make it easier to organize the content -in the future. - -There was further discussion on the new data model being worked on by TC API and its -JSON representation. - -We also spent some time talking over the issue of calendar spam and how this differs, -if at all, from email spam. This allowed us to collect our thoughts ready for a wider -discussion in the conference that followed. While calendar spam has not been a major -ongoing issue it has already caused some problems and we need to be ready to deal -with the inevitable. diff --git a/sources/csd-report-ioptestevent-39.adoc b/sources/csd-report-ioptestevent-39.adoc deleted file mode 100644 index b28fc9a..0000000 --- a/sources/csd-report-ioptestevent-39.adoc +++ /dev/null @@ -1,83 +0,0 @@ -= Report on Test Event and Developers Forum XXXIX, June 12-14, 2017 -:docnumber: 1704 -:copyright-year: 2017 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2017-07-21 -:published-date: 2017-07-21 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The event was hosted by Tandem in Seattle, Washington on June 12-14, 2017 - -The interoperability test event and developers forum had a relatively small number of -attendees. While this led to little actual testing we did spend our time discussing -some of the intricate details of work that is in progress. - -In attendance were: - -* Tandem (our hosts) -* Spherical Cow Group with Bedework -* Eventable -* FastMail -* Ribose - -There was discussion of how to deal with categorization for the new data model and -representation being developed in TC-API. This led to an agreement on the value being -a URI and that the actual details of what that represented was outside of the scope -of the TC-API work. This will also lead to some changes in the new calendaring -extensions for event publication draft. Additionally we looked at what it was -necessary to add to the data model to successfully handle tasks. - -We spent some time working on the subscription upgrade specification to ensure this -would work successfully with caching servers. There was some discussion on how to -flag a deleted event.The eventual consensus was to define a new "Deleted" status. We -also felt it was important to define a time-range query as that is probably a very -frequent use of subscriptions - e.g. what events happen this week? The consensus was -that we should use a HEAD request to discover the possible upgrades rather than an -OPTIONS request. - -We spent some time discussing various aspects of VCARD. There was a lot to be -discussed around the exact meaning of the UID. The wording of the specifications -suggest that it is associated with the actual entity -- i.e. a human or a resource. -Many of us thought that it should really be tied to a particular representation of -that entity. Associated with that was the issue of who or what should merge cards -that appear to represent the same entity. A number of us felt that no merge should be -attempted - it is up to the consumer to decide if two vCards represent the same -person. Perhaps UIs should consider adding the ability to explicitly link VCARDs -representing the same person. There is probably further discussion to be had on this -issue. diff --git a/sources/csd-report-ioptestevent-40.adoc b/sources/csd-report-ioptestevent-40.adoc deleted file mode 100644 index ee311f5..0000000 --- a/sources/csd-report-ioptestevent-40.adoc +++ /dev/null @@ -1,119 +0,0 @@ -= Report on Test Event and Developers Forum XL, September 25-27 2017 -:docnumber: 1706 -:copyright-year: 2017 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2017-11-20 -:published-date: 2017-11-20 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The event was hosted by Open-Xchange in Cologne, Germany on September 25-27, -2017. - -In attendance for this interoperability event and developers forum were: - -* Mike Douglass Spherical Cow Group - managing the event -* Ken Murchison, Robert Stepanek for Fastmail -* Thomas Schäfer for 1&1 -* Marten Gajda for dmfs -* Gren Eliot for Zimbra -* Ralf Becker for eGroupware -* Martin Herfurth and Tobias Friedrich for Open-Xchange -* Peter Tam for Ribose - -There was a significant amount of discussion around the new JSCalendar draft which also -spilled over into discussions on vCard. The JSCalendar specification is now felt to be relatively -stable and as yet there are few comments on the draft from outside CalConnect.The IETF will -be contacted to see if we can move this into a working group. - -There were some discussions about the relative merit of multiple RFCs for different aspects of -the standard (events v tasks) as against a single all encompassing draft. - -This led on to a discussion of the contacts api and the desire to come up with a format for -contacts that is based on the JSCalendar work. One idea is to define a common data model for -contacts, independent from data format and exchange protocols. Robert and Peter will share -the current work documents to see what's the overlap. - -Additionally Peter has been working on a GraphQL-based contacts API. The intent is to propose -this as a standard at some point. - -FastMail with the Cyrus server worked on subscription upgrade with dmfs and successfully -tested with WebCal-Sync. It should be noted how recurrence overrides are handled. Some -additional points on subscription upgrade: - -* Prefer=minimal will cause VTIMEZONEs to NOT be returned in subscription -upgrade. It can be overridden by using CalDAV-Timezones:T - -* Realized that CalDAV-Timezones SHOULD/MUST be included in Vary header -when server supports TZ-by-ref and subscription upgrade -There was some work done switching DEVGUIDE from old to new infrastructure. This -required a DNS change and bugfixing redirects. - -There was a lot of work around the CalDAV tester. Apple is no longer maintaining this tool so we -are free to apply our own updates to a CalConnect maintained copy. There was some -discussion around how we should avoid conflicts - the suggestion is to create a ticket for a test -or test you want to work on. Committing back to the core should be fine at least at this stage. - -Some work was started on trying to build bootstrap code into the tester. For many servers this -will remove the need fo a lot of configuration as the tester should be able to discover most of -what it needs. - -Open-Xchange had been discouraged by the enormous number of failures in the original tester. - -During this session they managed to get much further - concentrating on a smaller number fo -tests. - -Ralf for eGroupware has implemented caldavtester - a wrapper around the Apple originated -tester. This provides a GUI, options for selecting tests and features to determine what changes -happened as a result of server updates. Some work was done to add new feature to that tool. - -A number of changes were also made to some tests to make them less Apple specific - fro -example, redirects now accept all valid http redirect codes. -As the large number of errors were reduced we all find that errors in our own server code -surface. - -Zimbra also did some work on fixing an issue with shared addressbooks not visible from iOS / -CardDAV-Sync on Android. - -Further discussions covered: - -* iTip improvements: new response for scheduling requests -* Optimistic updates -* The need to check the CalDAV specification wrt caching proxies - -In all this was a very productive session. diff --git a/sources/csd-report-ioptestevent-41.adoc b/sources/csd-report-ioptestevent-41.adoc deleted file mode 100644 index 705a058..0000000 --- a/sources/csd-report-ioptestevent-41.adoc +++ /dev/null @@ -1,78 +0,0 @@ -= Report on CalConnect Test Event and Developers Forum XLI, January 29-31, 2018 -:docnumber: 1802 -:copyright-year: 2018 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2018-03-02 -:published-date: 2018-03-02 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The event was hosted by Oath in Sunnyvale, California, January 29-31, 2018 - -In attendance for this interoperability event and developers forum were: - -* Mike Douglass Spherical Cow Group - managing the event -* Ken Murchison for Fastmail -* Thomas Schäfer for 1&1 -* Greg Solovyev for Zimbra -* Peter Tam for Ribose -* Richard Brigham and Anjj Kumar Tweari for Oath - -Despite the small attendance we managed to cover a number of topics. - -There was some work being done with `ical4j` as we continue to try to move forward to a version -based on the latest from Ben Fortuna. Some members have heavily modified older versions but -are getting closer. We intend to create a clone with some or all of the members' changes which -can be used as a staging point for pushing them up to Ben. - -There was some discussion on the work that is going on with vCard or its replacement. There -are still questions on how to represent all the desired groups of information. It seems the -discussions helped clarify some points. - -There was more work trying to get the CalDAV tester running. Anuj from Oath got Darwin and -the tester running together in record time and then proceeded to run tests against their server. - -There was more work on updating the developers guide. - -In addition we were working on getting vPoll running again as there was to be a demonstration -in the main conference following. - -We should remind potential attendees that the developers forum and test event is as much -about detailed discussions on points of implementation as it is about testing. It provides an -opportunity to discuss those small details. If you do have something to test or develop then -come early and get advice on the best path to take. diff --git a/sources/csd-report-ioptestevent-42.adoc b/sources/csd-report-ioptestevent-42.adoc deleted file mode 100644 index 6821495..0000000 --- a/sources/csd-report-ioptestevent-42.adoc +++ /dev/null @@ -1,79 +0,0 @@ -= Report on CalConnect Test Event and Developers Forum XLII, June 4-6, 2018 -:docnumber: 1804 -:copyright-year: 2018 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2018-06-29 -:published-date: 2018-06-29 -:technical-committee: IOPTEST -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The event was hosted by Jorte in Tokyo, Japan, June 4-8, 2018 - -In attendance for this interoperability event and developers forum were -representatives from - -* Spherical Cow Group -* FastMail -* Open-Xchange -* Ribose -* Jorte - -Despite that small attendance we were all kept busy on a number of issues which -required discussion and implementation. - -Vpoll was being worked on by Robert Stepanek of FastMail in preparation for a -presentation and demonstration in the conference. - -We had further discussions on the new JSCalendar specification Robert is working on. -As the specification nears completion there are some remaining issues. The -description property and localization, client-side alarm handling amd -attendee-specific sequencing. As ever there were discussions about various aspects of -recurrences. - -The new server side subscriptions specification was discussed and the Open-Xchange -members carried out a preliminary implementation of the specification. This -specification allows DAV clients to POST subscription requests to the server which -then manages the synchronization of the data. Open-Xchange proposed some additions be -added: a "refresh now" option for clients and persisting and signaling account errors -to clients. These most likely will be added to the final specification. - -We talked about the progress being made with the VObject and VCard work in -preparation for presentations later in the week. - -Apart from the larger issues above these meetings provided the opportunity for -face-to-face in depth discussion on various topics. diff --git a/sources/csd-report-roundtable-1.adoc b/sources/csd-report-roundtable-1.adoc deleted file mode 100644 index 518fc13..0000000 --- a/sources/csd-report-roundtable-1.adoc +++ /dev/null @@ -1,84 +0,0 @@ -= Report on Roundtable I, 23-24 September 2004 -:docnumber: 0404 -:copyright-year: 2004 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2004-09-24 -:published-date: 2004-09-24 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Report - -The first Roundtable sponsored by the Consortium took place on 23-24 September, 2004, hosted -by Oracle Corporation in Montreal. This event was not restricted to Consortium members. It was -an invitational "Open Roundtable on the Future of Interoperable Calendaring and Scheduling" and -the invitation was sent out to a variety of individuals and organizations involved in Calendaring -and Scheduling as vendors, customers, standards participants, etc. - -Twenty-three individuals from fourteen organizations attended the Roundtable. The discussion -was oriented towards three general areas: - -* Do we agree on a problem statement? -* Are we willing to work together to address the problem(s)? -* How do we want to go about undertaking this work? - -At the end of the two days, the participants had broadly agreed on a common definition of the -problem in terms of what had to be done to move forward with interoperable Calendaring and -Scheduling, and had jointly agreed to work together to address the problems. The group adopted -the following informal "charter" as a synthesis of their discussions: - -[quote] -"WE" will come together to develop use cases, in concert with the users of calendaring products, -to shape the technical requirements and critical input to help shape the work taking place in at -least CalDAV, CALSIFY, UMA and other calendaring areas. Areas of focus will be calendar -interoperability and a definition of a minimum implementation of same. We will also focus on -testing and evaluation of interoperability. Attention will be paid to the promotion and evangelism -of calendaring standards, capabilities and interop. - -The Roundtable agreed to work within the Consortium structure to accomplish its work, and -established a timetable for participating organizations to commit to and join the Consortium. Plans -for initial technical committees, and a general timetable for carrying out the work, were also -agreed. - -Represented at the Roundtable were Apple, Duke University, Isamet, IBM Lotus, the Mozilla -Foundation, Nokia, Novell, Oracle, OSAF (Open Source Applications Foundation), Stata Labs, -UC Berkeley, University of Washington, Yahoo!, and the Calendaring and Scheduling -Consortium. - -The critical mass of organizations joining the Consortium in the following months, both those who -had participated in the September Roundtable and others, enabled the Consortium to make its -public launch announcement on December 14, 2004, and to move forward with plans for its next -Roundtable in January 2005. diff --git a/sources/csd-report-roundtable-10.adoc b/sources/csd-report-roundtable-10.adoc deleted file mode 100644 index 34fd3f5..0000000 --- a/sources/csd-report-roundtable-10.adoc +++ /dev/null @@ -1,172 +0,0 @@ -= Report on Roundtable X, September 19-21 2007 -:docnumber: 0713 -:copyright-year: 2007 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2007-09-21 -:published-date: 2007-09-21 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable X and the accompanying IOP Test Event took place September 17-21, hosted by The -Massachusetts Institute of Technology, in Cambridge, Massachusetts. The event was attended by -43 representatives from 31 organizations, including representatives from three observers -(organizations attending a Roundtable to see if they wish to join). - -The CalConnect Interoperability Test Event (C.I.T.E.) was held immediately prior to the -Roundtable, running Monday noon through Wednesday noon, September 17-19. Nine (9) -organizations participated in this event, performing interoperability testing between their -calendaring and scheduling implementations. A report on the IOP Test Event will be published as -soon as possible. - -In conjunction with this Roundtable, CalConnect hosted a one-day open vCard Workshop on -Tuesday, September 18th. The vCard Workshop was attended by about 20 people. A report on the -workshop together with presentations and other materials may be found at vCard Workshop -Report. - -Roundtable X, attended by 43 representatives from 35 organizations, including 4 observers ran -Wednesday afternoon, all day Thursday, and Friday morning. Wednesday afternoon began with a -Technology Preview demonstrating live interoperability in the areas of CalDAV Scheduling, -Server-Server, and Free/Busy URL between multiple dissimilar clients and servers. The majority -of the Roundtable was dedicated to technical committee sessions, BOFs, and informal discussions -and networking, with an all-hands Plenary meeting as the last item on Friday morning. The -Technical Committee sessions were organized sequentially, without competing parallel sessions, to -allow all attendees who wished to be involved in the discussions of a Technical Committee the -opportunity to do so. - -== Update on Technical Committees and Initiatives - -Work Products since Roundtable IX: - -* TC CALDAV has published CalDAV Scheduling Requirements. -* TC MOBILE has published the Mobile Calendar Interoperability Test Suite. -* The DST Ad Hoc Committee has published CalConnect EDST Reflections and -Recommendations, reviewing how the industry dealt with the early DST conversions in -March, and with recommendations both for the November 4 reversion from Daylight -Savings Time, and for the future of DST and timezone management. - -=== TC CALDAV - -TC CALDAV reported on its work to date including its recently-published -CalDAV Scheduling Requirements paper. Discussions covered new and continuing work in -several areas of potential extensions to the CalDAV specification, including Roles, Access -Control, Alarm Management and other scheduling extensions. - -=== TC EVENTPUB - -TC EVENTPUB reviewed the current state of the VVENUE proposal, -generating a great deal of discussion concerning possible intersections between VVENUE and the -potential work on vCard. The TC also reviewed the current status of work on the "eventmap" -event sharing proposal. - -=== TC FREEBUSY - -TC FREEBUSY reviewed work since the last Roundtable, especially work on -Free/Busy URL and in preparing for the Technology Previews of CalDAV Scheduling, serverserver, -and Free/Busy URL. Going forward the TC will continue work on Free/Busy URL and on -Free/Busy discussions with external entities. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test event just completed, and discussed early -plans to implement an issue-tracking mechanism and to work with TC MOBILE on planning for a -Mobile Interoperability Test Event. - -=== TC MOBILE - -TC MOBILE presented and reviewed its recently-published Mobile Calendar -Interoperability Test Suite, and discussed plans for an initial Mobile Interoperability Test Event, -including liaison activities with the OMA/DS group. The TC may also participate in establishing -interoperability testing for vCard if the Consortium goes forward in this area, as vCard is already -reflected in the Mobile IOP test suite. - -=== TC REALTIME - -TC REALTIME has been reactivated since Roundtable IX, and has been -meeting alternately with TC FREEBUSY to work on the VAVAILABILITY proposal and the -Technology Previews at this Roundtable. Going forward the TC will work on the REALTIME -messaging protocol, Discovery, and Authentication and Authorization. - -=== TC TIMEZONE - -TC TIMEZONE was reactivated to consider the DST Ad Hoc recommendations and work on a -formal Timezone Registry proposal and a proposal for a Timezone Service Protocol. The TC -presented the conceptual work to date for the registry and service proposals. - -=== TC USECASE - -The TC presented its in-progress work on Resources generating a lengthy -discussion on the subject. The TC has also undertaken a study of recurrence features in mobile -device support for TC MOBILE. - -=== Daylight Saving Time Ad Hoc - -The DST Ad Hoc published CalConnect EDST Reflections and -Recommendations just prior to this Roundtable, and gave a short discussion of the paper and its -recommendations. The Ad Hoc will remain instantiated until it is apparent whether additional -information gathering and delivery will be needed in preparation for the November 4 reversion to -standard time. - -=== CalConnect Interoperability Test Event - -Participants in the IOP test event -included Apple, IBM, Kerio, Marware, Mozilla, Open Connector Groupware,OSAF, Oracle, and -RPI (Bedework), Results from the event will be posted at Past IOP Reports as soon as they are -collated and prepared. - -=== BOFS - -BOF topics included XML for iCalendar representation, VVENUE and VALARM follow - -=== New Initiatives - -* The Consortium plans to initiate a TC in the area of XML representation of iCalendar data; -a draft charter will be prepared shortly after the Roundtable. -* The Consortium will initiate a TC in the area of a vCard Revision if the resources can be -found. A draft charter will be circulated via the public vcard-workshop-l mailing list. - -== Future Meetings - -* ROUNDTABLE XI: February 4-8, 2008, at Sun Microsystems, San Francisco Bay Area, -California. -* ROUNDTABLE XII: June 2-6, 2008, at the University of Wisconsin, Madison, Wisconsin. -* ROUNDTABLE XIII: October 6-10, 2008, host and location to be determined. - -The format of the CalConnect week is: - -* Monday noon through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday noon, Roundtable (TC sessions, BOFs, networking, Plenary). diff --git a/sources/csd-report-roundtable-11.adoc b/sources/csd-report-roundtable-11.adoc deleted file mode 100644 index 7b6d808..0000000 --- a/sources/csd-report-roundtable-11.adoc +++ /dev/null @@ -1,163 +0,0 @@ -= Report on Roundtable XI, February 6-8 2008 -:docnumber: 0809 -:copyright-year: 2008 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2008-02-08 -:published-date: 2008-02-08 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XI and the accompanying IOP Test Events took place February 6-8, 2008, hosted by -Sun Microsystems in Menlo Park, California. The event was attended by 53 representatives from -25 organizations, including representatives from five observers (organizations attending a -Roundtable to see if they wish to join). Two media representatives were also present by invitation -to see the Technology Preview on Wednesday afternoon. - -The CalConnect Interoperability Test Events (C.I.T.E.) were held immediately prior to the -Roundtable, running all day Monday and Tuesday, February 4-5. Nine organizations participated -in the regular IOP Test Event, performing interoperability testing between their calendaring and -scheduling implementations. In parallel, CalConnect hosted its first Mobile Interoperability Test -Event, attended by three organizations interested in conducting mobile calendaring tests. A total of -30 people attended the two IOP Test Events, including four observers. Reports on the IOP Test -Events will be published as soon as possible. - -Roundtable XI began Wednesday morning, and ran through early afternoon on Friday. Special -events at Roundtable XI included - -* A Technology Preview demonstrating live interoperability in the areas of CalDAV -Scheduling, Server-Server, and Free/Busy URL. A presentation about this Technology -Preview is available at Roundtable XI Technology Preview. -* Presentations on the Danish eKalendar.dk project from representatives of the Danish -Government and of Cabo Communications, the prime contractor on the project. The -presentations are available at Danish eKalendar Project and eKalendar from a Developer's -Perspective. - -The remainder of the Roundtable was dedicated to technical committee sessions, BOFs, and -informal discussions and networking, with an all-hands Plenary meeting as the last item on Friday -afternoon. The Technical Committee sessions were as usual organized sequentially, without -competing parallel sessions, to allow all attendees who wished to be involved in the discussions of -a Technical Committee the opportunity to do so. - -== Update on Technical Committees and Initiatives - -=== TC CALDAV - -TC CALDAV reported on its work since the last Roundtable and on its planto -incorporate implicit scheduling into the CalDAV Scheduling Specification. Discussions were held -in this area to clarify specific elements of implicit scheduling for the Technical Committee. - -=== TC EVENTPUB - -TC EVENTPUB reviewed the current state of the VVENUE proposal and -initiated a discussion on whether the approach was correct, or whether we should be encuraging -the appropriate extensions to vCARD now that the IETF has undertaken a Working Group to -revise the vCard RFC. - -=== TC FREEBUSY - -TC FREEBUSY reviewed work since the last Roundtable, especially work on -Free/Busy URL and in preparing for the Technology Previews of CalDAV Scheduling, serverserver, -and Free/Busy URL and discussed synergies with the Danish Government and the -eKalender.dk project. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test events just completed, including the first -Mobile Interoperability Test Event, discussed early plans to implement an issue-tracking -mechanism, and decided to adopt a work item on a formal test suite and capabilities to support -virtual IOP testing. - -=== TC MOBILE - -TC MOBILE presented its work since the publication of the Mobile Calendar -Interoperability Test Suite, and discussed the first Mobile Calendar Interoperability Test Event just -completed. Future directions in work for extending the test suite for vCard testing, and a focus on -mobile requirements for CalDAV, were adopted into the work plan. TC MOBILE is also exploring -having the next Mobile Interoperability Test Event in Europe, possibly in the autumn of 2008. - -=== TC REALTIME - -TC REALTIME presented and discussed its work on the REALTIME -messaging protocol, Discovery, and Authentication and Authorization, and in particular needs for -additional expertise in security within CalConnect to inform this work. - -=== TC TIMEZONE - -TC TIMEZONE presented the conceptual work to date for the registry and -service proposals and led discussion on various elements of the proposals. - -=== TC USECASE - -The TC presented its in-progress work on Resources generating a lengthy -discussion on the subject and some recommendations from other participants. - -=== CalConnect Interoperability Test Event - -Participants in the IOP test events -included Apple, Kerio, Marware, Microsoft, Oracle, RPI (Bedework), Scalix, Sony Ericsson, Sun -Microsystems and Zimbra. Results from the event will be posted at Past IOP Reports as soon as -they are collated and prepared. - -=== BOFS - -BOF topics included CalDAV Implicit Scheduling, moving forward with a TC-XML, how -to go forward with vCARD, and how to better support and attract European members. - -=== New Initiatives - -* CalConnect will initiate TC-XML in the area of XML representation of iCalendar data. -* CalConnect will support vCard via existing work within extant TCs plus a coordinating -function in TC CHAIRS, but will not initiate a new TC for vCard at this time. The public -vcard-workshop-l mailing list will be retained as a way of continuing to involve external -participants in ongoing focus in this area. -* CalConnect is exploring offering an invitational "meet CalConnect" event in Europe later -this year as a way to introduce potential members to the Consortium. -* CalConnect has initated a Guest Speaker program to invite selected individuals to speak to -CalConnect who are unlikely to attend Roundtables due to locale or work interests. - -== Future Meetings - -* ROUNDTABLE XII: June 2-6, 2008, at the University of Wisconsin, Madison, Wisconsin. -* ROUNDTABLE XIII: October 6-10, 2008, at Zimbra, Sunnyvalle, California. -* ROUNDTABLE XIV: February 2-6, 2009, host and location to be determined. - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Events) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-12.adoc b/sources/csd-report-roundtable-12.adoc deleted file mode 100644 index 103fe9c..0000000 --- a/sources/csd-report-roundtable-12.adoc +++ /dev/null @@ -1,140 +0,0 @@ -= Report on Roundtable XII, June 4-6 2008 -:docnumber: 0810 -:copyright-year: 2008 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2008-06-06 -:published-date: 2008-06-06 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XII took place June 4-6, 2008, hosted by the University of Wisconsin in Madison, -Wisconsin. The event was attended by 31 people from 22 organizations, including representatives -from two observers (organizations attending a Roundtable to see if they wish to join). - -The Roundtable was dedicated to technical committee sessions, BOFs, and informal discussions -and networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The -Technical Committee sessions were as usual organized sequentially, without competing parallel -sessions, as is our standard practice to allow all attendees who wished to be involved in the -discussions of each Technical Committee the opportunity to do so. - -== Update on Technical Committees and Initiatives - -=== TC CALDAV - -TC CALDAV reported on its work since the last Roundtable and on implicit -scheduling. In particular the discussion focused on calendar roles in preparation for the -development of a draft protocol on role-based access control in CalDAV. - -=== TC EVENTPUB - -TC EVENTPUB discussed venue information on vCard and the need to let the -new vCard specification develop. vCard V4 as planned will include new property types for -individual, organization, and group, and provide scope for resources. The TC will focus going -forward on requirements and use cases around the public event space, and additionally on how -that may relate to CalDAV. - -=== TC FREEBUSY - -TC FREEBUSY reviewed its work on Freebusy URL. Key issues related to -whether FBURL would be used to publish information, as well as meeting events and interactions -with CalDAV. Going forward the TC will focus on developing a formal FBURL specification. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test event just completed, and presented the -proposed Virtual Test Lab as part of the TC MOBILE session. - -=== TC MOBILE - -TC MOBILE presented its work on extending the Mobile Calendar -Interoperability Test Suite in the area of recurrences and formal definitions of mobile device -capability levels. Plans for a Virtual Test Lab were presented by TC IOPTEST, and the second -Mobile Interoperability Test Event was decided upon. - -=== TC TIMEZONE - -TC TIMEZONE presented the work to date on its draft proposal and RFC and -will work towards having the proposal ready to present at the October Roundtable. - -=== TC USECASE - -TC USECASE has been reviewing the topic of resources and finds little -commonality between existing implementations. The TC will focus on a recommendation -document for specific resource management issues. - -=== TC XML - -TC XML, founded at the last Roundtable, reported on its work to date in developing a -transform of iCalendar data to/from XML, particularly with respect to the size of an XML -representation and the relative friendliness of the XML created. - -=== CalConnect Interoperability Test Event - -Participants in the IOP test included -Apple, Mozilla, RPI (Bedework), Scalix, and Yahoo!/Zimbra. Results from the event will be -posted at Past IOP Reports as soon as they are collated and prepared. - -=== BOFS - -The major BOF was on preparing for an enhanced Technology Preview at the October -event, and to what degree CalConnect should be trying to conduct a public event with press -representatives. As before, we will invite a small number of selected individuals from the media -with an interest in calendaring to the Technical Preview in October. - -=== New Initiatives - -* CalConnect is developing a pilot of a Virtual Test Lab, to allow remote interoperability -testing of regular or mobile calendaring between registered test pairs, as an adjunct to its -regular in-person IOP test events. -* The second Mobile Interoperability Test Event will be held on 4-6 November, 2008, in -Plzen, Czech Republic, hosted by Kerio Technologies. -* CalConnect is continuing to consider an invitational "meet CalConnect" event in Europe but -the location and timing is still under discussion. - -== Future Meetings - -* ROUNDTABLE XIII: October 6-10, 2008, at Yahoo!, Sunnyvale, California. -Mobile IOP Test Event: November 4-6, 2008, at Kerio Technologies, Plzen, Czech Republic. -* ROUNDTABLE XIV: February 2-6, 2009, host and location TBD (east coast intended). -* ROUNDTABLE XV: June 1-5, 2009, host and location TBD (west coast intended). - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-13.adoc b/sources/csd-report-roundtable-13.adoc deleted file mode 100644 index 8750dd1..0000000 --- a/sources/csd-report-roundtable-13.adoc +++ /dev/null @@ -1,160 +0,0 @@ -= Report on Roundtable XIII, October 8-10 2008 -:docnumber: 0811 -:copyright-year: 2008 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2008-10-10 -:published-date: 2008-10-10 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XIII took place October 8-10, 2008, hosted by Yahoo!/Zimbra in Santa Clara, -California. The event was attended by 52 people from 19 organizations, including representatives -from two observers (organizations attending a Roundtable to see if they wish to join). - -The CalConnect Interoperability Test Event (CITE) was held immediately prior to the Roundtable, -October 6-8. Eleven organizations and 27 people participated in the regular test event, performing -interoperability testing between their calendaring and scheduling implementations. A reports on -the CITE will be published as soon as information has been delivered from all participants. - -The Roundtable was dedicated to technical committee sessions, BOFs, and informal discussions -and networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The -Technical Committee sessions were as usual organized sequentially, without competing parallel -sessions, as is our standard practice to allow all attendees who wished to be involved in the -discussions of each Technical Committee the opportunity to do so. - -An additional ten invitees joined us for the Technical Previews session on Wednesday afternoon. -The previews demonstrated live interoperability in the areas of CalDAV Scheduling, iSchedule -Server-Server scheduling, and Free/Busy URL. The presentation accompanying the life demos -will be made available shortly on the CalConnect website. - -== Update on Technical Committees and Initiatives - -=== TC CALDAV - -TC CALDAV reported on its work since the last Roundtable and on the status of -the latest scheduling draft, which includes implicit scheduling. A number of issues were raised and -discussed which will be further discussed and resolved in TC calls going forward. Work on -calendar roles will be resumed once the scheduling issues have been resolved. - -=== TC EVENTPUB - -TC EVENTPUB presented use cases concerning event publication and venue -information, and proposed some solutions. The TC will begin work on a formal proposal. - -=== TC FREEBUSY - -TC FREEBUSY summarized its work on the FREEBUSY READ URL draft -proposal. The TC will continue work on finalizing the draft and will begin consideration of issues -involving richer Freebusy information and availability/office hours. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test event just completed and on plans to start -collecting and reporting on bug and issue information discovered during the IOP tests. The TC -will look into the possiblity of an iCalendar parser to be made availabe on the CalConnect -website. The TC also presented a live demo of the new Virtual Test Lab facility. - -=== TC iSCHEDULE - -TC iSCHEDULE presented the status of the draft protocol. Much of the -discussion was on URI schemes and security provisions, such as relying on SSL certificates or to -move to S-MIME certificates in the payload rather than the transport layer. The TC will begin -work on the formal protocol. - -=== TC MOBILE - -TC MOBILE reported on its work since the last Roundtable and presented -feedback from the Open Mobile Alliance Data Synchronization working group on the TC's -recently published work products: Mobile Calendar Interoperability Test Suite V1.1 and Mobile -Recurrence Interoperability Recommendations. Plans for future interoperability testing were -discussed, including the second CalConnect Mobile Calendaring Interoperability Test Event in -Nov 2008 and beta testing of the new CalConnect Virtual Test Labs. It was agreed that the next -work item for the TC will be a "CalDAV considerations for mobile calendaring" paper. - -=== TC TIMEZONE - -TC TIMEZONE presented work to date on its draft proposal and RFC, and on -tentative plans to offer an open Timezone Workshop at the next Roundtable. The TC will work on -completion of its registry specification RFC and on a CalConnect Proposal for the Timezone -Service. - -=== TC USECASE - -TC USECASE presented its work on a new Resource Recommendations -document which includes congruences between iCalendar and vCard. The TC will develop a -formal document for publication and will work to provide its recommendations for vCard -extensions to the IETF in time for its November meeting. - -=== TC XML - -TC XML reported on its work to date in developing a round-trippable transform of -iCalendar data to/from XML, including an outline of what the XML data would look like and a -Relax NG Schema. Going forward the TC will resolve open issues and prepare a formal draft -document. - -=== CalConnect Interoperability Test Event - -Participants in the IOP test included -Apple, E&S Software, Google, IBM, Kerio, Microsoft, PeopleCube, RPI (Bedework), Scalix, Sun, -and Yahoo!/Zimbra. Results from the event will be posted at Past IOP Reports as soon as they are -collated and prepared. - -=== New Initiatives - -* The CalConnect Virtual Test Lab will be piloted immediately after Roundtable XIII and -should be available for use by the Mobile IOP Test Event in November. -* The second Mobile Interoperability Test Event will be held on 4-6 November, 2008, in -Plzen, Czech Republic, hosted by Kerio Technologies. -* CalConnect will offer a half-day Meet CalConnect introductory event on November 7 in -Prague, and November 10 in London. -* CalConnect will host an open Timezone Workshop on Tuesday, February 3, during the -CalConnect XIV week in Redmond. - -== Future Events - -* Mobile IOP Test Event: November 4-6, 2008, at Kerio Technologies, Plzen, Czech Republic. -* Meet CalConnect introductory event: November 7 (Prague) and November 10 (London), 2008. -* CALCONNECT XIV: February 2-6, 2009, Microsoft, Redmond, Washington. -* CALCONNECT XV: June 1-5, 2009, host and location TBD. -* CALCONNECT XVI: October 5-9, 2009, host and location TBD. - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-14.adoc b/sources/csd-report-roundtable-14.adoc deleted file mode 100644 index fd798c6..0000000 --- a/sources/csd-report-roundtable-14.adoc +++ /dev/null @@ -1,123 +0,0 @@ -= Report on Roundtable XIV, February 4-6 2009 -:docnumber: 0901 -:copyright-year: 2009 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2009-02-06 -:published-date: 2009-02-06 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XIV took place on February 4-6, 2009, hosted by Microsoft in Redmond, Washington. -The event was attended by 31 people from 20 organizations, including representatives from two -observers (organizations attending a Roundtable to see if they wish to join). - -The CalConnect Interoperability Test Event (CITE) was held immediately prior to the Roundtable -on February 2-4. Five organizations and 18 people participated in the regular test event, -performing interoperability testing between their calendaring and scheduling implementations. A -reports on the CITE will be published as soon as information has been delivered from all -participants. - -The Roundtable was dedicated to technical committee sessions, BOFs, and informal discussions -and networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The -Technical Committee sessions were as usual organized sequentially, without competing parallel -sessions, as is our standard practice to allow all attendees who wished to be involved in the -discussions of each Technical Committee the opportunity to do so. - -== Special Events - -Two special events occured at this roundtable. On Tuesday, the Timezone Technical Committee -sponsored an open workshop on issues with timezones, and CalConnect's work towards a -Timezone Registry and Timezone Service proposals. The event was attended by 17 people; remote -call-in and Livemeeting support was also available. - -On Wednesday afternoon Ben Fortuna, the author of iCal4J, was our first guest speaker. Ben spoke -about the inception and evolution of ical4j, and where he saw ical4j going in the future. Ben was -with us almost the entire week, so the membership had many opportunities to meet and talk with -Ben. Ben's presentation may be found at iCal4j at CalConnect. - -== Update on Technical Committees and Initiatives - -The following documents are about to finish Last Call and be published: - -* The draft proposed RFC for the iCalendar<-->XML transformation specification from TC -XML -* The Freebusy Read URL draft proposed RFC from TC FREEBUSY -* The draft RESOURCE proposed RFC from TC EVENTPUB - -The [underline]#Calendar Standards Roadmap#, which originally came out of TC-CalDAV, was enthusiastically -discussed at this Roundtable, spawning work in new areas by several TC's. This discussion is -hopefully just the beginning of a longer, engaging conversation. - -[underline]#Calonnect and the World Wide Calendar#: This brainstorming session for everyone attending the -Roundtable was designed to get people's heads up and have them look at the larger picture. We -looked at calendaring issues beyond the institutions and corporations most of us represent. -Interoperability on a world wide scale will begin to happen when soccer moms (or football -mums!) can see when their child's next game is and make appointments with their doctor as easily -as keep a work schedule. We discussed social adaptations like ubiquitous cell phone conversations -(maybe not a plus!) as well as the coming integration of calendaring with social networking sites -like Facebook. We intend for this to be an ongoing discussions at Roundtables as we pull back -from the (equally important) technical work to view calendaring from the viewpoint of the world -at large. - -== CalConnect Interoperability Test Event - -Participants in the IOP test included Apple, IBM, Microsoft, PeopleCube, and Yahoo!/Zimbra. -Results from the event will be posted at Past IOP Reports as soon as they are collated and -prepared. - -== Other Events - -* The second Mobile Interoperability Test Event was be held on 4-6 November, 2008, in -Plzen, Czech Republic, hosted by Kerio Technologies. The report from this IOP Test Event -may be found at Mobile Calendaring IOP Test Event Report - Nov 2008. -* CalConnect offered a half-day "Meet CalConnect" introductory event on November 7 in -Prague, and November 10 in London. A zip file of most of the presentations may be found -at Meet CalConnect Presentations. - -== Future Events - -* CALCONNECT XV: June 1-5, 2009. -* CALCONNECT XVI: October 5-9, 2009 -* CALCONNECT XVII: February 1-5, 2010 -* Third Mobile Calendaring IOP Test Event: timing and location not yet determined - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-15.adoc b/sources/csd-report-roundtable-15.adoc deleted file mode 100644 index 60b699f..0000000 --- a/sources/csd-report-roundtable-15.adoc +++ /dev/null @@ -1,167 +0,0 @@ -= Report on Roundtable XV, June 3-5 2009 -:docnumber: 0908 -:copyright-year: 2009 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2009-06-11 -:published-date: 2009-06-11 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XV took place on June 3-5 2009, hosted by Oracle Corporation in Redwood Shores, -California. The event was attended by 33 people from 20 members, plus a representative from the -OASIS oBIX working group. - -The CalConnect Interoperability Test Event (CITE) was held immediately prior to the Roundtable -on June 1-3. Six organizations and 13 people participated in the regular test event, performing -interoperability testing between their calendaring and scheduling implementations. A report on the -CITE will be published as soon as information has been delivered from all participants. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -A short (2 hour) workshop was held on Wednesday afternoon on Shared/Group/Public Calendars, -and provided a unique opportunity for discussion of this key area of calendaring that many -participants are interested in. The intent was to identify models and use cases for these types of -calendars and calendaring, what technologies and standards are needed, and how to move forward. -Work items will be picked up by TC USECASE and TC CALDAV to continue this effort. - -== Update on Technical Committees and Initiatives - -=== TC CALDAV - -TC CALDAV provided a status update on the various IETF Internet Drafts -relevant to CalDAV. The ZideOne Outlook to CalDAV connector was demonstrated. An open -discussion was held on several projects for extensions to CalDAV which will be part of the TC's -remit going forward. - -=== TC EVENTPUB - -TC EVENTPUB discussed the interactions between the TC and the shared -calendar workshop discussions throughout much of the Roundtable, in particular public events use -cases previously developed by the TC. The TC also discussed the state of work in its document -describing how vCard can be used with iCalendar. A decision was made to put the TC on hold -pending completion of vCard 4.0 work in the IETF, when it can be integrated into the -EVENTPUB resource proposal. - -=== TC FREEBUSY - -TC FREEBUSY reviewed the publication of the Freebusy Read URL proposal -and discussed work that has begun on a proposal for support of consensus scheduling. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test event just completed (elsewhere in this -report) and on plans for an iCalendar parser and further use of the Virtual Test Lab Facility. The -TC expects that testing will begin in October in new areas such as Freebusy Read URL, CardDAV, -and the new Timezone service and registry proposals (the first two were tested informally this -time; the Timezone protocols may begin informal testing in October). - -=== TC iSCHEDULE - -TC iSCHEDULE discussed the progress on the protocol and had an open -discussion on methods of deploying the iSchedule protocol in various scenarios. - -=== TC MOBILE - -TC MOBILE discussed its work on a Vision for Mobile Calendar, and held an -open discussion on the use cases for the document. An agreement was reached on the desirability -of a proposed document describing how CalDAV could effectively be used by mobile devices. The -Technical Committee is looking for a new Chair, following the reassignment of the previous Chair -within his organization. - -=== TC RESOURCE - -TC RESOURCE was established after the last Roundtable and has begun work -on defining a schema to represent resource attributes to enhance interoperability of resource data. -A consensus was reached in the discussion to use an abstract schema a bit more complicated than -name-value pairs, with an LDAP mapping example at the end of the document. - -=== TC TIMEZONE - -TC TIMEZONE presented work to date on its draft RFCs on Timezone -Registry and Timezone Service. It seems likely that there will be at least three trial -implementations available for interoperability testing at the October C.I.T.E. - -=== TC USECASE - -TC USECASE presented an overview of its three Resouce documents which -have just completed Last Call, and a vote to publish was taken at the TC Wrapup session at the -end of Roundtable XV. The documents are published at: - -* State of Resource Interoperability for Calendaring, Groupware, and Project Management -* Use Cases for Resources V1.0 -* A Recommendation for Minimum Interoperability of Resource Information - -The TC will begin work in three areas new areas: - -* Use cases for non-institutional, non-enterprise calendar users. -* Use cases drawn from the Shared Calendar Workshop notes. -* A revision of the Calendaring and Scheduling Glossary of Terms. - -=== TC XML - -The protocol for a round-trippable transform of iCalendar data to/from XML has been -completed and approved for publication, and has been submitted to the IETF as an Internet Draft; -see iCalendar XML Representation. A visitor from the OASIS oBIX working group was present -and discussed their interest in taking advantage of this work in the devleopment of their WS -calendar specification for intelligent building management. TX XML expects to begin next on a -JSON document for the specification. - -== CalConnect Interoperability Test Event - -Participants in the IOP test included Apple, Microsoft, Oracle, PeopleCube, Rensselaer -Polytechnic Institute (Bedework), and ZideOne. In addition to regular CalDAV, iMIP and iTIP -testing, some informal CardDAV and Freebusy Read URL testing was done as well. Results from -the event will be posted at Past IOP Reports as soon as they are collated and prepared. - -== Future Events - -* CALCONNECT XVI: October 5-9, 2009, hosted by Apple in Cupertino, California -* CALCONNECT XVII: February 1-5, 2010, hosted by the University of California, Irvine, in -Irvine, Californa - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-16.adoc b/sources/csd-report-roundtable-16.adoc deleted file mode 100644 index 2661566..0000000 --- a/sources/csd-report-roundtable-16.adoc +++ /dev/null @@ -1,160 +0,0 @@ -= Report on Roundtable XVI, October 7-9 2009 -:docnumber: 0910 -:copyright-year: 2009 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2009-10-19 -:published-date: 2009-10-19 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XVI took place on October 7-9 2009, hosted by Apple in Cupertino, California. The -event was attended by 35 people from 19 members. The CalConnect Interoperability Test Event -(CITE) was held immediately prior to the Roundtable on October 5-7. Five organizations and 13 -people participated in the regular test event, performing interoperability testing between their -calendaring and scheduling implementations; one observer was present. A report on the CITE will -be published as soon as information has been delivered from all participants. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -A short (2 hour) Meet the Apple Engineers session was held on Tuesday afternoon, prior to the -official Wednesday start of Roundtable XVI. It was was open to all Roundtable registrants, and -was attended by over 30 people. The Q&A session with engineers from Apple's iCal Client, iCal -Server, and iPhone Calendar teams was extremely collegial and frank. - -== Update on Technical Committees and Initiatives - -=== TC CALDAV - -TC CALDAV acknowledged the publication of RFC 5545 (iCalendar) and RFC -5689 (Extended MKCOL) and provided a status update on different Internet Drafts relevant to -CalDAV. Open discussions were held on CalDAV Extensions including calendar alarms, calendar -attachments, calendar push notifications, shared calendars, and WebDAV synchronization. - -=== TC EVENTPUB - -TC EVENTPUB will be reactivated with participants from three new members -and with a new Chair. - -=== TC FREEBUSY - -TC FREEBUSY discussed work on a proposal for support of consensus -scheduling, that is, the polling for a meeting time suitable for all or most attendees, and will be -working on a data format that can be carried in schedulng messages. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test event just completed (elsewhere in this -report). Initial testing for CardDAV and Timezone Service are expected to begin in February, with -initial iSchedule testing either in February or at the June event. - -=== TC iSCHEDULE - -TC iSCHEDULE discussed the progress on the protocol and reviewed -methods of deploying the iSchedule protocol in various scenarios. Open discussions were held on -well-known URIs, attachment support, migration issues, and tracing of iSchedule requests. - -=== TC MOBILE - -TC MOBILE presented a summary of the outreach, vision and calendar -questionnaire discussions that have taken place in the TC over the last few months, and surveyed -customer members present about their experiences with mobile calendaring to better inform the -direction of the TC. Ongoing work will include more outreach attempts, and a look at device -certification possibilities - -=== TC RESOURCE - -TC RESOURCE summarized the work of the TC to date, determining -attributes to better define a resource that can be standardized and thus ease client server -intoerperability in resource discovery. The TC also discussed the draft being developed for LDAP -and VCARD mapping for resource attributes. - -=== TC TIMEZONE - -TC TIMEZONE presented work to date on its draft RFCs on a Timezone -Registry, a Timezone Service protocol, and the Timezone Data XML format. The TC expects to -publish these documents in the next several weeks. - -=== TC USECASE - -TC USECASE discused current work with Non-Institutional/Non- -Enterprise/Free-Range users (NINEFR) and their usecases. The Glossary Revision which is -underway was briefly reviewed. - -=== TC XML - -TC XML has revised its Charter to accommodate n ew work at the behest of NIST, the -National Institute of Standards and Technology, in response to the -http://www.nist.gov/smartgrid/[NIST Smart Grid Interoperability Standards Project]. -This work includes an update to the iCalendar-to-XML -Protocol, and the development of an abstract calendaring API which will allow multiple protocol -bindings, one of which will be a web services protocol. - -== CalConnect Interoperability Test Event - -Participants in the IOP test event included Apple, Kerio, PeopleCube, Rensselaer Polytechnic -Institute (Bedework), and Sun. In addition to regular, Sun tested a preliminary version of a -CalDAV client for the Symbian OS which they will be contributing to Symbian R3. Results from -the event will be posted at Past IOP Reports as soon as they are collated and prepared. - -== Other News from Roundtable XVI - -CalConnect has decided to hold a full CalConnect week including an Inteorperability Test Event -and Roundtable in Europe in the next two years, probably in 2011. European members will be -solicited for hosting proposals. - -CalConnect is implementing a new public mailing list for Calendar Developers. Information about -this list can be found at Calendar Developers Mailing List. - -== Future Events - -* CALCONNECT XVII: February 1-5, 2010, hosted by the University of California, Irvine, in -Irvine, Californa -* CALCONNECT XVIII: May 31 - June 4, 2010, host TBD but probably East Coast -* CALCONNECT XIX: October 4-8 2010, host TBD but probably East Coast - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-17.adoc b/sources/csd-report-roundtable-17.adoc deleted file mode 100644 index d51cfa8..0000000 --- a/sources/csd-report-roundtable-17.adoc +++ /dev/null @@ -1,178 +0,0 @@ -= Report on Roundtable XVII, February 3-5 2010 -:docnumber: 1001 -:copyright-year: 2010 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2010-02-10 -:published-date: 2010-02-10 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XVII took place on February 3-5 2010, hosted by the University of California at -Irvine in Irvine, California. The event was attended by 26 people from 18 members. The -CalConnect Interoperability Test Event (CITE) was held immediately prior to the Roundtable on -February 1-3. Six members and 9 people participated in the regular test event, performing -interoperability testing between their calendaring and scheduling implementations. For the first -time, remote testing was usefully employed with three people and two servers located remotely, -including two client testers in another country, communicating via the Consortium's internal -secure jabber environment. A report on the CITE will be published as soon as information has -been delivered from all participants. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -A presentation on UC Irvine's (the host's) calendaring environment was presented as the first of a -regular User SIG (Special Interest Group) Profile when a customer organization hosts CalConnect. - -== Update on Technical Committees and Initiatives - -=== TC CALDAV - -TC CALDAV acknowledged the publication of RFC 5545 (iTIP) and provided a -status update on Internet Drafts relevant to CalDAV. Open discussions on CalDAV extensions -scheduling, WebDAV synchronization, calendar attachments. Discussed the upcoming Internet- -Draft on new iCalendar properties. - -=== TC EVENTPUB - -TC EVENTPUB was reactivated with a revised charter. The TC has been -reviewing event publication use cases and how to deal with non-standard data, and has reached -consensus on the previously-proposed "Reference" property; an RFC will be developed and -submitted before the next Roundtable. The TC also discussed "dirty" (i.e. non-iCalendarcompliant) -data and how to deal with it, and raised the issue of a Certification program and multilanguage -support in VEVENTS. - -=== TC FREEBUSY - -TC FREEBUSY has continued discussions on consensus or poll scheduling and -is considering a possible iCalendar extension for VPOLL. CalDAV and iSchedule implications -and how VPOLL items would be stored on a server were also discussed. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test event just completed (elsewhere in this -report). Substantial iSchedule testing is expected - -=== TC iSCHEDULE - -TC iSCHEDULE presented an overview of the first iSchedule Internet Draft. -An approach to allow an iSchedule Receiver to test the authorization of an iSchedule Sender was -discussed. Discussion began on planning for iSchedule interoperability testing in May. - -=== TC MOBILE - -TC MOBILE discussed holding a Mobile Calendaring Interoperability Test Event -in conjunction with the May IOP test event, as sufficient interest was not shown prior to this event. -This test event would be focused on sync technologies, primarily ActiveSync. General sync -technology problems and issues were discussed including a detailed presentation by MailSite. The -consensus was to push forward with the May ActiveSync-focused test event, trying to get key -participants in place within a month or two. - -=== TC RESOURCE - -TC RESOURCE revised the existing draft and discussed open issues; some -attributes need better definition and better examples. Discussed whether it make sense to add -attributes that depend on the policy decisions of a deployment, and how to best define it or to get -information. Expect to begin CalConnect Last Call on the resource draft soon, followed by -submission to the IETF as an RFC. - -=== TC TIMEZONE - -TC TIMEZONE summarized the problems they are currently trying to solve -and gave a brief description of where the draft RFCs stand. The two major issues outstanding were -discussed: Timezone identifier format and the implications of Mr. Olson's retirement on the supply -of Timezone data. - -=== TC USECASE - -TC USECASE discussed the Glossary revision, RFC 3283 (Guide to Internet -Calendaring), and "NINE" (Non-Institutional / Non-Enterprise) usecases. A proposal was agreed -to remove the current link to the glossary, initiate a wiki page with updated state, and continue -discussions about a broader wiki. TC USECASE will work on the wiki glossary, then move it to -HTML format, then look at RFC 3282 in a broader picture with more than one target audience; it -is not clear what can be done about RFC 3283 if we wish to supersede it with a CalConnect -document or (more likely) a more dynamic alternative such as a wiki feed. TC USECASE will -also continue work on NINE usecases to publish a document useful for information and outreach. - -=== TC XML - -TC XML briefly discussed the status of the XML iCalendar Representation and is -working on an updated draft with additional samples, and a resource linking proposal. The -majority of the session was spent on design issues for the calendar web services specification; -feedback from the participants was helpful in narrowing down the scope of the initial -specification. TC XML will plan on producing an initial draft and publishing it by the May -Roundtable. This work together with the XML iCalendar Representation will be input to work by -the OASIS WS-Calendar committee to be formed later this month, and substantial collaborative -effort between the technical committees is expected. - -== CalConnect Interoperability Test Event - -Participants in the IOP test event included Apple, PeopleCube and Sun Microsystems. In addition, -EMClient (Icewarp) tested remotely and Oracle and Andrew McMillan (DaviCal) made their -servers remotely available for testing. Results from the event will be posted at Past IOP Reports as -soon as they are collated and prepared. - -== Other News from Roundtable XVII - -CalConnect's first European CalConnect week will be hosted by Kerio Technologies in Plzen, -Czech Republic, in the Autumn of 2011 - the latter half of September or early in October. SWAMI -(The Swedish Organization for Middleware Infrastructure) has offered to host a Meet CalConnect -introductory half-day for prospective members in Scandinavia the week before or after the -CalConnect week. - -CalConnect has implemented the Calendar Developer mailing list as announced in October. The -list now has several dozen subscribers and is beginning to see activity. - -CalConnect has established an internal Jabber service requiring a userid on the CalConnect -system, as a secure tool for remote IOP testing, TC meetings, etc. - -== Future Events - -* CALCONNECT XVIII: May 24-28, 2010, Carnegie Mellon University, Pittsburgh PA -* CALCONNECT XIX: October 4-8 2010, IBM/Lotus, Littleton MA -* CALCONNECT XX: January 31 - February 4, 2011, TBD. - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-18.adoc b/sources/csd-report-roundtable-18.adoc deleted file mode 100644 index 886f580..0000000 --- a/sources/csd-report-roundtable-18.adoc +++ /dev/null @@ -1,186 +0,0 @@ -= Report on Roundtable XVIII, May 26-28, 2010 -:docnumber: 1005 -:copyright-year: 2010 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2010-06-02 -:published-date: 2010-06-02 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XVIII took place on May 26-28 2010, hosted by Carnegie Mellon University in -Pittsburgh, Pennsylvania. The event was attended by 27 people from 18 organizations, including -one observer. The CalConnect Interoperability Test Events were held immediately prior to the -Roundtable on May 24-26. Eight members and 15 people participated in the regular and Mobile -Calendaring IOP Test Events. As some people attended both an IOP Test Event and the -Roundtable, the total count of participants for the week was 34. - -The Mobile Calendar IOP Test Event featured ActiveSync testing, and six member organizations -participated; three organizations participated in the "regular" IOP Test Event. Reports on the IOP -Test Events will be published as soon as information has been delivered from all participants. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -Dr. Steven Lee, Professor and Head of the School of Architecture at Carnegie Mellon University, -gave a talk on his view of calendaring and the current challenges he faces in two roles: as Head of -a department that schedules many campus events, and as the IT person for a small business, his -architecture practice. Dr. Lee invited interested participants on a tour of the -http://www.cmu.edu/homepage/innovation/2007/spring/intelligent-workplace.shtml[Intelligent Workplace] -project at CMU on Friday morning. - -== Documents Published since Last Roundtable - -* TC IOPTEST has published the public and internal IOP Test Event Reports from February -* TC RESOURCE has published its Schema for representing calendaring and scheduling -resources -* TC XMLhas updated xCal - the XML format for iCalendar to Version 4 -* TC XML has released Cal-WS Web Services API for calendaring and scheduling for Public -Review and Comment - -== Update on Technical Committee Work and Initiatives - -=== Internet Calendar Subscription Ad Hoc - -The Internet Calendar Subscription Ad Hoc was -established to investigate the creation and promotion of a single icon and method to be used on -websites to indicate a calendar available for subscription or download. The Ad Hoc reports -significant progress in understanding and addressing the issue, and the Plenary recommended the -formation of a Technical Committee to carry on the work. - -=== TC CALDAV - -TC CALDAV discussed the status of the revision to RFC 2447 (iMIP) and the -progression of the draft on Collection Synchronization in WebDAV ("WebDAV Sync") which has -occupied much of the TC's time over the last few months. The TC also held an open discussion on -the Calendar Alarm Extensions for CalDAV, a Internet Draft on which the TC has been working. - -=== TC EVENTPUB - -TC EVENTPUB has been working on its LINK (formerly Reference) property -extension to iCalendar, and expects to publish and submit it as an Internet Draft by the end of -June. - -=== TC FREEBUSY - -TC FREEBUSY is continuing to work on consensus or poll scheduling, and is -developing a specification extending iCalendar and iTIP for VPOLL. CalDAV and iSchedule -implications and how VPOLL items would be stored on a server were also discussed. - -=== TC IOPTEST - -TC IOPTEST reported on the IOP test events just completed (elsewhere in this -report). There is interest in conducting iSchedule and CardDAV testing at the October regular IOP -Test Event, and Timezone Service testing at the February 2011 event. - -=== TC iSCHEDULE - -TC iSCHEDULE presented an overview of the second iSchedule Internet -Draft. The TC has settled on DKIM as the mechanism for authentication and authorization in -iSchedule, and a DNS mechanism to support delegation of iSchedule authority to another server. -The next draft of iSchedule is close to publication. - -=== TC MOBILE - -TC MOBILE reported on its very successful Mobile Calendaring IOP Test Event -focused on ActiveSync testing, in which six member organizations participated (also see below -under IOP Test Events). The TC will produce a summary of the test event with the goal of using -that document to promote testing to other vendors who were not present. The TC will also -enhance the testing suite by adding more detail as well as example calendar data to streamline the -testing process. Outreach efforts will continue. - -=== TC RESOURCE - -TC RESOURCE briefly presented comments on its just-published Schema for -representing calendaring and scheduling resources, which has been submitted to the IETF as an -Internet Draft, and discussed the implementation of the additional information in the DAV -protocols. - -=== TC TIMEZONE - -TC TIMEZONE gave a brief presentation of the Timezone Service and -Timezone Data Format drafts which are nearly ready for publication and submission as Internet -Drafts. The TC also discussed some major issues going forward such as maintaining Timezone -data, Timezone identifier format and the implications of Mr. Olson's retirement on the supply of -Timezone data. - -=== TC USECASE - -TC USECASE discussed the Glossary revision and RFC 3283 (Guide to Internet -Calendaring). The TC expects to complete the Glossary revision project by the next Roundtable. -The intent is to ignore RFC 3283 as obsolete and remove references to it except for a statement of -its lack of relevance. The revised Glossary will be made available on the CalConnect website in -HTML format to allow search engine and other search retrievals. - -=== TC XML - -TC XML reviewed the status of xCal - the XML format for iCalendar document which -has been updated several times since its initial publication. Most of the session was devoted to -review of the Cal-WS Web Services API for calendaring and scheduling document now out for -Public Review and Comments. This specification will become a substantial part of the OASIS WS -CALENDAR standard, and the TC discussed alternative approaches to making the document -available to OASIS upon publication. Preferred are submitting the material directly, to be -incorporated in WS CALENDAR, or arranging for OASIS to publish the material as a standard -which can then be normatively referenced by WS CALENDAR. This should be resolved with -OASIS hopefully by the end of the Public Review period in mid-June. Key to the approach will be -ensuring harmonization between CalConnect and OASIS for the future evolution of Cal-WS. - -== CalConnect Interoperability Test Event - -Participants in the "regular" IOP test event included Apple, EMClient (Icewarp), and Genentech. -Additionally Oracle, both Beehive and the Oracle Sun Server, Zimbra, and PeopleCube expressed -interest in remote testing. The Mobile Calendaring IOP Test Event, focused on ActiveSync, -included Icewarp, MailSite, Microsoft, Nokia, Notify Technology, and Synchronica. Results from -the events will be posted at Past IOP Reports as soon as they are collated and prepared. - -== Future Events - -* CalConnect XIX: October 4-8 2010, IBM/Lotus, Littleton MA -* CalConnect XX: January 31 - February 4, 2011, TBD -* CalConnect XXI: May 23-27 or June 6-10, 2011, TBD -* CalConnect XXII: October 3-7. 2011, Kerio Technologies, Plzen, Czech Republic - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-19.adoc b/sources/csd-report-roundtable-19.adoc deleted file mode 100644 index cdaf9b3..0000000 --- a/sources/csd-report-roundtable-19.adoc +++ /dev/null @@ -1,178 +0,0 @@ -= Report on Roundtable XIX, October 6-8, 2010 -:docnumber: 1013 -:copyright-year: 2010 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2010-10-20 -:published-date: 2010-10-20 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XIX took place on October 6-8 2010, hosted by IBM/Lotus in Littleton, -Massachusetts. The event was attended by 26 people from 15 organizations, including one -observer. The CalConnect Interoperability Test Event was held immediately prior to the -Roundtable on October 4-6. Five members and 10 people were present onsite for the IOP Test -Event, and two members and 2 people partipated remotely. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -IBM/Lotus provided an overview and demo of their calendaring products, followed by a Q&A -session with members of the IBM/Lotus engineering team. - -== Documents Published since Last Roundtable - -=== Published Documents - -* TC EVENTPUB - https://www.calconnect.org/CD1006%20LINK%20Property.shtml[Link Property Extensions to iCalendar] -* TC IOPTEST - https://www.calconnect.org/pubdocs/CD1009%20May%202010%20CalConnect%20Interoperability%20Test%20Event%20Report.pdf[public] and https://www.calconnect.org/membersonly/internaldocs/I1003%20May%202010%20CalConnect%20Interoperability%20Test%20Event%20Internal%20Report.pdf[internal] IOP Test Event Reports for CalConnect XVIII -* TC MOBILE - https://www.calconnect.org/pubdocs/CD1010%20TC%20MOBILE%20Interoperability%20Test%20Event%20Report.pdf[TC MOBILE Interoperability Test Event Report] -* TC TIMEZONE - https://www.calconnect.org/CD1007%20Timezone%20Service.shtml[TIMEZONE Service Protocol] and https://www.calconnect.org/CD1008%20Timezone%20XML.shtml[TIMEZONE XML Specification] -* TC XML - https://www.calconnect.org/CD1012_Intro_Calendaring.shtml[CalWS Restful Web Services Protocol for Calendaring] -* CalConnect - https://www.calconnect.org/CD1012_Intro_Calendaring.shtml[An Introduction to Internet Calendaring] - -=== Updated IETF Drafts (related to CalConnect) - -* http://tools.ietf.org/html/draft-daboo-srv-caldav-10 -* http://tools.ietf.org/html/draft-daboo-webdav-sync-04 -* http://tools.ietf.org/html/draft-cal-resource-schema-02 -* http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml-07 - -== Update on Technical Committee Work and Initiatives - -=== TC DSI - -The new TC DSI reviewed work to date on the icon design, and discussed -internationalization issues; discussed subscribe vs. download models of accepting calendar data. - -=== TC CALDAV - -TC CALDAV discussed how to deploy a multiple-server CalDAV system and what -requirements would be for clients; discussed managing attachments on a CalDAV server, coming -up with a new approach using a "workspace" collection; Apple presented their CalDAV-based -calendar sharing extensions, including a demo of some of the features. - -=== TC EVENTPUB - -TC EVENTPUB reviewed, its Link Property Extensions draft, and discussed -whether the required properties should be established via the Link specification, or as extensions -to iCalendar. The TC decided on the latter approach - extensions to iCalendar, and will be working -on this following the Roundtable. - -=== TC FREEBUSY - -TC FREEBUSY presented its work on the VPOLL extension to iCalendar, -which could be used with iTIP to implement consensus scheduled. Next step would be trial -implementations, including at least one client (to see how the mechanism would be presented in a -UI). - -=== TC IOPTEST - -TC IOPTEST conducted a "regular" IOP Test Event with participation from five -organizations and two remote participants, focusing on iMIP, CalDAV, and CardDAV testing. - -=== TC iSCHEDULE - -TC iSCHEDULE presented an overview of the current state of iSchedule -related standards, and an in depth view of the DKIM protocol and how it would be applied to -iSchedule. The scheduled time for the TC calls was adjusted to accommodate new participants. - -=== TC MOBILE - -TC MOBILE discussed its Mobile Interoperability Test Event Report from May, -the upcoming Mobile Calendaring IOP Test Event in February, and the development of a best -practices or "how to" document for calendaring on mobile devices, in particular mobile CalDAV -clients. The scheduled date and time for TC calls was adjusted to accommodate new participants. - -=== TC RESOURCE - -TC RESOURCE discussed "discovery" of resources and whether that could be -standardized; presented the "Principal search" mechanism used by Apple; and touched upon other -resource scheduling related tasks that could be discussed and standardized. - -=== TC TIMEZONE - -TC TIMEZONE discussed the current state of the Timezone Service Protocol -and Timezone XML specifications, and the negotiations between IANA and the timezone -community on providing a new home for timezone data. Also discussed were the implications of a -timezone service on protocols such as CalDAV, which use etags to implement synchronization, -and decided to carry out some research on clients to see in what ways they use timezone data -currently. - -=== TC USECASE - -TC USECASE held initial conversations about iSchedule's need for input from -the User and SysAdmin/Engineer's perspectives, especially concerning cross-domain scheduling. -The session concluded with an overview of the v2 Draft Glossary - -=== TC XML - -TC XML discussed he progress of iCalendar in XML through the IETF. The bulk of -the presentation was on the status of the recently released Cal-WS specification and the related -OASIS WS-Calendar specification. We also talked about the next steps for Cal-WS. Briefly noted -were questions of how we deal with the need for a new calendar query language, and a -standardized JSON representation. - -=== Digital Calendaring Outreach - -The CalEco Task Force presented a proposal for a CalEco -website implementation, which was discussed later by the Steering Committee. Some alternatives -were proposed to the Task Force. - -== CalConnect Interoperability Test Event - -Participants in the "regular" IOP test event included Apple, IBM, Kerio Technologies, Oracle -Corporation, and Rensselaer Polytechnic Institute (Bedework). Andrew McMillan (DaviCal) and -emClient (Icewarp) participated remotely. Results from the events will be posted at Past IOP -Reports as soon as they are collated and prepared. - -== Future Events - -* CalConnect XX: February 7-11, 2011, University of California, Berkeley, Berkeley, CA -* CalConnect XXI: May 23-27, 2011, NASA Ames, Mountain View, CA -* CalConnect XXII: October 3-7, 2011, Kerio Technologies, Plzen, Czech Republic - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-2.adoc b/sources/csd-report-roundtable-2.adoc deleted file mode 100644 index 14b4a58..0000000 --- a/sources/csd-report-roundtable-2.adoc +++ /dev/null @@ -1,149 +0,0 @@ -= Report on Roundtable II, 11-13 January 2005 -:docnumber: 0511 -:copyright-year: 2005 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2005-01-13 -:published-date: 2005-01-13 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -The first post-launch event of The Calendaring and Scheduling Consortium took place on 11-13 -January, 2005, sponsored by the University of Washington in Seattle. The event was attended by -31 people representing 16 organizations. The Roundtable event consisted of two days of Technical -Committee meetings, followed by an all-hands plenary meeting of the membership and attendees. -The first two days, a CalConnect Interoperability Event was held in parallel with the Technical -Committee meetings. The Technical Committee sessions were organized sequentially, to allow all -attendees who wished to be involved in the discussions of a Technical Committee the opportunity -to do so, and there was definitely "drift" between TC sessions and those participating in the -CalConnect Interoperability Event. - -== New Initiatives - -*TC-TIMEZONE* was formed as a result of work being done in CalDAV showing the need for a -formal time zone registry; iCAL needs this as well. Some work has been done in the past in this -area; the new Technical Committee will gather the work that has been done and develop a -proposal as to how best to move this forward. - -*TC-EVENTPUB* was formed based on work being done at UC Berkeley and elsewhere to -develop a precise understanding of event publishing and how it differs from general scheduling -problems, with the goal of attracting efforts being done in several academic institutions and -elsewhere to combine into a single work project and Technical Committee within Calconnect. - -*TC-CALSIFY* was re chartered with an expanded scope to support and help drive the CALSIFY -effort in the IETF via a Working Group to consider the potential revision of RFC 2445. - -*Glossary Project*: The work done in the USECASE Technical Committee has shown the need for -a taxonomy document for common vocabulary and glossary for calendaring and scheduling. Ms. -Egan volunteered to act as Project Editor to compile a first draft document for circulation by mid- -February. The Glossary, once complete, will be posted and publicly available on the Calconnect -website. - -*External Communications*: The Consortium has chartered an ad hoc group to develop proposals -for publicity, promotion, and recruitment, e.g. ways of communicating activities in calendaring -and scheduling, such as an RSS Feed for the C&S space, speaking appearances at technical -conferences and trade shows, and an expanded website presence including links to sites offering -calendaring functionality. - -== Calconnect Interoperability Event - -Participants in the CalConnect Interoperability Event included Isamet, Mozilla, Oracle, and the -University of Washington. The major part of the CalConnect Interoperability Event was CalDAV -testing; this was the first formal interoperability testing of CalDAV implementations, and -demonstrated basic interoperability between two CalDAV servers (Isamet, Oracle) and three -clients (Isamet Mulberry Desktop and Mobile Clients and Mozilla). The results of the CalConnect -Interoperability Event should be available by early February and will be posted on the Consortium -website and delivered to the IETF. - -== Technical Committees - -Five Technical Committees met on Tuesday and Wednesday. - -The Min-IOP Technical Committee is working to develop a comprehensive table of which features -of iCAL are actually implemented in which Calendaring products and are able to interoperate -successfully. The goal is to determine the minimum interoperable subset of functions defined by -the three RFCs which are actually in use and which must be succesfully carried forward into any -revision or "simplification" of RFC 2445, iCalendar. The Technical Committee is actively -involved in developing this matrix and determining how well the matrix maps to what the needed -minimum actually is. - -The CALDAV Technical Committee will produce scenarios for additional CalDAV testing for the -next Calconnect Interoperability Event, then turn to assisting CalDAV authors in submitting the -CalDAV draft to the IETF. They expect to use the use cases from the USECASE TC and anticipate -contributing additional use cases. CALDAV is very interested in being able to conduct virtual -Interops on a monthly basis and will work with IOP/TEST and the IOP Manager to accomplish -this under Consortium auspices. The Oracle and Isamet CalDAV servers are available on the -internet for client testing. - -The CALDAV participants were heavily involved in the CalConnect Interoperability Event and -also provided several demonstrations to the Roundtable: - -* Mozilla's Sunbird and Oracle Calendar with CalDAV protocol adapter -* Mozilla's Sunbird and Oracle's Exchange CalDAV protocol adapter -* Isamet Mulberry Desktop Client and Isamet CalDAV server -* Isamet Mulberry Mobile Client and Isamet CalDAV server - -The IOP/TEST Technical Committee is working to develop and formalize the Consortium's -CalConnect Interoperability Event testing. Among the issues being addressed by the Technical -Committee are planning and implementing virtual and ad hoc interops; how to contact nonmembers -about CalConnect Interoperability Event testing; how to establish CalConnect -Interoperability Event planning early on and integrate product planning; and how to conduct -multiple CalConnect Interoperability Event tests together. The Committee is also beginning -discussions on a reference implementations which for ad hoc testing by implementers as a service -from the Consortium to promote calendaring and scheduling standards. - -The RECURR Technical Committee was only able to meet briefly as the Chair was not able to -come to the Roundtable and had to join the TC by teleconference. The problem statement for the -TC was reviewed and narrowed to focus on recurrence rule problems. An additional effort will be -to identify and document the specifics of existing problems with recurrence rules as part of the -MIN-IOP effort. - -The USECASE Technical Committee spent substantial time compiling a set of Use Cases -identifying "real world" requirements for interoperable calendaring and scheduling -implementations. Some 29 specific use cases were documented. The next steps will be to develop -a ranking method and continue to add use cases from other members, and from other Technical -Committees. - -== Future Meetings - -Three regular meetings per year were agreed, roughly in January, May, and September. The -membership is strongly in favor of holding combined 2-1/2 day events featuring a CalConnect -Interoperability Event, Technical Committee meetings, and a membership plenary, after the model -followed at this Roundtable. The Consortium will attempt to alternate meetings between the east -and west coasts. The next meeting (Roundtable III) will take place 1-3 June, 2005, hosted by Duke -University in Durham, North Carolina. The following meeting will be in mid- to late September, -on the west coast. diff --git a/sources/csd-report-roundtable-20.adoc b/sources/csd-report-roundtable-20.adoc deleted file mode 100644 index dd0b1dd..0000000 --- a/sources/csd-report-roundtable-20.adoc +++ /dev/null @@ -1,92 +0,0 @@ -= Report on Roundtable XX, February 9-11, 2011 -:docnumber: 1103 -:copyright-year: 2011 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2011-03-16 -:published-date: 2011-03-16 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XX took place on February 9-11, 2011, hosted by the University of California, -Berkeley, in Berkeley, California. The event was attended by 30 people from 17 organizations. -The CalConnect Interoperability Test Event was held immediately prior to the Roundtable on -February 7-9. Thirteen people from 6 organizations were present onsite, and 3 organizations and 3 -people partipated remotely. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -Shel Waggener, Associate Vice Chancellor and CIO of the University of California, Berkeley, -gave a presentation on Calendaring at a Public University which was very well received and -focused in part on future issues already being discussed in the Consortium. - -== Documents Published or Updated since Last Roundtable - -=== Published Documents - -* TC EVENTPUB - http://www.calconnect.org/CD1101%20Eventpub%20iCalendar%20Extensions.shtml[Event Publishing Extensions to iCalendar] -* TC IOPTEST - https://www.calconnect.org/pubdocs/CD1014%20October%202010%20CalConnect%20Interoperability%20Test%20Event%20Report%20V1.0.pdf[Public IOP Test Event Report for CalConnect XIX] - -=== Updated IETF Drafts (related to CalConnect) - -* http://tools.ietf.org/html/draft-daboo-srv-caldav -* http://tools.ietf.org/html/draft-daboo-webdav-sync -* http://tools.ietf.org/html/draft-cal-resource-schema -* http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml - -== Update on Technical Committee Work and Initiatives - -RoundTable session summaries and activities may be found at -http://calconnect.org/minutes/CalConnect%20Minutes%20Feb2011.pdf. - -== Future Events - -* CalConnect XXI: May 23-27, 2011, NASA Ames, Mountain View, CA -* CalConnect XXII: October 3-7, 2011, Kerio Technologies, Czech Republic -* CalConnect XXIII: February 6-10, 2012, TBD - -The format of the CalConnect week is: - -* Monday morning through Wednesday noon, C.I.T.E. (CalConnect Interoperability Test Event) -* Wednesday noon through Friday afternoon, Roundtable (presentations, TC sessions, BOFs, -networking, Plenary). diff --git a/sources/csd-report-roundtable-21.adoc b/sources/csd-report-roundtable-21.adoc deleted file mode 100644 index 192ce9a..0000000 --- a/sources/csd-report-roundtable-21.adoc +++ /dev/null @@ -1,107 +0,0 @@ -= Report on Roundtable XXI, May 25-27, 2011 -:docnumber: 1105 -:copyright-year: 2011 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2011-06-20 -:published-date: 2011-06-20 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXI took place on May 25-27, 2011, hosted by NASA Ames at Moffett Field, -Mountain View, California. The event was attended by 26 people from 16 organizations. The -CalConnect Interoperability Test Event was held immediately prior to the Roundtable on May 23- -25. Ten people from three organizations were present onsite. plus two more remotely A -Workshohp on Tasks was held Wednesday afternoon as part of the Roundtable; in addition to the -Roundtable participants, several others were present just for the workshop or attended remotely. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -A Workshop on Tasks (VTODOs) was held Wednesday afternoon with the goal of determining -what needs to be added to iCalendar and related specifications to improve and encourage the use -of the standards for task and project management, as well as personal information management. - -The host presentation was given by Charlie xxxx, Assistant Project Manager of the Kepler -Mission, focused on the secheduling and resource optimization issues (especially concerning the -Deep Space Network) encountered with the mission. See https://www.calconnect.org/presentations/Kepler%20Mission%20Operations%20Scheduling.pdf[Kepler Mission Operations Schedulilng]. - -Friday afternoon we were offered a tour of two simulation facilities, the Future Flight Center and -the Crew-Vehicle systems Research Facility. - -== Documents Published or Updated since Last Roundtable - -=== Published Documents - -* Event Publishing Extensions to iCalendar -* Calendaring and Scheduling Glossary of Terms Version 2.0 -* Index to Calendaring and Scheduling Standards Version 2.0 - -CalConnect has replaced the internal Interoperability Test Event Report with an internal wiki. - -CalConnect has replaced the public Interoperability Test Report with a section on the Test Event in -the CalConnect _Minutes_ newsletter publised after each event. - -=== Updated IETF Drafts Related to CalConnect (includes updates to published CalConnect documents) - -* http://tools.ietf.org/html/draft-daboo-webdav-sync -* http://tools.ietf.org/html/draft-cal-resource-schema -* http://tools.ietf.org/html/draft-daboo-et-al-icalendar-in-xml -* http://tools.ietf.org/html/draft-daboo-calendar-availability -* http://tools.ietf.org/html/draft-douglass-link-extension - -== Update on Technical Committee Work and Initiatives - -Roundtable session summaries and activities may be found at -http://calconnect.org/minutes/CalConnect%20Minutes%20May2011.pdf. - -== Future Events - -* CalConnect XXII: October 3-7, 2011, Kerio Technologies, Czech Republic -* CalConnect XXIII: January 30 - February 3, 2012, TBD -* CalConnect XXIV: May 21-25, Patricia Egen Consulting, Chattanooga, TN - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, -BOFs, networking, Plenary) diff --git a/sources/csd-report-roundtable-22.adoc b/sources/csd-report-roundtable-22.adoc deleted file mode 100644 index 0db2cd0..0000000 --- a/sources/csd-report-roundtable-22.adoc +++ /dev/null @@ -1,107 +0,0 @@ -= Report on Roundtable XXII, October 5-7, 2011 -:docnumber: 1106 -:copyright-year: 2011 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2011-11-07 -:published-date: 2011-11-07 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXII took place on October 5-7, 2011, hosted by Kerio Technologies in Prague, -Czech Republic. The event was attended by 22 people from 14 organizations. The CalConnect -Interoperability Test Event was held immediately prior to the Roundtable on October 3-5. Fifteen -people from 8 organizations were present onsite. plus one remotely. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -The Roundtable was structured with all regular TC sessions occurring in the afternoon to facilitate -remote participation via GotoMeeting for individuals in North America. Thursday and Friday -mornings were used for special symposia and workshops: - -* The Evolution of Internet Calendaring and Scheduling -* Integrating Internet Calendaring Standards into products and services -* Workshop on Tasks (VTODOs) -* BOF: CalConnect Internationally - next steps -* BOF: Autodiscovery - -The host session was chaired by Pavel Suk of Kerio, and focused ways to drive adoption of -CalDAV and CardDAV on mobile devices by simplifying provisioning and other techniques to -reduce complexity for end users. - -== Documents Updated since Last Roundtable - -=== Updated IETF Drafts related to CalConnect (includes updates to published CalConnect documents) - -* http://tools.ietf.org/html/rfc6321 -* http://www.rfc-editor.org/rfc/rfc6350.txt -* http://www.rfc-editor.org/rfc/rfc6351.txt -* http://www.rfc-editor.org/rfc/rfc6352.txt -* http://tools.ietf.org/html/draft-daboo-icalendar-extensions -* http://tools.ietf.org/html/draft-daboo-valarm-extensions/ -* http://tools.ietf.org/html/draft-desruisseaux-caldav-sched -* http://tools.ietf.org/html/draft-daboo-webdav-sync -* http://tools.ietf.org/html/draft-cal-resource-schema -* http://tools.ietf.org/html/draft-daboo-webdav-sync/ -* http://tools.ietf.org/html/draft-douglass-timezone-service/ - -CalConnect has replaced the internal Interoperability Test Event Report with an internal wiki, and -the public Interoperability Test Report with a section on the Test Event in the CalConnect _Minutes_ -newsletter publised after each event. - -== Update on Technical Committee Work and Initiatives - -Roundtable session summaries and activities and a report on the Interoperability Test Event may -be found at http://calconnect.org/minutes/CalConnect%20Minutes%20Nov2011.pdf. - -== Future Events - -* CalConnect XXIII: January 30 - February 3, 2012, Apple Inc., Cupertino, California -* CalConnect XXIV: May 21-25, 2012, Patricia Egen Consulting, Chattanooga, Tennessee -* CalConnect XXV: October 1-5, 2012, TBD - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, -BOFs, networking, Plenary) diff --git a/sources/csd-report-roundtable-23.adoc b/sources/csd-report-roundtable-23.adoc deleted file mode 100644 index e32fb36..0000000 --- a/sources/csd-report-roundtable-23.adoc +++ /dev/null @@ -1,98 +0,0 @@ -= Report on Roundtable XXIII, February 1-3, 2012 -:docnumber: 1201 -:copyright-year: 2012 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2012-02-15 -:published-date: 2012-02-15 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXIII took place on February 1-3, 2012, hosted by Apple in Cupertino, California. -The event was attended by 35 people from 16 organizations. The CalConnect Interoperability Test -Event was held immediately prior to the Roundtable on January 30 - February 1. Twenty-one -people from 8 organizations were present onsite, including representatives from five different -areas in Apple. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -Two "implementation" BOFS were held during the Interoperability Test Event on Monday and -Tuesday afternoons: - -* Update versus replacement of calendar and contact data -* Auto-discovery and account provisioning - -We expect the findings and output from the BOFs to inform future work in CalConnect, either in -the context of one or more existing Technical Committees or in possibly forming new Technical -Committees. The host session was chaired by Wilfredo Sánchez of Apple, and discussed the -adoption and implementation of open standards in Apple's calendaring products. - -== Documents Updated since Last Roundtable - -=== Updated IETF Drafts related to CalConnect (includes updates to published CalConnect documents) - -* http://tools.ietf.org/html/draft-daboo-webdav-sync -* http://tools.ietf.org/html/draft-cal-resource-schema -* http://tools.ietf.org/html/draft-douglass-timezone-service/ - -CalConnect has replaced the internal Interoperability Test Event Report with an internal wiki, and -the public Interoperability Test Report with a section on the Test Event in the CalConnect _Minutes_ -newsletter publised after each event. - -== Update on Technical Committee Work and Initiatives - -Roundtable session summaries and activities and a report on the Interoperability Test Event may -be found at http://calconnect.org/minutes/CalConnect%20Minutes%20Feb2012.pdf. - -== Future Events - -* CalConnect XXIV: May 21-25, 2012, Patricia Egen Consulting, Chattanooga, Tennessee -* CalConnect XXV: October 1-5, 2012, Google, Zurich, Switzerland -* CalConnect XXVI: January 28 - February 1, 2013, TBD -* CalConnect XXVII: June 3-7, 2012, University of Wisconsin, Madison, Wisconsin - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, -BOFs, networking, Plenary) diff --git a/sources/csd-report-roundtable-24.adoc b/sources/csd-report-roundtable-24.adoc deleted file mode 100644 index c6366eb..0000000 --- a/sources/csd-report-roundtable-24.adoc +++ /dev/null @@ -1,104 +0,0 @@ -= Report on Roundtable XXIV, May 23-25, 2012 -:docnumber: 1203 -:copyright-year: 2012 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2012-06-01 -:published-date: 2012-06-01 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXIV took place on May 23-25, 2012, hosted by Patricia Egen Consulting in -Chattanooga, Tennessee. The event was attended by 17 people from 11 organizations. The -CalConnect Interoperability Test Event was held immediately prior to the Roundtable on May 21- -23. Nine people from 4 organizations were present onsite, and one individual and implementation -participated remotely. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -Two "implementation" BOFS were planned to be held during the Interoperability Test Event on -Monday afternoon: - -* CalDAV Test Suites and Performance Testing -* Shared Address Books - -In the even the CalDAV Test Suites and Performance Testing BOF was held on Thursday -afternoon due to lack of time. - -A special BOF on Autodiscovery was also held Wednesday afternoon as a follow-on to BOFs in -February and last October, and it was decided to form a Technical Committee to work in this area. - -== Documents since Last Roundtable - -=== Public Review Documents - -* CalWS-SOAP SOAP Web Services Protocol for Calendaring - -=== Updated IETF Drafts and Proposed Standards related to CalConnect (includes updates to published CalConnect documents) - -* https://tools.ietf.org/html/draft-desruisseaux-caldav-sched-12 -* https://www.ietf.org/rfc/rfc6578.txt -* https://datatracker.ietf.org/doc/draft-cal-resource-vcard/ -* http://tools.ietf.org/html/draft-douglass-timezone-service/ - -CalConnect has replaced the internal Interoperability Test Event Report with an internal wiki, and -the public Interoperability Test Report with a section on the Test Event in the CalConnect _Minutes_ -newsletter publised after each event. - -== Update on Technical Committee Work and Initiatives - -Roundtable session summaries and activities and a report on the Interoperability Test Event will -be available as part of the CalConnect _Minutes_ newsletter to be published shortly. Once it is -available this entry will be changed to link to the newsletter. - -== Future Events - -* CalConnect XXV: October 1-5, 2012, Google, Zurich, Switzerland -* CalConnect XXVI: January 28 - February 1, 2013, Oracle, San Francisco Bay Area, California -* CalConnect XXVII: June 3-7, 2012, University of Wisconsin, Madison, Wisconsin - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, -BOFs, networking, Plenary) diff --git a/sources/csd-report-roundtable-25.adoc b/sources/csd-report-roundtable-25.adoc deleted file mode 100644 index ec794ef..0000000 --- a/sources/csd-report-roundtable-25.adoc +++ /dev/null @@ -1,121 +0,0 @@ -= Report on Roundtable XXV, October 3-5, 2012 -:docnumber: 1204 -:copyright-year: 2012 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2012-10-18 -:published-date: 2012-10-18 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXV took place on October 3-5, 2012, hosted by Google in Zürich, Switzerland. The event -was attended by 26 people from 11 members and 5 non-members. The CalConnect Interoperability Test -Event was held immediately prior to the Roundtable on October 1-3. Twenty-two people from 10 members -and 2 non-members were present onsite, and four members participated remotely. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and networking, -with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical Committee sessions -were as usual organized sequentially, without competing parallel sessions, as is our standard practice to -allow all attendees who wished to be involved in the discussions of each Technical Committee the -opportunity to do so. - -== Special Events - -The Roundtable was structured with all regular TC sessions occurring in the afternoon to facilitate remote -participation (in particular from North America) for the TC sessions. Thursday and Friday mornings were -used for special symposia and BOFs: - -* Improving the web calendaring experience for end users -* Calendaring futures and CalConnect directions -* Internationalization/Localization for calendaring data -* Best practices for publishing iCalendar data to ensure optimum interoperability -* BOF on VTODOs -* BOF on Consensus Scheduling - -Following the BOF on VTODOs, a VTODO Ad Hoc Committee was formed to examine requirements and -ongooing work on VTODOs and recommend future activity in this area to CalConnect. The Ad Hoc -committee will report out at Roundtable XXVI. - -The host session was presented by Fabian Schlup of Google and focused on various aspects of Google -Calendar including internal and external APIs. - -== Documents since Last Roundtable - -=== Public Review Documents - -* CalWS-SOAP SOAP Web Services Protocol for Calendaring - -=== Updated IETF Drafts and Proposed Standards (published RFCs) related to CalConnect (includes updates to published CalConnect documents) - -NOTE: The majority of specification work in CalConnect is necessarily focused on work to become internet draft -submissions to the IETF and ultimpately be progressed to become RFCs (Proposed Standards), rather -than be directly published by CalConnect itself. - -* https://tools.ietf.org/html/draft-daboo-calendar-availability-03 -* https://tools.ietf.org/html/draft-daboo-icalendar-extensions-05 -* https://datatracker.ietf.org/doc/draft-daboo-ical-vcard-parameter-encoding/ -* https://tools.ietf.org/html/draft-daboo-valarm-extensions-04 -* https://www.ietf.org/rfc/rfc6638.txt[Scheduling Extensions to CalDAV RFC 6638] -* http://svn.calendarserver.org/repository/calendarserver/CalendarServer/trunk/doc/Extensions/caldavsharing.txt -* https://tools.ietf.org/html/draft-daboo-ical-vcard-parameter-encoding-01 -* https://datatracker.ietf.org/doc/draft-murchison-webdav-prefer/ -* https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/ - -CalConnect has replaced the internal Interoperability Test Event Report with an internal wiki and -etherpads, and the public Interoperability Test Report with a section on the Test Event in the CalConnect -_Minutes_ newsletter publised after each event. - -== Update on Technical Committee Work and Initiatives - -Roundtable session summaries and activities and a report on the Interoperability Test Event are published -after each CalConnect event as part of the CalConnect _Minutes_ newsletter, to be published shortly. Issues -of the newsletter may be found at CalConnect _Minutes_. - -== Future Events - -* CalConnect XXVI: January 28 - February 1, 2013, Oracle, San Francisco Bay Area, California -* CalConnect XXVII: June 3-7, 2013, University of Wisconsin, Madison, Wisconsin -* CalConnect XVIII: Autumn, 2013 (late September/early October), TBD - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, BOFs, -networking, Plenary) - -This format has been altered for the two (so far) European CalConnect events to move all TC sessions to -the afternoon and offer symposia and BOFs during Thursday and Friday mornings. diff --git a/sources/csd-report-roundtable-26.adoc b/sources/csd-report-roundtable-26.adoc deleted file mode 100644 index 9795dd3..0000000 --- a/sources/csd-report-roundtable-26.adoc +++ /dev/null @@ -1,261 +0,0 @@ -= Report on Roundtable XXVI, January 30 - February 1, 2013 -:docnumber: 1302 -:copyright-year: 2013 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2013-02-20 -:published-date: 2013-02-20 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: -:imagesdir: images/roundtable-26 - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -NOTE: Incorporates material formerly distributed via the CalConnect _Minutes_ newsletter, now discontinued. - -Roundtable XXVI took place on January 30 - February 1, 2013, hosted by Oracle in Santa Clara, California. The Roundtable was -attended by 29 people from 16 members and 3 non-members. The CalConnect Interoperability Test Event was held immediately -prior to the Roundtable on January 28-30. Nineteen people from 9 members were present onsite, and 2 members participated -remotely. In total, 36 people attended, including 2 from Europe, 1 from India, and 1 from New Zealand. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and networking, with an all-hands -Plenary meeting as the last item on Friday afternoon. The Technical Committee sessions were as usual organized sequentially, -without competing parallel sessions, as is our standard practice to allow all attendees who wished to be involved in the -discussions of each Technical Committee the opportunity to do so. - -== Special Events - -Wednesday afternoon, January 30th, was dedicated to the Consensus Scheduling Workshop. The workshop was open to the public -with prior registration and drew three participants from non-members. The workshop was announced on the -https://calconnect.wordpress.com/2012/12/13/calconnect-consensus-scheduling-workshop-january-30-2013-at-calconnect-roundtable-xxvi/[CalConnect Blog Workshop Announcement] -and the post-workshop report will also be posted to the blog. - -== Documents since Last Roundtable - -Much of the work in CalConnect is necessarily focused on specifications to -become internet draft submissions to the IETF and ultimately be progressed to -become RFCs (Proposed Standards), rather than be directly published by CalConnect itself. - -=== Published Documents - -* 7 Things You Should Know About Consensus Scheduling -* CalWS-SOAP SOAP Web Services Protocol for Calendaring -* Report on Roundtable XXV - -=== New Internet Drafts Submitted to IETF - -* https://tools.ietf.org/html/draft-york-vpoll-00[VPOLL: Consensus Scheduling Component for iCalendar] -* https://datatracker.ietf.org/doc/draft-vcard-objectclass/[Objectclass property for Card] -* https://datatracker.ietf.org/doc/draft-vcard-schedulable/[Schedulable Objectclass for vCard] -* https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery] - -=== Updated Internet Drafts and Published RFCs - -* https://tools.ietf.org/html/draft-douglass-calendar-extension-02[Event Publishing Extensions to iCalendar] -* https://tools.ietf.org/html/draft-kewisch-et-al-icalendar-in-json-01[jCal: The JSON format for iCalendar] -* https://tools.ietf.org/html/draft-daboo-icalendar-extensions-06[New Properties for iCalendar] -* https://datatracker.ietf.org/doc/rfc6868/[Parameter Value Encoding in iCalendar and vCard] -* https://datatracker.ietf.org/doc/draft-cal-resource-vcard/[vCard Representation of Resources] -* https://datatracker.ietf.org/doc/draft-murchison-webdav-prefer/[Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)] -* https://tools.ietf.org/html/draft-douglass-timezone-service-07[Timezone Service Protocol] - -== Update on Technical Committee Work and Initiatives - -=== TC AUTODISCOVERY - -We discussed the status of the current draft which has now -https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[moved over for consideration in the IETF]. -Recent changes include a -switch to using JSON instead of XML. The IETF should be holding a BOF at the next IETF meeting to develop interest there -with a view to setting up a working group to develop the specification further. The TC will in the future work on supporting the -IETF effort and promote interoperability testing at CalConnect. - -=== TC CALDAV - -* Described latest modification to the -https://tools.ietf.org/html/draft-daboo-caldav-attachments-01[managed attachment] draft. -Really productive conversation around identifying a -managed attachment. -* Presented the proposed http://svn.calendarserver.org/repository/calendarserver/CalendarServer/trunk/doc/Extensions/caldav-sharing.txt[calendar sharing model]: some issues were raised around scalability of the solution for people -managing large number of calendars. -* CardDAV sharing: 2 possible approaches were discussed (group level or address book sharing). -* Calendar Searching: discussed the bootstrap process: what should be the target URI for calendar search reports. - -=== TC EVENTPUB - -We briefly covered the state of the new properties defined for event publishing, STRUCTURED-LOCATION, PARTICIPANT, -STRUCTURE-RESOURCE and STYLED-DESCRIPTION. These have been described and discussed at previous Roundtables so -this was largely a status report. The -https://tools.ietf.org/html/draft-douglass-calendar-extension-02[internet draft has been refreshed] -and there are a number of comments to be circulated to the -group and discussed. - -Most of the session was taken up discussing the need for new properties to enable enhancements in itineraries. Examples are the -need to specify starting and ending locations for events, chaining of events and tasks, and properties to hold information such as -flights. It was agreed that detailed information may be better kept elsewhere with well-defined references to that information. -Next steps for itineraries involve a discussion of needs and identifying which TC or TCs will handle the work. It is hoped that -writing a "7 Things You Should Know About Itineraries" or a white paper may help attract new members to the TC. The other -https://tools.ietf.org/html/draft-daboo-icalendar-extensions-06[extensions draft] -which covers images has also been refreshed, and in the next few weeks we will discuss how to make progress -with both drafts. - -=== TC FREEBUSY - -The TC hosted the Consensus Scheduling Workshop on Wednesday afternoon. The workshop covered the key aspects of -consensus scheduling and described CalConnect's proposed solution: -https://tools.ietf.org/html/draft-york-vpoll-00[VPOLL]. -The workshop started with a detailed overview of -what consensus scheduling is, why people use it, and why standards - currently lacking - would enhance the process. This was -followed by overviews of various products that do some form of consensus scheduling or booking. We then had a detailed -overview of the VPOLL specification, covering the key elements and recent changes made by the TC. This included a description -of how the POLL-MODE property will be used to define various modes and levels of complexity for polls. Initially there will be a -simple "basic" mode that will be used as the basis for initial interoperability testing and will be used to encourage implementors to -develop products. Going forward the TC will work on refinements to the VPOLL specification based on feedback from -implementors. We plan on VPOLL testing at the next Interoperability Test Event event. - -=== TC IOPTEST - -The interoperability testing sessions were fairly busy and featured both new and established testers. There was a significant -amount of work testing many of the basic CalDAV functions and beyond that to testing implicit scheduling. Some of us spent -most of our time working on iSchedule, testing the new DKIM canonicalization. This was a successful test with events and -freebusy being transferred. Most problems related to the non-standard disposition of the services. There was some work in getting -the CalDAV test and performance suites running. In addition there was some timezone service testing with the new JSON format -and a certain amount of iMIP. - -A useful feature of the sessions was the occasional informal discussions which involved most of the participants. We covered -some of the detailed issues related to sharing and notifications. - -=== TC ISCHEDULE - -After an general introduction to https://tools.ietf.org/html/draft-desruisseaux-ischedule-04[iSchedule], -we reviewed presented the main changes in Draft 03. - -Interoperability testing feedback: - -* 4 Servers participated in the tests -* Successfully tested new canonicalization algorithm - -IETF status: - -* Trying to get a working group started, most likely via DOSETA. We reviewed the process required to do so. -* CalConnect members need to show interest in order to justify working group in the IETF -* Some IPR issues with DKIM; the IETF working group will have to deal with it before we can proceed. - -=== TC RESOURCE - -We had a short session where we reviewed the work of the TC to date, current discussions, and work remaining. The new -https://datatracker.ietf.org/doc/draft-vcard-objectclass/[vCard objectclass property] -and its value of a https://datatracker.ietf.org/doc/draft-vcard-schedulable/[schedulable] -was introduced and we went over an example of how it would be used. The TC is working on 3 -drafts to get the work standardized - those just mentioned plus -https://datatracker.ietf.org/doc/draft-cal-resource-vcard/[vCard Representation of Resources]. - -=== TC TIMEZONE - -The current state of the https://tools.ietf.org/html/draft-douglass-timezone-service-07[Timezone Service Protocol] -was presented. The only change is from an XML based approach to JSON. -This approach is more in line with the expected use by web developers. The main outstanding service issue is how to deal with -inactive timezones. While there appear to be about 80 timezones currently in use there are over 400 in the Olson database. We -discussed timezones by reference: that is, servers don't send timezone data and clients use their own cached copy. This is largely -in line with current practice though not in line with the specifications. We talked about a registry for timezone related information -and how we should proceed. Finally the issue of allowing a TZID for DATE values was mentioned - RFC5545 disallows it, but -users want it. - -=== TC USECASE - -Lively first discussion about the merits of calendar user community involvement in CalConnect and possible ways to enhance -CalConnect discovery (that is, finding out CalConnect exists and what it is), to provide useful value to the user community, plus -some concrete first steps CalConnect can take to support the commerce of ideas and needs between user and vendor communities. - -=== TC XML - -We reviewed the history of https://tools.ietf.org/html/rfc6321[xCal: the XML format for iCalendar], -how we developed the SOAP and RESTful CalWS protocols and -how we had influenced the development of WS-Calendar within OASIS for the SmartGrid. The current state of the jCal data -model was described and we finished up by agreeing to try to get server side libraries working for the next Roundtable. - -=== VTODO AD HOC - -The session covered the proposed charter and work items that the Ad Hoc has been working on since the last Roundtable. We -have carefully analyzed the requirements for improving task handling in iCalendar, prioritizing the work we think needs to be -done. We looked at other task-based systems, including WSHumanTask, to inform our work. In addition, we took care to rule out -certain issues to keep the scope of any TC constrained to a reasonable set of deliverables. The Ad Hoc anticipates that a number -of items will re-use work done in other TCs. At this point we proposed that a TC be setup in CalConnect to move forward with -this work, and expect a decision on setting up a TC to be made during the Roundtable Plenary. TC TASKS was approved, and we -will move ahead with the work items. - -== Plenary Decisions - -A new TC TASKS technical committee was created to carry out the work program identified by the VTODO Ad Hoc Committee, -which reported out at this event recommending the formation of such a new TC. - -We have accepted an offer from http://www.dhl.com[DHL Express] to host the Autumn 2013 CalConnect event at their ITS Data Center in Prague, -Czech Republic, the week of September 23-27, 2013. - -== Future Events - -* CalConnect XXVII: June 3-7, 2013, University of Wisconsin, Madison, Wisconsin -* CalConnect XXVIII: September 23-27, 2013, DHL Express, Prague, Czech Republic -* CalConnect XIX: Winter, 2014, TBD - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, BOFs, networking, Plenary) - -This format has been altered for the two (so far) European CalConnect events to move all TC sessions to the afternoon and offer -symposia and BOFs during Thursday and Friday mornings. - -== Photos from CalConnect XXVI - -[%unnumbered,cols="a,a"] -|=== -| [%unnumbered] -image::CC26-01.jpg[] -| [%unnumbered] -image::CC26-02.jpg[] -| [%unnumbered] -image::CC26-03.jpg[] -| [%unnumbered] -image::CC26-04.jpg[] -| [%unnumbered] -image::CC26-05.jpg[] -| [%unnumbered] -image::CC26-06.jpg[] -| [%unnumbered] -image::CC26-07.jpg[] -| [%unnumbered] -image::CC26-08.jpg[] -|=== \ No newline at end of file diff --git a/sources/csd-report-roundtable-27.adoc b/sources/csd-report-roundtable-27.adoc deleted file mode 100644 index fbffaed..0000000 --- a/sources/csd-report-roundtable-27.adoc +++ /dev/null @@ -1,266 +0,0 @@ -= Report on Roundtable XXVII, June 5-7, 2013 -:docnumber: 1304 -:copyright-year: 2013 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2013-07-08 -:published-date: 2013-07-08 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXVII took place on June 5-7, 2013, hosted by the University of Wisconsin in -Madison, Wisconsin. The Roundtable was attended by 22 people from 13 members, including 3 -new members. The CalConnect Interoperability Test Event was held immediately prior to the -Roundtable on June 3-5, and had 13 participants from 7 members. In total, 28 people attended -some portion of the week, including three from Europe and one from New Zealand. - -The Roundtable was dedicated to technical committee sessions, and informal discussions and -networking, with an all-hands Plenary meeting as the last item on Friday afternoon. The Technical -Committee sessions were as usual organized sequentially, without competing parallel sessions, as -is our standard practice to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. - -== Special Events - -Two special BOFs were held on Wednesday, June 5. Wednesday morning a BOF on Federated -Shared Calendars was held; the timing permitted both Interoperability Test Event and Roundtable -participants to attend. Wednesday afternoon was a BOF on Travel Itineraries. CalConnect will -form an Ad Hoc Group on the former later this summer, and will host a public workshop on Travel -Itineraries at the Prague meeting in September. - -== Documents since Last Roundtable - -Much of the work in CalConnect is necessarily focused on specifications to become internet draft submissions to the -IETF and ultimately be progressed to become RFCs (Proposed Standards), rather than be directly published by -CalConnect itself. - -=== Published documents - -* 7 Things You Should Know About Tasks -* Report on Roundtable XXVI -* Report on Interoperability Test Event XXVI - -=== New Internet Drafts Submitted to IETF - -* https://datatracker.ietf.org/doc/draft-daboo-icalendar-rscale/[Non-Gregorian Recurrence Rules in iCalendar] - -=== Updated Internet Drafts and Published RFCs - -* https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery] -* https://tools.ietf.org/html/draft-douglass-calendar-extension/[Event Publishing Extensions to iCalendar] -* https://tools.ietf.org/html/draft-desruisseaux-ischedule/[Internet Calendar Scheduling Protocol (iSchedule)] -* https://tools.ietf.org/html/draft-kewisch-et-al-icalendar-in-json/[jCal: The JSON format for iCalendar] -* https://datatracker.ietf.org/doc/rfc8144/[Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)] -* https://tools.ietf.org/html/draft-douglass-timezone-service/[Timezone Service Protocol] -* https://datatracker.ietf.org/doc/draft-cal-resource-vcard/[vCard representation of resources] -* https://datatracker.ietf.org/doc/rfc7095/[jCard: The JSON format for vCard] (now an IETF WG draft) - -== Update on Technical Committee Work and Initiatives - -=== CALSCALE-ADHOC - -Presented a problem statement and our proposed approach. The draft is now at the IETF: -https://datatracker.ietf.org/doc/draft-daboo-icalendar-rscale/[Non-Gregorian Recurrence Rules in iCalendar]. -There was a discussion on RPATTERN vs RRULE, "L" -suffix vs BYLEAPMONTH. The outcomes were: - -. Give a call to all calendar services and clients to fail if they encounter unfamiliar term in -RRULE -. Verify that no major client interprets RSCALE as a wrong recurrence (in Gregorian) -. Try to stick with RRULE and "L" suffix, pending discussion @IETF -. Keep discussion on calsify@ietf -. Have a one-off call after the Roundtable to determine further courses of action - -=== TC AUTODISCOVERY - -The draft has been updated to use JSON -https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery]. -Most of the presentation -was on TC goals and motivation so there were no technical updates during the roundtable. For the -next few months the activity will take place mainly on the IETF where we expect discussion -mostly about what we have now versus WebFinger. - -=== TC CALDAV - -After a status update on the pending IETF drafts, we discussed the remaining open issues on two -of them: managed attachment and prefer header. We then had an open discussion on calendar -sharing and calendar searching. - -=== TC EVENTPUB - -The first part of the session was a review of the extensions specification and the properties and -parameters defined there. Since the last round table we've defined a new GROUP parameter to -allow grouping of related properties. This has expected uses outside of event publication - in -particular tasks. The PARTICIPANT property has now been renamed to ASSOCIATE. There were -suggestions about the role of ASSOCIATE and how it relates to ATTENDEE. There are no iTIP -semantics for ASSOCIATE so no broadcasting of data to potentially very large numbers of users. -The specification was resubmitted at the beginning of the week and needs some review and then -trying to move it on to the next stage in the IETF. - -We also talked (again) about sharing and subscriptions. Of particular interest in event publication -is the ability to register for a specific event. Related to that is the ability to signify interest in -selected events or tasks and have those appear in the users calendar client and for that user to -receive notifications of changes. Bedework implements a special collection type in which such -events appear. - -=== TC FREEBUSY - -We reviewed the current work of the committee and the VPOLL specification, and additionally -discussed "office hours" and "reverse scheduling" as examples of ways that VPOLL (and -VAVAILABILITY) may be used for innovative ways of scheduling. - -=== TC IOPTEST - -12 attendees representing 5 organizations (with 1 observing) tested and developed features in the -areas of CalDAV, VPOLL, WebDAV Sync, Calendar Sharing and Timezones. Some attendees also -spent time working with the Apple test suite and the Apple performance suite. We spent some time -discussing various issues at the technical level, including VPOLL, issues with locating a service -when all we have is the CUA, etc. - -We also discussed how CalConnect can better organize the sessions to get newer attendees rapidly -paired up with each other for testing. We will talk about this more on some of the upcoming TC -calls but the approach will probably be to allocate n hour or so at the very start to discuss the -testers' needs and who can help them resolve their outstanding issues. - -There has also been some discussion on finding a way to emphasize the value of these (test event -discussion) sessions as a forum for developers which involves more than testing clients and -servers. The various BOFs have been a step along that path. - -=== TC ISCHEDULE - -Presented a status update on the iSchedule draft, and discussed the possible disconnect between -email provider and calendar provider and how this affects the iSchedule work flow. - -=== TC RESOURCE - -Presented the work done so far by the committee and the drafts produced. Discussed searching and -finding the right resource for scheduling. The conclusion was that we need to define something for -easy search for scheduling based on certain user-provided criteria, not limited to resources. - -=== TC TASKS - -Good progress since last roundtable in areas of: - -* STATUS / PARTSTAT with new status values and parameters -* ORGANIZATION and other roles -* Task Definitions -- identification of the task type -* Task Relationships with recommendations for new RELTYPE values and a new parameter -(GAP) - -After the roundtable report the key discussion points were on: - -* Requirements for notifications in relation to calendar sharing -* Relationships -* The use of a RELATED-ID for identifying projects -* Clarification on project management RELTYPES and DEPENDS-ON as a back pointer - -Next steps will focus on consolidating what we have so far in to drafts and developing the other -areas in scope for the TC: - -* Task specific data -* Task assignments -* Deadlines / alarms / escalations -* Resulting API / Protocol changes - -=== TC TIMEZONE - -We presented the current state of the timezone work. We have a draft (expired) at the IETF which -represents the current state of the servers. This is ready for last call so we should progress it -through the IETF. Additional work, which does not require spec changes, would be to add a new -content type related to the current zoneinfo format. This may encourage OS vendors to use a -timezone service. We talked about ways we might accelerate the dissemination of data. Some OS -providers already track the data and provide system updates. If they use a timezone service maybe -they could become a more timely source of data. We also talked about delivering timezones by -reference, that is drop the timezone component from icalendar files and see what clients do. It -appears they generally ignore the data anyway - as do servers. Aliases is another topic and we -need to build up a good set of aliases that we can use in our servers. Unicode Consortium has a list -that we can probably extract. - -=== TC USECASE - -Presented recommendations to attending members for actions CalConnect can take regarding -CalConnect visibility and membership activity: - -* Establish a regular presentation on "State of the User Experience" -* Fold UseCase into USIG -* Establish a regular, non-structured RoundTable session dedicated to, or focused-on, a user -constituency problem, issue, or topic -* Establish a focus on Social Media and online methods as a means of outreach and raising -CalConnect visibility - -Voice votes taken during the TC-WrapUp session were supportive for all four recommendations. - -=== TC XML - -We had a short session in which we brought people up to date: - -* The xCal spec is unchanged and no further issues reported -* CalWS-SOAP and REST are now official OASIS standards. Both will be worked on to -* handle the other features available in CalDAV - synch, vpoll etc. -* jCal and jCard are progressing well and ready for last call in the IETF - -We need to work on implementations and some testing of jCal and jCard. We talked briefly about -where TC-XML is headed. Possibly some role as liaison but maybe there are no more 'XML' -issues to resolve. - -== Plenary Decisions - -CalConnect accepts an offer from http://www.aol.com[AOL] to host the Spring 2014 2013 CalConnect event at their -center in Dulles, Virginia, the week of May 19-23, 2014. - -CalConnect plans to hold workshops on Federated Shared Calendars and Travel Itineraries at the -September, 2013 CalConnect event in Prague. The Travel Itineraries workshop will be open to the -public by registration. - -CalConnect will develop ways to make it easier for new members and participants to become -familiar with and involved in the Roundtables, Interoperability Test Events, and the technical -work. - -== Future Events - -* CalConnect XXVIII: September 23-27, 2013, DHL Express, Prague, Czech Republic -* CalConnect XIX: Winter, 2014, TBD -* CalConnect XXX: May 19-23, 2014, AOL, Dulles, Virginia - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, -BOFs, networking, Plenary) - -This format has been altered for the two (so far) European CalConnect events to move all TC -sessions to the afternoon and offer symposia and BOFs during Thursday and Friday mornings. diff --git a/sources/csd-report-roundtable-28.adoc b/sources/csd-report-roundtable-28.adoc deleted file mode 100644 index 1001549..0000000 --- a/sources/csd-report-roundtable-28.adoc +++ /dev/null @@ -1,258 +0,0 @@ -= Report on Roundtable XXVIII, September 25-27, 2013 -:docnumber: 1306 -:copyright-year: 2013 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2013-10-10 -:published-date: 2013-10-10 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXVIII took place on September 25-27, 2013, hosted by DHL in Prague, Czech -Republic. The Roundtable was attended by 24 people from 15 members and one first-time nonmember -observer. The CalConnect Interoperability Test Event was held immediately prior to the -Roundtable on September 23-25, and had 14 participants onsite from 10 members and one firsttime -non-member, including one member testing remotely. In total, 25 people attended some -portion of the week, including six from North America, one from New Zealand, and the rest from -the U.K. and continental Europe. - -The Roundtable consisted primarily of technical committee sessions, workshops and BOFs. In -addition new member presentations were offered during the Opening Session, as was a special -session dedicated to reviewing a proposed restructuring of the Steering Committee. The sessions -were as usual organized sequentially without competing parallel sessions, as is our standard -practice, to allow all attendees who wished to be involved in the discussions of each Technical -Committee the opportunity to do so. The Roundtable finished with the CalConnect Plenary -Session on Friday afternoon. - -== Special Events - -Two workshops were held on Thursday and Friday mornings: Travel Itineraries and Calendaring, -and Federated Shared Calendars respectively. BOFs were also held on Friday morning on a -standardized PUSH mechanism for CalDAV, and a discussion on CalConnect's scope and -activities. - -Ad Hoc Committees to explore new work areas were formed for Calendaring APIs, Federated -Shared Calendars, and PUSH for CalDAV, and the existing Itinerary Ad Hoc was continued. These -Ad Hoc will recommend to CalConnect how to proceed in these areas. - -TC XML was closed as it has completed its charter and scope of work. Follow-own activity in the -area of Calendaring APIs will be explored by one of the new Ad Hocs. - -== Documents since Last Roundtable - -Much of the work in CalConnect is necessarily focused on specifications to become internet draft submissions to the -IETF and ultimately be progressed to become RFCs (Proposed Standards), rather than be directly published by -CalConnect itself. - -=== Published Documents - -* Getting Started at the CalConnect Interoperability Test Event -* Getting Started at the CalConnect Roundtable Technical Conference -* Report on Roundtable XXVII -* Report on Interoperability Test Event XXVII - -=== New Internet Drafts Submitted to IETF - -* https://datatracker.ietf.org/doc/draft-daboo-caldav-timezone-ref/[CalDAV: Timezones by Reference] - -=== Updated Internet Drafts and Published RFCs - -* https://tools.ietf.org/html/draft-daboo-icalendar-rscale-01[Non-Gregorian Recurrence Rules in iCalendar] -* https://tools.ietf.org/html/draft-douglass-ical-relations/[Support for iCalendar Relationships] -* https://datatracker.ietf.org/doc/html/draft-kewisch-et-al-icalendar-in-json/[jCal: The JSON format for iCalendar] -* https://datatracker.ietf.org/doc/rfc8144/[Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)] -* https://tools.ietf.org/html/draft-daboo-caldav-attachments/[CalDAV Managed Attachments] -* https://datatracker.ietf.org/doc/draft-daboo-icalendar-extensions/[New Properties for iCalendar] -* https://datatracker.ietf.org/doc/draft-ietf-jcardcal-jcard/[jCard: The JSON format for vCard] (now an IETF WG draft) - -== Update on Technical Committee Work and Initiatives Including BOFs and Workshops - -=== BOF - PUSH for CALDAV - -We had a good discussion on whether/how to add push notification support to CalDAV (and -WebDAV/CardDAV). It was clear there was a demand for some common way to push, maybe -using dufferent push implementations. We will start an Ad Hoc Committee to move forward with -this discussion and specify a TC charter. - -=== CALSCALE-ADHOC - -The draft has been updated following the last Roundtable: -https://tools.ietf.org/html/draft-daboo-icalendar-rscale-01[Non-Gregorian Recurrence Rules in iCalendar]. -There have been no changes to the presentation since Roundtable XXVII in June; the -presentation was repeated unchanged for those who were not at the June event. The draft -specification is at the IETF and we are working to generate additional and broader interest in it. -Libraries such as iCal4j have been updated to ensure that they will properly ignore the RSCALE -parameter on RRULE when encountered. Google hopes to be able to conduct interoperability -testing at CalConnect XXIX next February of their initial implementation of RSCALE. - -=== TC AUTODISCOVERY - -https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery]. -We presentated the current state of the draft - the protocol has a -new name: Automated Service Configuration. We showed a quick overview of how this protocol -will be of benefit to users. We had agreement that this would be a benefit to a lot of users, but we -really need buy in from client and OS system configuration, and IETF folks to move this forward. - -We will continue to pursue those avenues as well as setup actual demos of the technology as a -proof-of-concept. - -=== TC CALDAV - -We first presented the changes in version 02 of the managed attachment draft -https://tools.ietf.org/html/draft-daboo-caldav-attachments/[CalDAV Managed -Attachments]. -During the last interop, several new implementations of the managed attachment -draft have emerged, raising new questions. We did discuss those, as well as the last few open -issues remaining on the spec. We then had a very lively discussion around the notion of scheduling -object draft. There seemed to be an agreement that it is an area where we should spend some time -in the coming months. In our next call, we will discuss the prioritization of the various specs we -are working on. - -=== TC EVENTPUB - -We presented the two iCalendar extension specs that are being developed in this committee: -https://tools.ietf.org/html/draft-douglass-calendar-extension/[Event -Publication Extensions to iCalendar] and -https://tools.ietf.org/html/draft-daboo-icalendar-extensions[New Properties for iCalendar]. -The first specification adds -STYLED-DESCRIPTION, ASSOCIATE, STRUCTURED-LOCATION and STRUCTUREDRESOURCE. -We discussed the GROUP parameter (which probably has to be renamed). This -allows different properties to be associated with each other - e.g. DESCRIPTION with a -STYLED-DESCRIPTION. - -The second specification allows many more properties on the VCALENDAR component and adds -the COLOR and IMAGE properties. It also defines the DISPLAY parameter - indicating how an -image hould be used,and the EMAIL parameter for attendees and organizers. There was some -discussion on the use of CSS3 names for color ending in general (if not complete) agreement. The -issue of tzid on DATE was raised and discussed again - perhaps with less discernable consensus. - -=== TC FREEBUSY - -We presentated an overview of the VPOLL specification, which has not changed much since last -time. We then saw a protoype VPOLL client demo illustrating the advantages of integrating a -polling system directly with an existing calendaring and scheduling system such as CalDAV. - -=== TC IOPTEST - -A successful session testing some new features and as ever testing some of the more mature parts -of the protocol with new clients and servers. Tested jcal support for clients and servers. This -appears to be working very well. Timezones by reference was tested together with the associated -CalDAV extensions. Mostly sucessful with some minor issues to be resolved. Suggests we could -move ahead after the resolution of those issues. Some testing was done on the prefer header for -WebDAV and on managed attachments. We also tested VPOLL support including VPOLL in -JSON. Cyrus presented the CalDAV test suite (again) and provided further assistance in getting it -running. - -=== TC ISCHEDULE - -Discussion on "identity crisis". Presented 3 scenarios involving Webfinger redirect, iSchedule -redirect and iMIP based interaction. Identity crisis not solved but it looks like Webfinger is part of -the solution. - -=== TC RESOURCE - -The session reviewed the work done so far. We had a discussion on possible DAV extensions for -Resource discovery. Concentrating on extension of Principal properties to make search more -efficient. Digressed into search in general too. - -=== TC TASKS - -TC-TASKs has made good progress against the original scope and has now prepared two drafts: - -* https://tools.ietf.org/html/draft-douglass-ical-relations/[Support for iCalendar Relationships] - submitted as IETF draft -* Task-extensions - early draft - -Further discussion is required in the areas of task assignment and deadlines / escalations, which -will continue to the next Roundtable (XXIX). From the work done to date GAP, SUBSTATE and -the PREPARE status need to be revisited based on Roundtable feedback. In addition to this the -publication and maintenance of domain specific data (e.g. namespaced reason codes, substates, -related-ids etc) to support client customization is to be included in scope. Task time planning (e.g. -allocated time, estimated time) will be investigated as extension of scope beyond the current work -plan. - -=== TC TIMEZONE - -Described why we got where we are and presented the current state of the server specification. -The specification is now ready for last call at the IETF. Before we try to make progress with that -last step we intend trying to engage other groups, for example the ICU and OS or API maintainers. -We would like to see other implementations and uses. A discussion followed on some possible -extensions to the timezone service and changes to the way timezone data is currently maintained. - -=== TC XML - -Presented a description of the jCard and jCal formats with examples. jCard and jCal have made -good progress through the IETF and are approaching RFC status. Most current issues with the -specifications have been resolved and interop testing has shown that the fomat is relatively easy to -use. We agreed that TC-XML has achieved its charter and milestones and that we should now shut -it down. An Ad Hoc Committee will be set up to explore the remaining issue of calendaring APIs. - -=== WORKSHOP - Federated Shared Calendars - -The broad topic of federating shared calendars across different services was discussed and -explored. Several different use cases exist, some more complex than the others. There was broad -interest in continuing to work on this problem, to define use cases, break it down into manageable -pieces etc. An Ad Hoc Committee will be set up to continue this work. - -=== WORKSHOP - Travel Itineraries and Calendaring - -We had a presentation and discussion about how a standards based approach, using iCalendar, -could enhance the user experience with planning and managing travel itineraries. We determined -that it is important to get involvement from industry experts to determine their needs and the scope -of any problems to be solved. We will move forward by continuing with our Ad Hoc Committee, -trying to garner interest from outside parties. - -== Plenary Decisions - -The API Ad Hoc, FSC Ad Hoc, and PUSH Ad Hoc were established and the Itinerary Ad Hoc -continued to explore those areas of work and recommend ways forward. TC-XML was closed as it -had completed its charter. The follow-on API Ad Hoc Committee will continue TC-XML's focus -in the API area and maintain the OASIS WS-Calendar liaison activities. - -== Future Events - -* CalConnect XIX: Winter, 2014, TBD -* CalConnect XXX: May 19-23, 2014, AOL, Dulles, Virginia -* CalConnect XXXI: Autumn, 2014, TBD (probably Europe) - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, -BOFs, networking, Plenary) - -The format for European events is to move TC sessions to the afternoon and offer symposia and -BOFs during Thursday and Friday mornings. diff --git a/sources/csd-report-roundtable-29.adoc b/sources/csd-report-roundtable-29.adoc deleted file mode 100644 index 7a240e4..0000000 --- a/sources/csd-report-roundtable-29.adoc +++ /dev/null @@ -1,230 +0,0 @@ -= Report on Roundtable XXIX, February 5-7, 2014 -:docnumber: 1401 -:copyright-year: 2014 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2014-02-26 -:published-date: 2014-02-26 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable XXIX took place on February 5-7, 2014, hosted by Mozilla in San Francisco, -California. The Roundtable was attended by 31 people from 20 members and one first-time nonmember -observer. The CalConnect Interoperability Test Event was held immediately prior to the -Roundtable on February 3-5, and had 21 participants onsite from 11 members, plus two members -testing remotely. In total, 36 people attended some portion of the week, including two from Hong -Kong, one each from the Czech Republic, England, France, India, New Zealand and Switzerland, -and the remainder from North America. - -The Roundtable consisted primarily of technical committee sessions, workshops and BOFs. In -addition new member presentations were offered during the Opening Session, as was a special -session dedicated to reviewing the ongoing work on restructuring the Steering Committee. The -sessions were as usual organized sequentially without competing parallel sessions, as is our -standard practice, to allow all attendees who wished to be involved in the discussions of each -Technical Committee the opportunity to do so. The Roundtable finished with the CalConnect -Plenary Session on Friday afternoon. - -== Special Events - -A BOF on CardDAV Sharing led to the formation of a new Provisional Committee (formerly Ad -Hoc) on Contacts Sharing to report out at CalConnect XXX in May. - -A BOF on the iSchedule Domain Identifier led to agreement on a way forward with this -contentions issue which will be integrated into the work of TC ISCHEDULE. - -== Documents since Last Roundtable - -Much of the work in CalConnect is focused on specifications to become internet draft submissions to the IETF and -ultimately be progressed to become RFCs (Proposed Standards), rather than be directly published by CalConnect itself. - -=== Published Documents - -* Calendaring Service Architecture -* Task Architecture V0.4 -* Report on Roundtable XXIX -* Report on Interoperability Test Event XXIX -* 7 Things You Should Know About Digital Travel Itineraries -* 7 Things You Should Know About Tasks - -=== Updated internet drafts and published RFCs - -* https://tools.ietf.org/html/rfc7095[jCard: The JSON Format for vCard] (RFC 7095) -* https://tools.ietf.org/html/draft-daboo-icalendar-rscale-02[Non-Gregorian Recurrence Rules in iCalendar] -* https://tools.ietf.org/html/draft-douglass-ical-relations/[Support for iCalendar Relationships] -* https://tools.ietf.org/html/draft-kewisch-et-al-icalendar-in-json/[jCal: The JSON format for iCalendar] -* https://datatracker.ietf.org/doc/rfc8144/[Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)] -* https://tools.ietf.org/html/draft-daboo-caldav-attachments/[CalDAV Managed Attachments] -* https://datatracker.ietf.org/doc/draft-daboo-icalendar-extensions/[New Properties for iCalendar] -* https://tools.ietf.org/html/draft-douglass-timezone-service-10[Timezone Service Protocol] -* https://www.ietf.org/internet-drafts/draft-daboo-calendar-%20availability-04.txt[Calendar Availability](VAVAILABILITY) -* https://www.ietf.org/internet-drafts/draft-douglass-calendar-%20extension-04.txt[Event Publishing Extensions to iCalendar] - -== Update on Technical Committee Work and Initiatives Including BOFs and Workshops - -=== API Ad Hoc - -The API Ad Hoc Committee was formed at CalConnect XXVIII to evaluate a work area for -CalConnect on an Abstract API for Calendaring and Scheduling. The Ad Hoc recommended -forming a Technical Committee and had produced a draft charter, an outline of an abstract API -and some milestones, in addition to a draft Architecture for Calendaring and Scheduling. -Deliverables are expected to be a well specified abstract API and a simple instantiation of that API --- probably some sort of RESTful web api. Instantiation of the follow-on TC will occur shortly -after the conference. - -=== CALSCALE Ad Hoc - -The draft was updated following CalConnect XXVIII: -https://tools.ietf.org/html/draft-daboo-icalendar-rscale-02[Non-Gregorian Recurrence Rules in iCalendar]. -The Ad Hoc presented a short presentation was done of the RSCALE proposal and -draft to do recurrences in different calendar scales and to do arithmetic in these scales. The -primary requirement is to support non-Gregorian calendars while maintaining compatibility by -using Gregorian dates in the actual calendar entries. There are still some compatibility issues, -however one implementation has been done. The draft is moving forward at the IETF. - -=== FSC (Federated Shared Calendars) Ad Hoc - -The Ad Hoc continued the discussion of sharing and federated calendar sharing and alternative -models, and agreed to continue to move forward as an Ad Hoc pending identification of an agreed -common way forward. - -=== Itinerary Ad Hoc - -No session was held at the conference. The goal is to improve the user experience with itinerary -info from travel sites by extending iCalendar to incorporated needed information; however, we -need input from travel industry experts on what is needed. The Ad Hoc continues to look for -experts to inform the work. - -=== TC AUTODISCOVERY - -No TC session was held at this conference. The TC has produced an initial draft of a mechanism -for multiple service discovery via a single protocol for client setup and submitted to the IETF: -https://datatracker.ietf.org/doc/draft-daboo-aggregated-service-discovery/[Aggregated Service Discovery]. We are waiting for an opportunity to move this forward at the -IETF. - -=== TC CALDAV - -The TC described the latest changes in the VALARM Extensions draft and introduced a new -recurrence splitting topic which led to discussion on support for RANGE and on invitations -growing to unreasonable size. Additionally the latest changes to the managed attachments -specification were reviewed, and a discussion initiated on rich capabilities: there seems to be -enough interest to move forward with a spec. - -=== TC EVENTPUB - -Summarized the state of the 2 drafts that have been worked on with this TC, -https://tools.ietf.org/html/draft-douglass-calendar-extension/[Event Publication Extensions to iCalendar] and -https://tools.ietf.org/html/draft-daboo-icalendar-extensions[New Properties for iCalendar]. -Apart from a couple of changes both -are essentially ready to move forward to Last Call, and we will be able to demonstrate the use of -the new properties at the next interoperability test event. - -=== TC FREEBUSY - -The TC reviewed -https://tools.ietf.org/html/draft-york-vpoll-00[VPOLL: Consensus Scheduling Component for iCalendar] and had a demo of a -prototype web client supporting VPOLL. - -=== TC IOPTEST - -Had a successful and well attended Interoperability Test Event featuring 13 organizations and 23 -participants (2 remote). The test event will be reported on separately at -http://www.calconnect.org/eventreports.shtml#ioptestevents[CalConnect Interoperability Test Event Reports]. - -=== TC ISCHEDULE - -TC ISCHEDULE offered a brief introduction to iSchedule and discussed the "identity crisis" -(domain identifier) BOF and the results, followed by a discussion on Webfinger. Also discussed -how to develop understanding of and interest in deploying iSchedule. The TC will begin work on -a "7 things" document for iSchedule. - -=== TC PUSH - -CalConnect XXIX was the first conference since TC PUSH was established. The TC presented its -charter and the initial work on requirements and a 7 Things document. Some Push basics and -optimizations were discussed, as was HTTP long poll as a simple push protocol that serves as a -specific example for the framework. - -=== TC RESOURCE - -The TC session focused on how to find the additional information required by attendees and -organizers on locations and resources in calendar data and concluded that using the new structured -properties that allow inclusion of a link to more information is the way to go. The use of -information via vCards was preferred and clients will need to be able to parse vCard data and -possibly cache it. Also identified a need for an extension of CalDAV to include a principal -property pointing to related CardDAV. - -=== TC TASKS - -TC TASKS reviewed the work since CalConnect XXVII on relationships and the relationships -draft, extensions related to RELTYPE and defined formal versions to be registered, abd ab the ad -hoc approach for namespace tokens for specific applications. Also looked at the Task Architecture -V0.4 diagram worked on since the last conference - -=== TC TIMEZONE - -The TC reviewed the current state of the -https://tools.ietf.org/html/draft-douglass-timezone-service-10[Timezone Service Protocol] -draft, which has had -moderate changes since the last meeting, and reported on the interoperability testing results. The -service protocol draft is ready to move forward to informal last call in the IETF. - -== Plenary Decisions - -The Contacts Sharing Provisional Committee was established. The API, FSC, and Itinerary Ad -Hocs continue to explore these areas of work. - -The Plenary decided to change the term "Roundtable", used from CalConnect's inception for its -conference, to "CalConnect Conference" or "Conference". The term Ad Hoc (Committee) was -also changed to Provisional Committee. Going forward these terms will be used, although -historical documents and pages will not be changed. - -The offer from Kerio to host the Winter, 2015 meeting in San Jose was accepted. - -== Future Events - -* CalConnect XXX: May 19-23, 2014, AOL, Dulles, Virginia -* CalConnect XXXI: Autumn, 2014, Europe (host, location, exact dates TBD) -* CalConnect XXXII: January 26-30, 2015, Kerio Technologies, San Jose, California - -The general format of the CalConnect week is: - -* Monday morning through Wednesday noon, CalConnect Interoperability Test Event -* Wednesday noon through Friday afternoon, CalConnect Roundtable (presentations, TC sessions, -BOFs, networking, Plenary) - -The format for European events is to move TC sessions to the afternoon and offer symposia and -BOFs during Thursday and Friday mornings. diff --git a/sources/csd-report-roundtable-3.adoc b/sources/csd-report-roundtable-3.adoc deleted file mode 100644 index 6dbdf06c..0000000 --- a/sources/csd-report-roundtable-3.adoc +++ /dev/null @@ -1,120 +0,0 @@ -= Report on Roundtable III, 1-3 June 2005 -:docnumber: 0512 -:copyright-year: 2005 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2005-06-03 -:published-date: 2005-06-03 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -The second formal event of The Calendaring and Scheduling Consortium took place on 1-3 June, -2005, hosted by Duke University Durham, North Carolina. The event was attended by -representatives of seventeen Consortium members. The Roundtable event consisted of two days of -Technical Committee meetings, and an all-hands plenary meeting of the membership and -attendees. The first two days, a CalConnect Interoperability Eventt was held in parallel with the -Technical Committee meetings. The Technical Committee sessions were organized sequentially, to -allow all attendees who wished to be involved in the discussions of a Technical Committee the -opportunity to do so, and there was definitely "drift" between TC sessions and those participating -in the CalConnect Interoperability Event. - -== Update on Initiatives - -*Glossary Project*: The Calendaring Glossary should be ready for initial publication on the -Consortium website within the next few weeks; it is currently in Last Call within the Consortium. - -*Recurrence Questionnaire*: The results of the Recurrence Questionnaire conducted by TCRECURR -on the internet will be posted publicly to the Consortium website as soon as the results -document completes Final Call within the Consortium. - -*TC-REALTIME* has been on hold pending the completion of other work, and will begin its work -in mid to late June. - -*TC-MIN-IOP* was disbanded and folded into TC-IOPTEST. - -*External Communications*: The Consortium will be announcing an RSS feed for Calendaring -issues and announcements in the next several weeks. - -*New initiatives*: The Consortium is considering initiating work in three new areas, if there is -sufficient interest among existing and new members and if resources are available to work in these -areas: - -* Calendar user address discovery and calendar server discovery -* Cross domain security and access control -* Todos for project management - -== Calconnect Interoperability Event - -Participants in the CalConnect Interoperability Event included Isamet, Mozilla, Novell, Oracle, -and Rensselaer Politechnic Institute. The CalConnect Interoperability Event was focused on -CalDAV testing and tested three CalDAV servers and four clients with very positive results. The -results of the CalConnect Interoperability Event should be available soon and will be posted on -the Consortium website and delivered to the IETF. - -== Technical Committees - -All Calconnect Technical Committees met during the course of the Roundtable to review their -status and work to date with the entire set of attendees and to progress their work with the large -input from the Roundtable. Of particular note: - -TC-CALDAV has made its CalDAV test script available on the Consortium website (under -"Resources"). - -TC-CALSIFY has been re-chartered more explicitly as a coordination effort between Consortium -Technical Committees and the incipient IETF CALISFY working group. The intent is to feed -information to the working group as rapidly as possible and ensure that TC work being done for -consumption by the working group meets the needs of the WG. - -TC-EVENTPUB is developing a survey on Event Publication, which will be distributed as widely -as possible, and may require some level of publicity to draw attention to it. - -TC-IOPTEST has taken on the tasks associate with the former TC-MIN-IOP to determine the -"minimum interoperability subset" for iCalendar. This is in addition to TC-IOPTEST's charter to -plan for, develop and formalize the Consortium's CalConnect Interoperability Event testing. - -TC-RECURR is planning a second questionnaire to delve more deeply into some specific -recurrence issues identified by the first questionnaire. The Committee intends to have results and -recommendations by the next Consortium Roundtable, and make them available to the IETF -CALSIFY working group before the November IETF meeting. - -TC-TIMEZONE is conducting a questionnaire on Timezone implementations as part - -== Future Meetings - -The next meeting (Roundtable IV) will take place 13-15 September in San Francisco, hosted by -the Open Source Applications Foundation. The following meeting (Roundtable V) will take place -in mid-January in Provo, Utah, hosted by Novell, Inc. diff --git a/sources/csd-report-roundtable-4.adoc b/sources/csd-report-roundtable-4.adoc deleted file mode 100644 index b8ddac7..0000000 --- a/sources/csd-report-roundtable-4.adoc +++ /dev/null @@ -1,111 +0,0 @@ -= Report on Roundtable IV, 13-15 September 2005 -:docnumber: 0513 -:copyright-year: 2005 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2005-09-15 -:published-date: 2005-09-15 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable IV took place on 13-15 September, 2005, hosted by the Open Souce Applications -Foundation in San Francisco, California. The event was attended by 43 representatives from -seventeen Consortium members and four observers. The Roundtable event consisted of two days -of Technical Committee meetings, and an all-hands plenary meeting of the membership and -attendees. The first two days, a CalConnect Interoperability Event was held in parallel with the -Technical Committee meetings. The Technical Committee sessions were organized sequentially, to -allow all attendees who wished to be involved in the discussions of a Technical Committee the -opportunity to do so. - -== Update on Initiatives - -*Published documents*: The Consortium has published the Results of the Recurrence -Questionnaire, the Results of the Timezone Questionnaire, and the CalDAV Use Cases document. -The Min-IOP Use Cases Document, Timezone Recommendations, Timezone Registry/Resource -Recommendations, Calendaring Glossary and others are in preparation. - -*TC-CALSIFY* was disbanded as its function was duplicated by the TC-CHAIRS coordination -committee. - -*TC-REALTIME* will be rechartered and will act as a research TC to look at a variety of serverserver -issues and determine whether specific work needs to be undertaken in the area. - -*TC-AUTHENTICATE* (calendaring authentication and authorization) and *TC-MOBILE* -(calendaring on mobile devices) were chartered at this Roundtable. - -*External Communications*: The Consortium will be announcing an RSS feed for Calendaring -issues and announcements in the next several weeks. - -== Calconnect Interoperability Event - -Participants in the CalConnect Interoperability Event included EVDB, IBM, Isamet, Mozilla, -Novell, Oracle, OSAF, RPI (Rensselaer Polytechnic Institute) and Sun Microsystems. Results -from the CalConnect Interoperability Event are posted at Past CalConnect Interoperability Event -Reports. - -== Technical Committees - -All Calconnect Technical Committees met during the course of the Roundtable to review their -status and work to date with the entire set of attendees and to progress their work with the large -input from the Roundtable. Of particular note: - -TC-CALDAV has made its CalDAV test script available on the Consortium website (under -"Resources"). - -TC-EVENTPUB will complete its survey at the end of September. TC members are investigating -ways to extend iCalendar function in the area of location and are looking at alternatives including -vCard. - -TC-IOPTEST is accumulating a set of specific iCalendar and related test scripts with the plan to -develop them, in addition to other purpose-developed material, into a test suite. - -TC-RECURR intends to have results and recommendations by the next Consortium Roundtable, -and make them available to the IETF CALSIFY working group at the November IETF meeting. - -TC-TIMEZONE has completed its questionnaire on Timezone implementations and is developing -a recommendations document on the results of the questionnaire, and another document on the -subject of a Timezone Registry and a Timezone Resource. - -== Future Meetings - -The next meeting (Roundtable V) will take place 09-12 January, 2006, hosted by Novell in Provo, -Utah. Starting with this meeting, the CalConnect Interoperability Event will be conducted prior to -the beginning of the Roundtable. Specifically the IOP event will begin on on Monday the 9th, and -continue on Tuesday morning the 10th, followed by the Roundtable from Tuesday afternoon -through Thursday afternoon. (Participants found that trying to do both the CalConnect -Interoperability Event and the Roundtable TC sessions in parallel weren't working very well.) The -following meeting (Roundtable VI) will be held in mid-May; a host has not yet been established. diff --git a/sources/csd-report-roundtable-5.adoc b/sources/csd-report-roundtable-5.adoc deleted file mode 100644 index 9e071e2..0000000 --- a/sources/csd-report-roundtable-5.adoc +++ /dev/null @@ -1,106 +0,0 @@ -= Report on Roundtable V, 09-12 January 2006 -:docnumber: 0613 -:copyright-year: 2006 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2006-01-12 -:published-date: 2006-01-12 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable V took place on January 9-12, 2006, hosted by Novell in Provo, Utah. Monday -January 9th and Tuesday morning the 10th were a dedicated CalConnect Interoperability Event -where seven organizations performed interoperability testing on their calendaring and scheduling -implementations. The Roundtable itself convened midday on Tuesday the 10th and closed midday -on Thursday the 12th. As usual, most of the time was dedicated to technical committee sessions, -with an all-hands Plenary meeting at the end. The Technical Committee sessions were organized -sequentially, to allow all attendees who wished to be involved in the discussions of a Technical -Committee the opportunity to do so. Delegates were also present from The Open Group -Messaging Forum to discuss a possible joint endeavor with respect to a Federated Freebusy -Challenge which the TOG/MF has issued. - -== Update on Technical Committees and Initiatives - -*Work Products*: _The iCalendar Timezone Problems and Recommendations_ document and an -update to the _Min-IOP Use Cases_ document were approved for publication and have been -published on the Consortium web site. The _Timezone Registry/Resource Recommendations_ -document, _Calendaring Glossary_, and _Recurrence Problems and Recommendations_ document, -among others, are in progress; the Recurrence document is intended to be published in time to be -delivered to the CALSIFY Working Group of the IETF in March. - -*TC-AUTHENTICATE* is undertaking a study of authentication schemes used by existing -calendaring and scheduling implementations (many proprietary) in preparation for -recommendations for short-term and longer-term authentication methods for calendaring. The -study will be published when complete. - -*TC-CALDAV* is beginning work on use cases and requirements for CalDAV Scheduling as input -to the development of the scheduling draft for CalDAV. The TC is also considering requirements -for a specialized Freebusy Service component for CalDAV which might address the TOG/MF -requirement mentioned above. - -*TC-EVENTPUB* has conducted a survey on existing event publication systems, and is working -on requirements for expanded location information in iCalendar to support the needs for event -publication. - -*TC-MOBILE* is conducting a survey of calendaring with mobile devices and has begun the -development of a problem statement to define the requirements for open, interoperable -calendaring with mobile devices. The TC hopes to liaise with the OMA in April and invite their -participation in the May Roundtable to assist in developing the requirements for calendaring and -scheduling standards to support mobile devices. - -*TC-REALTIME* is beginning the refinement of use cases associated with "real time" server-toserver -communcation. - -*TC-RECURR* is in the process of refining its Problems and Recommendations document to be -delivered to the IETF Calsify Working Group in time for their March meeting. - -*TC-TIMEZONE* has completed its Problems and Recommendations document for publication -and is working on a Timezone Registry and Service recommendations document. - -*TC-USECASE* has completed its Min-IOP Use Cases document for publication and is working on -the Calendaring Glossary document. - -*CalConnect Interoperability Event*: Participants in the interoperability testing event included -EVDB, Mozilla, Novell, Oracle, OSAF, RPI (Rensselaer Polytechnic Institute) and Trumba. -Results from the event will be posted at Past IOP Reports. - -== Future Meetings - -The next meeting (Roundtable VI) will take place 22-25 May 2006, hosted by IBM/Lotus in -Cambridge, Massachusetts. Based on the successful model for Roundtable V, where the -CalConnect Interoperability Event was conducted the first 1.5 days, followed by the Roundtable, -this model will be continued at Roundtable VI. diff --git a/sources/csd-report-roundtable-6.adoc b/sources/csd-report-roundtable-6.adoc deleted file mode 100644 index da06b5e..0000000 --- a/sources/csd-report-roundtable-6.adoc +++ /dev/null @@ -1,110 +0,0 @@ -= Report on Roundtable VI, 22-25 May 2006 -:docnumber: 0614 -:copyright-year: 2006 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2006-05-23 -:published-date: 2006-05-23 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable VI took place on May 22-25, 2006, hosted by IBM/Lotus in Cambridge, -Massachusetts. Monday May 22nd and Tuesday morning the 23rd were a dedicated CalConnect -Interoperability Event where participating organizations performed interoperability testing on their -calendaring and scheduling implementations. - -Tuesday morning a pair of Practicums on iCalendar standards and on CalDAV were offered. The -Roundtable itself convened midday on Tuesday the 23rd and closed midday on Thursday the 25th. - -Tuesday afternoon was dedicated to a Mobile Calendaring Workshop, sponsored by TC-MOBILE -(and replacing TC MOBILE's regular working session). - -Wednesday, and part of Thursday morning, were dedicated to the other technical committee -sessions, with an all-hands Plenary meeting at the end. The Technical Committee sessions were -organized sequentially, to allow all attendees who wished to be involved in the discussions of a -Technical Committee the opportunity to do so. - -== Update on Technical Committees and Initiatives - -*Work Products*: Since Roundtable V, _Recurrence Problems and Recommendations_ document and -the _Timezone Registry and Service Recommendations_ have been published. The _Calendaring -Glossary_ should proceed to last call shortly, as should the _Mobile Calendaring Questionnaire -Results_ Document. - -*TC-AUTHENTICATE* is monitoring discussion on the issues of http authentication leading up to -the IETF meeting in July. - -*TC-CALDAV* is working on requirements for CalDAV Scheduling as input to the development of -the scheduling draft for CalDAV. - -*TC-EVENTPUB* has developed a proposal for a VVENUE extension to iCalendar to support -event publication with expanded information, and plans to submit it as an individual draft to the -IETF. - -*TC-FREEBUSY* was formed at this Roundtable to coordinate CalConnect efforts associated with -The Open Group Federated Free/Busy Challenge, leading to a proof of concept demonstration in -Mid-July. - -*TC-MOBILE* conducted its Mobile Calendaring Workshop at this Roundtable and will publish -the results of its mobile calendaring questionnaire shortly. The TC is beginning work on a white -paper delineating the reasons for (especially) mobile device and software manufacturers and -operators to migrate to iCalendar from vCalendar. - -*TC-REALTIME* is actively working on the issues associated with server to server -communication. - -*TC-RECURR* was disbanded, having completed its charter. - -*TC-TIMEZONE* was disbanded, having completed its charter. - -*TC-USECASE* has completed work on the Calendaring Glossary document, which will go to Last -Call in the Consortium shortly, and has begun work on the minimum interoperable subset for tasks -(vtodos). - -*CalATOM Ad Hoc Group*: A discussion mailing list on CalATOM and associated issues such as -RSS was formed at this Roundtable. The discussion list is open to interested individuals whether -or not they represent CalConnect members. - -*CalConnect Interoperability Event*: Participants in the interoperability testing event included -EVDB, Oracle, OSAF and RPI (Rensselaer Polytechnic Institute). Results from the event will be -posted at Past IOP Reports. - -== Future Meetings - -The next meeting (Roundtable VII) will take place 26-29 September 2006 in the San Francisco -Bay Area. The following meeting (Roundtable VIII) will take place in mid-January, probably on -the East Coast. diff --git a/sources/csd-report-roundtable-7.adoc b/sources/csd-report-roundtable-7.adoc deleted file mode 100644 index 545fa95..0000000 --- a/sources/csd-report-roundtable-7.adoc +++ /dev/null @@ -1,127 +0,0 @@ -= Report on Roundtable VII, 26-29 September 2006 -:docnumber: 0615 -:copyright-year: 2006 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2006-09-29 -:published-date: 2006-09-29 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable VII took place on September 26-29, 2006, hosted by Apple Computer in Cupertino, -California. The event was attended by sixty representatives to the IOP testing and/or the -Roundtable, including representatives from nine observers (organizations attending a Roundtable -to see if they wish to join). - -Tuesday September 26th and Wednesday morning the 27th were a dedicated CalConnect -Interoperability Test Event where participating organizations performed interoperability testing on -their calendaring and scheduling implementations. Wednesday morning a reprise of the Federated -Free/Busy demo originally done at The Open Group meeting in Miami in July, 2006 was arranged. -Wednesday afternoon, all day Thursday, and Friday morning comprised the Roundtable. The -majority of this time was dedicated to technical committee sessions, with an all-hands Plenary -meeting as the last item on Friday morning. The Technical Committee sessions were organized -sequentially, to allow all attendees who wished to be involved in the discussions of a Technical -Committee the opportunity to do so. - -== Update on Technical Committees and Initiatives - -*Work Products*: Since Roundtable VI, the _Mobile Calendaring Questionnaire Results_ Document -has been published. The _Calendaring and Scheduling Glossary of Terms_ will be published shortly -after Roundtable VII, as will the _CalDAV Scheduling Use Cases and Requirements_ document. - -*TC-AUTHENTICATE* has been shutdown. Currently work is ongoing in the IETF to specify -new HTTP authentication protocols that can be utilized by CalDAV as well as other HTTP -applications. As a result the Consortium's technical committee chairs felt that TC-AUTHENTICATE -was unnecessary right now, as there was no specific input from the Consortium -that was needed. - -*TC-CALDAV* continues to work on requirements for CalDAV Scheduling as input to the -development of the scheduling draft for CalDAV, and will be focusing after this Roundtable on the -areas of availability, scheduled event updates, and external attachments. - -*TC-EVENTPUB* has developed use cases and requirements for the VVENUE iCalendar -extension, which will be submitted to the IETF shortly after Roundtable VII as an individual -submission by its authors, and will focus on event sharing and event server synchronization after -this Roundtable. - -*TC-FREEBUSY* conducted the proof of concept Federated Free/Busy Demo in July and reprised -it with additional participants, and will look at ways to extend the Freebusy aggregator and -enhance the Free/Busy tool as a basis for further development. - -*TC-IOPTEST* conducted the IOP test event and is starting to consider the development of mobile -calendaring tests in conjunction with TC MOBILE. - -*TC-MOBILE* discussed three major areas _The Benefits of iCalendar for the mobile industry_, a -white paper under development; recurrence simplification for mobile devices as input to the IETF -CALSIFY effort; and the development of a mobile calendaring IOP test suite and IOP test events -for mobile devices; work on all of these will proceed after the Roundtable. The session was -attended by a delegation of ten people from the OMA Data Sync working group, with which -CalConnect has a liaison. - -*TC-REALTIME* is focusing on three major discussion areas: addressing, discovery, and -authentication/authorization/access control, and will continue work in those areas after the -Roundtable. - -*TC-USECASE* has completed the Calendaring Glossary document which will be published -shortly after the Roundtable, has begun work on the minimum interoperable subset for tasks -(vtodos), and will undertake a study of recurrence features in mobile device support for TC -MOBILE. - -*vCard Ad Hoc Group*: One of the OMA/DS delegates presented a paper on vCard and on contact -information in genera as part of a discussion on whether or not the Consortium should undertake -any action in this area. - -*CalConnect Interoperability Test Event*: Participants in the IOP test event included Apple -Computer, Eventful (formerly EVDB), Mozilla, OSAF and RPI (Rensselaer Polytechnic Institute). -Results from the event will be posted at Past IOP Reports shortly. - -*NEW INITIATIVES*: The Consortium is studying the possibility of undertaking work in several -new areas, in particular vCard/contact information, resources, and a general assessment of -Calendaring tools and specifications such as CalDAV/RSS-SSE/microformats and so forth. -Possible work will be undertaken depending on whether or not the Consortium has resources -interested in the work, and the development of charters and proposed work products appropriate -for the Consortium. - -== Future Meetings - -The next meeting (Roundtable VIII) will take place January 29 through February 2 in Provo, Utah, -hosted by Novell. Due to the increasing size of the IOP test event, the format of the January -meeting will be changed to span the week. The IOP test event will run from noon Monday (Jan -29) through noon Wednesday (Jan 31). The Roundtable will run from noon Wednesday (Jan 31) -through noon Friday (Feb 2). - -Roundtable IX will take place the week of May 7-11, location TBD. diff --git a/sources/csd-report-roundtable-8.adoc b/sources/csd-report-roundtable-8.adoc deleted file mode 100644 index 00b5acf..0000000 --- a/sources/csd-report-roundtable-8.adoc +++ /dev/null @@ -1,169 +0,0 @@ -= Report on Roundtable VIII, 29 January - 2 February 2007 -:docnumber: 0711 -:copyright-year: 2006 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2007-02-02 -:published-date: 2007-02-02 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable VIII took place January 29 to February 2, 2007, hosted by Novell in Provo, Utah. The -event was attended by 30 representatives to the IOP testing and/or the Roundtable, including -representatives from two observers (organizations attending a Roundtable to see if they wish to -join). - -Monday noon through Wednesday noon, January 29-31, was a dedicated CalConnect -Interoperability Test Event where participating organizations performed interoperability testing -between their calendaring and scheduling implementations. Wednesday afternoon, all day -Thursday, and Friday morning comprised the Roundtable. The majority of this time was dedicated -to technical committee sessions, BOFs, and informal discussions and networking, with an allhands -Plenary meeting as the last item on Friday morning. The Technical Committee sessions -were organized sequentially, to allow all attendees who wished to be involved in the discussions of -a Technical Committee the opportunity to do so. - -== Update on Technical Committees and Initiatives - -=== Work Products - -Since Roundtable VII, TC USECASE has published the _Calendaring and -Scheduling Glossary of Terms_ and TC MOBILE has published _The Benefits of iCalendar for the -Mobile Industry_. - -=== TC CALDAV - -TC CALDAV and TC FREEBUSY jointly worked on the availability discussions -which contributed to the VAVAILABILITY specification recently submitted to the IETF by its -authors. The TC is in the final stages of work on the _CalDAV Scheduling Requirements_ paper -which should be published in February. Following completion of the paper, the TC plans work on -several topics including client metadata, external attachments, scheduled event updates, -synchronization support and polling improvements. TC CALDAV intends to complete its work by -Roundtable IX in May 2007, after which the TC will be shut down and TC REALTIME -reactivated. - -=== TC EVENTPUB - -TC EVENTPUB developed use cases and requirements for the VVENUE -iCalendar extension, which has been submitted to the IETF as an individual submission by its -authors. The TC is about to begin work on two new initiatives, event sharing and a possible event -sharing protocol for event servers, and localization and a possible VLOCALIZE iCalendar -extension. - -=== TC FREEBUSY - -The TC has completed its original scope of work with the completion of the -report to The Open Group. Following the Roundtable it will begin work on FREEBUSY URLs -and is exploring another initiative. - -=== TC IOPTEST - -TC IOPTEST conducted the IOP test event and is continuing to work with TC -MOBILE on the development of a Mobile Interoperability Test Suite and planning for a Mobile -Interoperability Test Event. The TC is planning to initiate monthly Jabber-based remote IOP test -events as an adjunct to the formal IOP test events conducted with the Roundtables. - -=== TC MOBILE - -The TC has completed and published _The Benefits of iCalendar for the Mobile -Industry_ and is working on the development of a Mobile Interoperability Test Suite in conjunction -with TC IOPTEST. Planning has begun for a Mobile Interoperability Test Event targeted to the -mobile device industry. Timing and location are not yet determined but late 3rd or 4th quarter in -Europe or the U.K. seem most likely at this time. The TC is also working on recurrence -simplification for mobile devices as input to the IETF CALSIFY effort. - -=== TC REALTIME - -The TC will be reactivated following the completion of the work in TC -CALDAV, which will free up some necessary resources; the Consortium's intent is to reactivate at -the May 2007 Roundtable. The TC anticipates focusing on three major discussion areas: -addressing, discovery, and authentication/authorization/access control, all of which are needed to -enable general server-server freebusy lookup and event scheduling. - -=== TC USECASE - -The TC has published the Calendaring and Scheduling Glossary of Terms and has -begun work on a paper defining usecases for the minimum interoperable subset for tasks (vtodos). -The TC has also undertaken a study of recurrence features in mobile device support for TC -MOBILE, and is considering a work item on usecases for resource management. - -=== Daylight Saving Time Ad Hoc - -The DST Ad Hoc Group has developed and published on the -Consortium Website two documents having to do with the imminent DST change: _Extended -Daylight Saving Time Review and Considerations_ and _Extended Daylight Saving Time Links_, -_Advisories and Changes_. In early summer the group plans to develop and publish a "Lessons -Learned" from user experiences during March as a reference and guide to the change back to -standard time in November. - -=== vCard Ad Hoc Group - -There is still interest initiating work in the contacts/vCard area but it waits -on the availability of resources from existing or new members. - -=== CalConnect Interoperability Test Event - -Participants in the IOP test event -included Apple, Eventful, Kerio, Marware, Novell, Oracle, OSAF, and Bedework (Rensselaer -Polytechnic Institute). Results from the event will be posted at Past IOP Reports shortly. - -=== BOFS - -For the first time, the Roundtable was able to provide time for BOFS, and three were held, -on localization, the freebusy url, and DST conversions. The Consortium plans to continue to -provide schedule time for BOFS in the future, together with informal networking amongst those -not interested in the BOFS. - -=== New Initiatives - -Work will be undertaken in existing TCS on new initiatives including -localization, the FREEBUSY URL proposal, event sharing, and other possible items which could -result in the establishment of new TCs once the subjects have been fleshed out and the work -scoped. - -== Future Meetings - -* ROUNDTABLE IX: May 7-11, Seattle, Washington, hosted by Boeing Aircraft Company. -* ROUNDTABLE X: September 17-21, Cambridge, Massachusetts, hosted by M.I.T. (location and -host tentative). -* ROUNDTABLE XI: February 4-8, 2008, location and host TBD -* ROUNDTABLE XII: June 2-6, 2008, Madison, Wisconsin, hosted by the University of -Wisconsin (date, location and host tentative). - -The format of CalConnect week will remain the same for these events: - -* Monday noon through Wednesday noon, IOP Test Event -* Wednesday noon through Friday noon, Roundtable (TC sessions, BOFs, networking, Plenary). diff --git a/sources/csd-report-roundtable-9.adoc b/sources/csd-report-roundtable-9.adoc deleted file mode 100644 index 26171d8..0000000 --- a/sources/csd-report-roundtable-9.adoc +++ /dev/null @@ -1,146 +0,0 @@ -= Report on Roundtable IX, May 7-11 2007 -:docnumber: 0712 -:copyright-year: 2007 -:language: en -:doctype: administrative -:edition: 1 -:status: published -:revdate: 2007-05-11 -:published-date: 2007-05-11 -:technical-committee: CHAIRS -:mn-document-class: cc -:mn-output-extensions: xml,html,pdf,rxl -:local-cache-only: -:data-uri-image: - -.Foreword -The Calendaring and Scheduling Consortium ("`CalConnect`") is a global non-profit -organization with the aim to facilitate interoperability of technologies across -user-centric systems and applications. - -CalConnect works closely with liaison partners including international -organizations such as ISO, OASIS and M3AAWG. - -The procedures used to develop this document and those intended for its further -maintenance are described in the CalConnect Directives. - -In particular the different approval criteria needed for the different types of -ISO documents should be noted. This document was drafted in accordance with the -editorial rules of the CalConnect Directives. - -Attention is drawn to the possibility that some of the elements of this -document may be the subject of patent rights. CalConnect shall not be held responsible -for identifying any or all such patent rights. Details of any patent rights -identified during the development of the document will be in the Introduction -and/or on the CalConnect list of patent declarations received (see -www.calconnect.com/patents). - -Any trade name used in this document is information given for the convenience -of users and does not constitute an endorsement. - -This document was prepared by Technical Committee _{technical-committee}_. - -== Introduction - -Roundtable IX and the accompanying IOP test event took place May 7-11, 2007, hosted by Boeing -in Seattle, Washington. The event was attended by 43 representatives from 31 organizations, -including representatives from three observers (organizations attending a Roundtable to see if they -wish to join). - -Monday noon through Wednesday noon, May 7-9, was a dedicated CalConnect Interoperability -Test Event where 6 participating organizations performed interoperability testing between their -calendaring and scheduling implementations. Wednesday afternoon, all day Thursday, and Friday -morning comprised the Roundtable. The majority of this time was dedicated to technical -committee sessions, BOFs, and informal discussions and networking, with an all-hands Plenary -meeting as the last item on Friday morning. The Technical Committee sessions were organized -sequentially, to allow all attendees who wished to be involved in the discussions of a Technical -Committee the opportunity to do so. - -== Update on Technical Committees and Initiatives - -=== Work Products - -Since Roundtable VIII, TC USECASE has published the Minimum -Interoperable Subset Use Cases for Tasks (VTODO), and the DST Ad Hoc committee regularly -updated the Extended Daylight Savings Time Information pages to provide information on the -early shift to Daylight Savings Time. The Consortium also implemented a public Calendar -Administrators Discussion List, and a new website. - -=== TC CALDAV - -The TC is in the final stages of work on the _CalDAV Scheduling Requirements_ -paper which should be published in June. The TC also has several extensions which have been -proposed for investigation, but expects to complete its work by Roundtable X in September. - -=== TC EVENTPUB - -TC EVENTPUB reviewed VVENUE and discussions on localization, and the -current status of work on the "eventmap" event sharing proposal. - -=== TC FREEBUSY - -TC FREEBUSY reviewed previous work including the status of the Boeing -Federated Free/Busy project, and has begun work on the FREEBUSY URL proposal. - -=== TC IOPTEST - -TC IOPTEST initiated monthly Jabber IOP test events as an adjunct to the full -IOP test events held with Roundtables. The TC reported on the IOP test event just completed, and -is continuing to work with TC MOBILE on the development of a Mobile Interoperability Test -Suite and planning for a Mobile Interoperability Test Event. - -=== TC MOBILE - -TC MOBILE reviewed the current draft of its Mobile Interoperability Test Suite, -and continues to develop it. The TC plans a Mobile Interoperability Test Event targeted to the -mobile industry in 4Q07 or 1Q08, probably in the U.K. or Europe. The TC is also working on -recurrence simplification for mobile devices as input to the IETF CALSIFY effort. - -=== TC REALTIME - -The TC will be reactivated in June and expects to begin work with the -consideration of Anonymous Free/Busy, in conjunction with TC FREEBUSY. - -=== TC USECASE - -The TC has published the Min-IOP (Minimum Interoperable Subset) Use Cases -for Tasks (VTODO) and has begun work on considering Use Cases for Resources. The TC has -also undertaken a study of recurrence features in mobile device support for TC MOBILE. - -=== Daylight Saving Time Ad Hoc - -The DST Ad Hoc reported on its work leading up th the DST -conversion in March, and plans to prepare a "lessons learned" document. The document will cover -preparations, lessons learned, planning for November, and longer-term recommendations. - -=== CalConnect Interoperability Test Event - -Participants in the IOP test event -included Apple, Marware, OSAF, Bedework (Rensselaer Polytechnic Institute) Sun Microsystems -(Lightning), and Synchronica. Results from the event will be posted at Past IOP Reports as soon -as they are collated and prepared. - -=== BOFS - -BOF topics included SSE (Simple Sharing Extensions), XML for iCalendar representation, -vCard initiatives, and the DST follow-on work. - -=== New Initiatives - -The Consortium plans to initiate work on a follow-on activity to TC -TIMEZONE in the area of a timezone registry and service protocol; XML for iCalendar -representation; and a possible vCard/Content Workshop in September to help define the problems -and potential solutions. - -== Future Meetings - -* ROUNDTABLE X: September 17-21, Cambridge, Massachusetts, hosted by M.I.T. (location and -host tentative). -* ROUNDTABLE XI: February 4-8, 2008, location and host TBD -* ROUNDTABLE XII: June 2-6, 2008, Madison, Wisconsin, hosted by the University of -Wisconsin (date, location and host tentative). - -The format of CalConnect week will remain the same for these events: - -* Monday noon through Wednesday noon, IOP Test Event -* Wednesday noon through Friday noon, Roundtable (TC sessions, BOFs, networking, Plenary).