Caro Golf 4
164 A Barbu Vacarescu Blvd
2nd Distrrict
020285 Bucharest
Romania
http://carohotel.ro/bucharest-hotels/4-star-hotel-bucharest/

Monday 18 May
0800-0830 Coffee Service
0830-1000 Testing
1000-1030 Break and Refreshments
1030-1230 Testing
1230-1330 Lunch
1330-1430 Breakout: API discussions
1330-1530 Testing
1430-1530 Testing
1530-1600 Break and Refreshments
1600-1800 Testing

1900-2100 Interop Test Dinner
Trattoria Il Calcio
Strada Glodeni 1-3, Bucureşti 023824, Romania
(within the Pescariu Sports & SPA)

Tuesday 19 May
0800-0830 Coffee Service
0830-1000 Testing
1000-1030 Break and Refreshments
1030-1130 Breakout: iMIP
1030-1230 Testing
1230-1330 Lunch
1330-1430 Breakout: DAV PUSH
1330-1530 Testing
1330-1530 Testing
1530-1600 Break and Refreshments
1600-1800 Testing

Wednesday 20 May
0800-0830 Coffee Service
0830-1000 Testing
1000-1030 Break and Refreshments
1030-1200 Testing
1200-1230 Wrap-up
1230 End of IOP Testing

1230-1330 Lunch/Opening¹

Technical Committee Summaries and IETF Status
A summary of what each Technical Committee (TC) has worked on and the interoperability testing that has taken place. Will also cover new and changed draft specifications, and a description of new "stable" specifications that implementors should begin working on (e.g RSCALE, relationships, etc.)

Embedding Calendar Data in Media (QRCODE, Data URI)
Using QRcode and data URIs to make calendar data available without networking

Investigating Scheduling in Government
Discussion of common issues that affect governmental services, for example health care, appointments with officials; development of use cases, guide to what they could do with calendaring

Changes to the scheduling model
The current - enterprise meeting oriented - scheduling model does not address all current needs, e.g. multiple organizers or no organizer are common models not supported.

Shared calendars and address books
Issues such as scheduling in shared calendars, address book sharing models (sharing of groups, individual contacts, etc) will be discussed.

Consensus Scheduling and Office Hours applications (i.e. reverse scheduling)
The use of VPOLL and VAVAILABILITY

Identity crisis revisited
Using email addresses from outside your domain as identifiers leads to problems. Many services did so and some are now backing out. How does this affect protocols and services such as iSchedule?

TC API data model
The first step in producing the new API is to define a concrete data model and Rest/URI mapping actions on that. We will discuss the options available.

Calendaring systems in general (solar, luni-solar, etc.)
Discussion of non-Gregorian calendaring systems (from a historical aspect) as well as how the new RSCALE iCalendar spec can be used.

RSCALE
Implementing recurrences in different calendar scales

Technical Committee work in a global organization
We now have members/member reps in ten time zones and soon more. What means of working can we develop to allow participation from individuals around the world in the work of our TCs? What are best practices and good approaches?

Conference Dinner⁴
Caru' cu bere
Strada Stavropoleos, Bucureşti, Romania

Aligning the task model with project and building management
Adding new properties to describe relationships and status

iCalendar 3
Is it time to consider a major overhaul of the representation and data model or can we continue to add new features to the current model.

Security model/technologies for iSchedule and Federated Sharing
Sending sharing invitations and other data requires some degree of security. Some models allow features, such as end to end privacy.

Sending invitations through something other than e-mail
Email is often not the primary vehicle for messaging among people. Instant messaging and other services should be considered as a way to deliver invitations and notifications. New mime types are one possible solution.

CalDAV Topics
Progress on the server information specification
Server and client capability matrix

DEVGUIDE progress
Discuss the progress of the work in the new TC. Solicit additional topics that should be included in the Devguide.

CalConnect Plenary Meeting
Administrative business, coming events, consensus agreements on decisions reached during the week, open floor.