<?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 I, 23-24 September 2004</title>
<docidentifier primary="true" type="CalConnect">CC/A 0404:2004</docidentifier><docnumber>0404</docnumber><date type="published"><on>2004-09-24</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>2004-09-24</revision-date></version><language>en</language><script>Latn</script><status><stage>published</stage></status><copyright><from>2004</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="_dbf4cf52-dae2-3cee-ac4f-60fbeb7e154e" obligation="normative"><p id="_f1e04aa6-f789-42c5-5d0f-de370d1570d6">© 2004 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></preface><sections>
<clause id="_8b3c23f3-ddd2-18e3-5ef5-6341a7aa74a8" obligation="normative">
<title id="_dee6e8d4-127b-5284-e6ea-6f4e1928714b">Report</title>
<p id="_0c6c4bbc-4c46-18db-2a2c-034794d732af">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.</p>

<p id="_82e46beb-4cf1-c085-aff3-cd4d6075e274">Twenty-three individuals from fourteen organizations attended the Roundtable. The discussion was oriented towards three general areas:</p>

<ul id="_51640761-d606-1c02-17a4-6d3ac9e9e16d"><li><p id="_7addd2f8-f084-0b3d-e190-a7e128f5ad73">Do we agree on a problem statement?</p>
</li>
<li><p id="_21928e26-967c-7613-4164-ab12081ba4fe">Are we willing to work together to address the problem(s)?</p>
</li>
<li><p id="_e5046293-7733-82a7-b260-0f9f838530da">How do we want to go about undertaking this work?</p>
</li>
</ul>

<p id="_2d100a0a-5299-5dbe-b699-0fdb2295e553">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:</p>

<quote id="_3ec0fa3b-f73b-5371-d89a-5c3fd91892d6"><p id="_d9951949-cd68-5a2b-3b7b-aba8b693bab9">“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.</p>
</quote>

<p id="_bee9f0ab-47b3-0ec4-3f8b-794da0914cbd">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.</p>

<p id="_eab29e37-e320-3a40-5748-b954a6eb0ef8">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.</p>

<p id="_49f73e20-a764-e67d-af33-dbe085c94f94">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.</p>
</clause>
</sections>
</metanorma>
