From douglm@rpi.edu Tue May 17 07:49:46 2011 Return-Path: X-Original-To: caldav@ietfa.amsl.com Delivered-To: caldav@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 217BBE0665 for ; Tue, 17 May 2011 07:49:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qiPOB5DZl+ku for ; Tue, 17 May 2011 07:49:45 -0700 (PDT) Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by ietfa.amsl.com (Postfix) with ESMTP id 86026E0658 for ; Tue, 17 May 2011 07:49:45 -0700 (PDT) Received: from [128.113.124.225] (blue-eyes-white-dragon-17.dynamic2.rpi.edu [128.113.124.225]) (authenticated bits=0) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id p4HEnhCH005683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 May 2011 10:49:43 -0400 Message-ID: <4DD28B07.2060303@rpi.edu> Date: Tue, 17 May 2011 10:49:43 -0400 From: Mike Douglass User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: CalDAV Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Bayes-Prob: 0.0001 (Score 0) X-RPI-SA-Score: 1.40 (*) [Hold at 12.00] RATWARE_GECKO_BUILD,22490(-25) X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228 Subject: [caldav] Availability draft 02 X-BeenThere: caldav@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2011 14:49:46 -0000 The spec says: availableprop = *( ; ; the following are REQUIRED, ; but MUST NOT occur more than once ; dtstamp / dtstart / uid / But the example has no DTSTAMP for available BEGIN:AVAILABLE UID:20111005T133225Z-00001-A@example.com SUMMARY:Monday to Thursday from 9:00 to 17:00 DTSTART;TZID=America/Montreal:20111002T090000 DTEND;TZID=America/Montreal:20111002T170000 RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH END:AVAILABLE I'd be inclined to question the need for UID or DTSTAMP in available as the component cannot stand alone -- Mike Douglass douglm@rpi.edu Senior Systems Programmer Communication& Collaboration Technologies 518 276 6780(voice) 2809 (fax) Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180 From andrew@morphoss.com Wed May 18 18:33:51 2011 Return-Path: X-Original-To: caldav@ietfa.amsl.com Delivered-To: caldav@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B839E0674 for ; Wed, 18 May 2011 18:33:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.046 X-Spam-Level: X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zFTjYzR7JvO4 for ; Wed, 18 May 2011 18:33:50 -0700 (PDT) Received: from mail.morphoss.com (hoppy.mcmillan.net.nz [202.78.240.82]) by ietfa.amsl.com (Postfix) with ESMTP id C8248E06E3 for ; Wed, 18 May 2011 18:33:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.morphoss.com (Postfix) with ESMTP id 1398A20325; Thu, 19 May 2011 13:33:44 +1200 (NZST) X-Virus-Scanned: Debian amavisd-new at mail.morphoss.com Received: from mail.morphoss.com ([127.0.0.1]) by localhost (hoppy.mcmillan.net.nz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rp0Dfoufb9Iw; Thu, 19 May 2011 13:33:39 +1200 (NZST) Received: from [192.168.55.25] (home.mcmillan.net.nz [202.160.48.75]) (Authenticated sender: andrew@mail.morphoss.com) by mail.morphoss.com (Postfix) with ESMTPSA id 4013F20320; Thu, 19 May 2011 13:33:39 +1200 (NZST) From: Andrew McMillan To: Mike Douglass In-Reply-To: <4DD28B07.2060303@rpi.edu> References: <4DD28B07.2060303@rpi.edu> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-0IvgZlYnuq5WDXY2vcJl" Organization: Morphoss Ltd Date: Thu, 19 May 2011 13:33:38 +1200 Message-ID: <1305768818.6709.394.camel@dave.home.mcmillan.net.nz> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Cc: CalDAV Subject: Re: [caldav] Availability draft 02 X-BeenThere: caldav@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: andrew@morphoss.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2011 01:33:51 -0000 --=-0IvgZlYnuq5WDXY2vcJl Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2011-05-17 at 10:49 -0400, Mike Douglass wrote: > The spec says: >=20 > availableprop =3D *( > ; > ; the following are REQUIRED, > ; but MUST NOT occur more than once > ; > dtstamp / dtstart / uid / >=20 > But the example has no DTSTAMP for available >=20 > BEGIN:AVAILABLE > UID:20111005T133225Z-00001-A@example.com > SUMMARY:Monday to Thursday from 9:00 to 17:00 > DTSTART;TZID=3DAmerica/Montreal:20111002T090000 > DTEND;TZID=3DAmerica/Montreal:20111002T170000 > RRULE:FREQ=3DWEEKLY;BYDAY=3DMO,TU,WE,TH > END:AVAILABLE >=20 > I'd be inclined to question the need for UID or DTSTAMP in available as= =20 > the component cannot stand alone If you ever get two of them it'd be nice to know which one is the freshest, and that yet they are still the same thing. Perhaps there is value in having something rather than UID, however. Seen out of context it's not clear to me what the above is referencing, but (e.g.) as a sub-component of a VCARD the DTSTAMP and UID from the outer component would obviate any need for them inside this component. Cheers, Andrew. --=20 ------------------------------------------------------------------------ http://andrew.mcmillan.net.nz/ Porirua, New Zealand Twitter: _karora Phone: +64(272)DEBIAN Cat, n.: Lapwarmer with built-in buzzer. ------------------------------------------------------------------------ --=-0IvgZlYnuq5WDXY2vcJl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABCAAGBQJN1HNyAAoJEOr8/r+P646/G0oQAKu/kaNhj5J7ErpsDOp0I+ax lysluhgymxAKMM+hPpT25B1cqg0RQwi0n+NWSMOmF1ooK/aOv4rBEvAn04zmGiyG V1sKIMtX4UMToXN7xMvtSsCWjYrWBgp09H8oqNQqZkwk37qCFRA/zbN9pVgv64Qp RDHu4Z2cqKwoi97UJsRVkNfs0DyhGrFDsgC+9p9jZ8XS5xWdGC3n333lCYD+3pKb 33yRLcfQK2sbmh6I++x70jmIZsd+AtXax6QEyVTn34rd67ujYUOMWLijio7UVgPj kjkXoH6q3JCjLjLysgZ5TdDgijHsIIePD0WI17BiBnlh3y49/wB2BRy2KF55frPX ifs4vfeCTv2iZw7we229DkUg7hD4DJcgglUaFbLC1boXyE9j0e4hozF4ycB+RP4I +wsIY3+pidNrRpbP+fKCiWdvdB6pcE6GUoBo2+LqBdXTdAAa3mOXRRq6ldjJWfw4 zYIvH2eiEAQbE7m9jHQ1Z0qpz4bOLlIbbqDJhVqyJTS/UTlO0PH50Rvy21Lwuzn1 9JMTKib2oluFix2u5OcQs9ykF8qxNepl291RGXjDTf0N7qyeIp85IZgwChYLLpf9 2oJVqD2AWks3jR31zDR4PolHV/F4BdT2TveNFwsDRXkyrDnCKCBrXfTii74j0L7C HE5eO3xt7JdSzWq8QEUQ =rhAy -----END PGP SIGNATURE----- --=-0IvgZlYnuq5WDXY2vcJl-- From bernard.desruisseaux@oracle.com Thu May 26 13:15:53 2011 Return-Path: X-Original-To: caldav@ietfa.amsl.com Delivered-To: caldav@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 769F0E0689; Thu, 26 May 2011 13:15:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.598 X-Spam-Level: X-Spam-Status: No, score=-8.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZxf+YHWyDaf; Thu, 26 May 2011 13:15:51 -0700 (PDT) Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by ietfa.amsl.com (Postfix) with ESMTP id A4B4EE0694; Thu, 26 May 2011 13:15:51 -0700 (PDT) Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p4QKFmY6029348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 26 May 2011 20:15:50 GMT Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id p4QKFlqo029547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 May 2011 20:15:48 GMT Received: from hqdfmt01.oracle.com (hqdfmt01.oracle.com [148.87.24.194]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p4QKFfoD026757; Thu, 26 May 2011 15:15:42 -0500 Received: from [10.159.54.55] (/10.159.54.55) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 26 May 2011 13:15:40 -0700 USER-AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 X-ORACLE-DEBUG=STACK X-ORACLE-LIMIT=2500 OracleBeehiveExtension/1.1.0.0pre29-Alpha Thunderbird/3.1.10 MIME-Version: 1.0 Message-ID: <4DDEB4E7.1050708@oracle.com> Date: Thu, 26 May 2011 13:15:35 -0700 (PDT) From: Bernard Desruisseaux To: IETF Calsify , IETF CalDAV , IETF iSchedule Content-Type: multipart/alternative; boundary="------------000308070703080302060204" Content-Transfer-Encoding: 7bit X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090207.4DDEB4F6.0229:SCFMA922111,ss=1,fgs=0 Cc: "Eric S. Chan" Subject: [caldav] Fwd: [members] 30-day Public Review for Integrated Collaboration Object Model for Interoperable Collaboration Services Version 1.0, Committee Specification Draft 01 X-BeenThere: caldav@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 20:15:53 -0000 --------------000308070703080302060204 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable I'm forwarding this message on behalf of Eric S. Chan, who is not on this mailing list. -------- Original Message -------- Subject: [members] 30-day Public Review for Integrated Collaboration=20 Object Model for Interoperable Collaboration Services Version 1.0,=20 Committee Specification Draft 01 Date: Thu, 19 May 2011 14:37:45 -0700 (PDT) From: Chet Ensign To: tc-announce@lists.oasis-open.org, members@lists.oasis-open.org,=20 icom@lists.oasis-open.org CC: Carol Geyer , Chet Ensign=20 , Robin Cover , Paul=20 Knight , tab@lists.oasis-open.org,=20 board-plus@lists.oasis-open.org The OASIS Integrated Collaboration Object Model for Interoperable Collabo= ration Services (ICOM) TC [1] members have recently approved a Committee = Specification Draft (CSD) and submitted this specification for 30-day pub= lic review: Integrated Collaboration Object Model (ICOM) for Interoperable Coll= aboration Services Version 1.0 Committee Specification Draft 01 / Public Review Draft 01 16 March 2011 Specification Overview: The Integrated Collaboration Object Model (ICOM) for Interoperable = Collaboration Services standard defines a framework for integrating a bro= ad range of domain models for collaboration activities in an integrated a= nd interoperable collaboration environment. The framework is intended to = enable seamless transitions across collaboration activities. For example,= applications can aggregate conversation threads in email with other conv= ersations on the same topic in instant message, over the phone or via rea= l-time conferencing, by discussion threads in community forum, weblog or = micro blog, and activity stream of participants from all channels. ICOM e= ncompasses and improves on a range of models which are part of existing s= tandards and technologies. The framework lowers the barrier for independe= nt software vendors and open source communities to integrate collaboratio= n services and to create collaboration tools that offer seamless user exp= erience for diverse collaboration activities with minimal context switchi= ng. Public Review Period: The public review starts today, 19 May 2011 and ends 18 June 2011. This is an open invitation to comment. OASIS solicits feedback from= potential users, developers and others, whether OASIS members or not, fo= r the sake of improving the interoperability and quality of its technical= work. URIs: The prose specification document and related files are available he= re: Editable Source (Authoritative): http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd= 01.doc HTML: http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd= 01.html PDF: http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd= 01.pdf Other specification artifacts: Additional information about the specification and the OASIS OASIS = Integrated Collaboration Object Model for Interoperable Collaboration Ser= vices TC may be found at the TC's public home page: http://www.oasis-open.org/committees/icom/ Comments may be submitted to the TC by any person through the use o= f the OASIS TC Comment Facility which can be located via the button label= ed "Send A Comment" at the top of the TC public home, or directly at: http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=3Dicom Comments submitted by TC non-members for this work and for other wo= rk of this TC are publicly archived and can be viewed at: http://lists.oasis-open.org/archives/icom-comment/ All comments submitted to OASIS are subject to the OASIS Feedback L= icense, which ensures that the feedback you provide carries the same obli= gations at least as the obligations of the TC members. In connection with= this public review of 'Integrated Collaboration Object Model (ICOM) for = Interoperable Collaboration Services Version 1.0', we call your attention= to the OASIS IPR Policy [2] applicable especially [3] to the work of thi= s technical committee. All members of the TC should be familiar with this= document, which may create obligations regarding the disclosure and avai= lability of a member's patent, copyright, trademark and license rights th= at read on an approved OASIS specification. OASIS invites any persons who= know of any such claims to disclose these if they may be essential to th= e implementation of the above specification, so that notice of them may b= e posted to the notice page for this TC's work. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Additional references: [1] OASIS Integrated Collaboration Object Model for Interoperable Collabo= ration Services TC http://www.oasis-open.org/committees/icom/ [2] http://www.oasis-open.org/who/intellectualproperty.php [3] http://www.oasis-open.org/committees/icom/ipr.php http://www.oasis-open.org/who/intellectualproperty.php#s10.2.3 RF on Limited Terms Mode IPR Mode /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-378-3472 Mobile: +1 201-341-1393 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open --------------------------------------------------------------------- This email list is used solely by OASIS for official consortium communica= tions. Opt-out requests may be sent to member-services@oasis-open.org, however, = all members are strongly encouraged to maintain a subscription to this li= st. --------------000308070703080302060204 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 
I'm forwarding this message on behalf of Eric S. Chan <eric-s.chan@oracle.com>, who is not on this mailing list.
-------- Original Message --------
Subject: [members] 30-day Public Review for Integrated Collaboration Object Model for Interoperable Collaboration Services Version 1.0, Committee Specification Draft 01
Date: Thu, 19 May 2011 14:37:45 -0700 (PDT)
From: Chet Ensign <chet.ensign@oasis-open.org>
To: tc-announce@lists.oasis-open.org, members@lists.oasis-open.org, icom@lists.oasis-open.org
CC: Carol Geyer <carol.geyer@oasis-open.org>, Chet Ensign <chet.ensign@oasis-open.org>, Robin Cover <robin@oasis-open.org>, Paul Knight <paul.knight@oasis-open.org>, tab@lists.oasis-open.org, board-plus@lists.oasis-open.org 


The OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day public review:

     Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0 
     Committee Specification Draft 01 / Public Review Draft 01
     16 March 2011

Specification Overview:  
     The Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services standard defines a framework for integrating a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment. The framework is intended to enable seamless transitions across collaboration activities. For example, applications can aggregate conversation threads in email with other conversations on the same topic in instant message, over the phone or via real-time conferencing, by discussion threads in community forum, weblog or micro blog, and activity stream of participants from all channels. ICOM encompasses and improves on a range of models which are part of existing standards and technologies. The framework lowers the barrier for independent software vendors and open source communities to integrate collaboration services and to create collaboration tools that offer seamless user experience for diverse collaboration activit
ies with minimal context switching.

Public Review Period: 
     The public review starts today, 19 May 2011 and ends 18 June 2011.

     This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

URIs: 
     The prose specification document and related files are available here:

Editable Source (Authoritative): 
http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd01.doc 

HTML:
http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd01.html

PDF:
http://docs.oasis-open.org/icom/icom-ics/v1.0/csprd01/icom-ics-v1.0-csprd01.pdf

Other specification artifacts:
     Additional information about the specification and the OASIS OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services TC may be found at the TC's public home page:

http://www.oasis-open.org/committees/icom/ 

     Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button labeled "Send A Comment" at the top of the TC public home, or directly at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=icom

     Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/icom-comment/

     All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of 'Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0', we call your attention to the OASIS IPR Policy [2] applicable especially [3] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.


========== Additional references:

[1] OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services TC
     http://www.oasis-open.org/committees/icom/

[2] http://www.oasis-open.org/who/intellectualproperty.php

[3] http://www.oasis-open.org/committees/icom/ipr.php
     http://www.oasis-open.org/who/intellectualproperty.php#s10.2.3
     RF on Limited Terms Mode IPR Mode


/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-378-3472
Mobile: +1 201-341-1393

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open


---------------------------------------------------------------------

This email list is used solely by OASIS for official consortium communications.

Opt-out requests may be sent to member-services@oasis-open.org, however, all members are strongly encouraged to maintain a subscription to this list.
--------------000308070703080302060204--