2.1.  Published documents

2.2.  New Internet Drafts Submitted to IETF

2.3.  Updated Internet Drafts and Published RFCs

3.1.  CALSCALE-ADHOC

Presented a problem statement and our proposed approach. The draft is now at the IETF: Non-Gregorian Recurrence Rules in iCalendar. There was a discussion on RPATTERN vs RRULE, “L” suffix vs BYLEAPMONTH. The outcomes were:

3.2.  TC AUTODISCOVERY

The draft has been updated to use JSON 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.

3.3.  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.

3.4.  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.

3.5.  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.

3.6.  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.

3.7.  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.

3.8.  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.

3.9.  TC TASKS

Good progress since last roundtable in areas of:

After the roundtable report the key discussion points were on:

Next steps will focus on consolidating what we have so far in to drafts and developing the other areas in scope for the TC:

3.10.  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.

3.11.  TC USECASE

Presented recommendations to attending members for actions CalConnect can take regarding CalConnect visibility and membership activity:

Voice votes taken during the TC-WrapUp session were supportive for all four recommendations.

3.12.  TC XML

We had a short session in which we brought people up to date:

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.