<?xml version="1.0" encoding="UTF-8"?>
<metanorma xmlns="https://www.metanorma.org/ns/standoc" type="semantic" version="2.8.5" schema-version="v2.1.5" flavor="cc">
<bibdata type="standard">
<title language="en" type="main">Report on Roundtable III, 1-3 June 2005</title>
<docidentifier primary="true" type="CalConnect">CC/A 0512:2005</docidentifier><docnumber>0512</docnumber><date type="published"><on>2005-06-03</on></date><contributor><role type="author"/><organization>
<name>CalConnect</name>
</organization></contributor><contributor><role type="author"><description>committee</description></role><organization>
<name>CalConnect</name>
<subdivision type="Technical committee">
<name>CALCONNECT</name>
</subdivision></organization></contributor><contributor><role type="publisher"/><organization>
<name>CalConnect</name>
</organization></contributor><edition>1</edition><version><revision-date>2005-06-03</revision-date></version><language>en</language><script>Latn</script><status><stage>published</stage></status><copyright><from>2005</from><owner><organization>
<name>CalConnect</name>
</organization></owner></copyright><ext><doctype abbreviation="A">administrative</doctype><flavor>cc</flavor></ext></bibdata><metanorma-extension><semantic-metadata><stage-published>true</stage-published></semantic-metadata>
<presentation-metadata><toc-heading-levels>2</toc-heading-levels><html-toc-heading-levels>2</html-toc-heading-levels><doc-toc-heading-levels>2</doc-toc-heading-levels><pdf-toc-heading-levels>2</pdf-toc-heading-levels></presentation-metadata></metanorma-extension>
<boilerplate><copyright-statement>

<clause id="_48485c3c-cb59-de1c-dae7-1b0db46ad857" obligation="normative"><p id="_7ad3e32c-019d-9fa6-4579-92ec203686f0">© 2005 The Calendaring and Scheduling Consortium, Inc.</p>
</clause>
</copyright-statement>

<legal-statement>

<clause id="_30bb02f9-a03f-937c-b3bb-0058ec7c185d" obligation="normative"><p id="_4997ac1f-fe23-c399-660a-4ca594a6abda">All rights reserved. Unless otherwise specified, no part of this         publication may be reproduced or utilized otherwise in any form or by any         means, electronic or mechanical, including photocopying, or posting on the         internet or an intranet, without prior written permission. Permission can         be requested from the address below.</p>
</clause>
</legal-statement>

<feedback-statement>

<clause id="_525641bf-9235-cdcb-5b80-9232a01ea9cc" obligation="normative"><p id="_9c7e0878-01cd-c6a2-8060-5caf3135b547" anchor="boilerplate-name">The Calendaring and Scheduling Consortium, Inc.</p>

<p id="_851786db-d5f1-a086-bdb1-3bd48dc4f17c" anchor="boilerplate-address">4390 Chaffin Lane<br/> McKinleyville<br/> California 95519<br/> United States of America<br/> <br/> <link target="mailto:copyright@calconnect.org"/><br/> <link target="https://www.calconnect.org">www.calconnect.org</link></p>
</clause>
</feedback-statement>
</boilerplate><preface><foreword id="_19c357dd-d570-e2fd-6bb5-2e5752b03f8d" obligation="informative">
<title id="_41c9fad3-d4c1-eecc-4fad-f91704acc026">Foreword</title>
<p id="_978efc4a-4424-2bdd-9f8a-1e4be31eb9a9">The Calendaring and Scheduling Consortium (“<tt>CalConnect</tt>”) is a global non-profit organization with the aim to facilitate interoperability of technologies across user-centric systems and applications.</p>

<p id="_69d40857-4c40-88c8-469b-e0c9a8d8d874">CalConnect works closely with liaison partners including international organizations such as ISO, OASIS and M3AAWG.</p>

<p id="_e821e1fe-2cf4-934e-4567-582480580b1d">The procedures used to develop this document and those intended for its further maintenance are described in the CalConnect Directives.</p>

<p id="_cd9018d9-8c79-6bb5-c345-1aaa6f04fe15">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.</p>

<p id="_080f073a-4f79-f108-5f75-ca6659f38fd4">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).</p>

<p id="_882b2a20-4eba-ae6e-3dc1-2ffc96683fc9">Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.</p>

<p id="_706ffe8c-2f4c-ed7e-e04b-f2a2dc1a33c0">This document was prepared by Technical Committee <em>CALCONNECT</em>.</p>
</foreword><introduction id="_f93cba71-d7a1-ed1c-f7be-ab57d5a9228f" obligation="informative">
<title id="_2b2e98d1-114a-3da4-8556-01ae0a724280">Introduction</title>
<p id="_f84340e8-f8df-6c8c-095f-98a91ca539d7">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.</p>
</introduction></preface><sections>

<clause id="_8c182aff-0641-7247-11ae-4453013e737a" obligation="normative">
<title id="_68006943-14a7-cbb0-3190-80c33718c9c8">Update on Initiatives</title>
<p id="_aca6af2b-d996-6c75-46f9-3b7819e99ef7"><strong>Glossary Project</strong>: 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.</p>

<p id="_7b4086f3-f4f1-2f3f-d386-98679a5412b6"><strong>Recurrence Questionnaire</strong>: 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.</p>

<p id="_38b37654-5a74-4ac5-e472-f0a2e459e642"><strong>TC-REALTIME</strong> has been on hold pending the completion of other work, and will begin its work in mid to late June.</p>

<p id="_5c4f87a5-5214-0a5c-453d-685e62ae2a37"><strong>TC-MIN-IOP</strong> was disbanded and folded into TC-IOPTEST.</p>

<p id="_813b1b5c-c4e3-ceec-ae26-bebe6e6881c9"><strong>External Communications</strong>: The Consortium will be announcing an RSS feed for Calendaring issues and announcements in the next several weeks.</p>

<p id="_17781816-a86c-8157-89bd-ac4ba696f432"><strong>New initiatives</strong>: 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:</p>

<ul id="_6c4b216c-c72d-dcf2-c62e-2dfff15c2c14"><li><p id="_b9e5339d-1745-e852-f40c-9d5612bd4f77">Calendar user address discovery and calendar server discovery</p>
</li>
<li><p id="_f2f149d2-cd57-1542-77bd-f56ad0ddd42e">Cross domain security and access control</p>
</li>
<li><p id="_a4b88fe2-137a-95f2-1518-7ffb48efdc28">Todos for project management</p>
</li>
</ul>
</clause>

<clause id="_951d7ede-2efe-d67f-28f9-cafd05da6fcb" obligation="normative">
<title id="_2a48cb21-7cb9-89b0-876f-36c8b2e43ebe">CalConnect Interoperability Event</title>
<p id="_1c4e6ac7-d9be-1f16-3703-0a0b6626add5">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.</p>
</clause>

<clause id="_232cf42d-8828-b6ae-1a8f-873dc2f93bf1" obligation="normative">
<title id="_c20e8917-0a34-ec90-a2d6-83801e1f5b11">Technical Committees</title>
<p id="_256a8177-3bf9-4260-c911-de84f527397d">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:</p>

<p id="_43da4ed4-bfe3-e611-1ad4-55aa48adeef8">TC-CALDAV has made its CalDAV test script available on the Consortium website (under “Resources”).</p>

<p id="_c0a6a43f-4152-7949-ecc0-0caeda390728">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.</p>

<p id="_e8ea3092-ceaa-3a79-bec3-6c09dba73e0b">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.</p>

<p id="_d74bd97c-7c86-63ac-e857-ae2955c6eaef">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.</p>

<p id="_4c90897b-61f0-0002-b2d8-3821f39147fe">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.</p>

<p id="_49896e08-27ed-ea2d-5f25-c3ef1b0b3764">TC-TIMEZONE is conducting a questionnaire on Timezone implementations as part</p>
</clause>

<clause id="_866bd372-dff8-c735-f1f8-583a9b60f507" obligation="normative">
<title id="_bcb61276-2cbc-7311-0126-0460d4dc9129">Future Meetings</title>
<p id="_0835402f-ee63-455f-e5ff-d93058f2fb2f">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.</p>
</clause>
</sections>
</metanorma>
