From cyrus@daboo.name Wed May 18 07:15:29 2011 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A858E0718; Wed, 18 May 2011 07:15:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 YUGmSwy5PWXQ; Wed, 18 May 2011 07:15:29 -0700 (PDT) Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id B8CECE06A1; Wed, 18 May 2011 07:15:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id BE4748A559B; Wed, 18 May 2011 10:15:27 -0400 (EDT) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEX2u-W+VGsP; Wed, 18 May 2011 10:15:23 -0400 (EDT) Received: from [17.45.162.218] (unknown [17.45.162.218]) by daboo.name (Postfix) with ESMTPSA id 23B898A5590; Wed, 18 May 2011 10:15:21 -0400 (EDT) Date: Wed, 18 May 2011 10:15:20 -0400 From: Cyrus Daboo To: CardDAV Message-ID: <5647EF58A6594053C5BE14E5@[17.45.162.218]> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1013 Cc: Calsify Subject: [calsify] iCalendar-in-XMlL updated X-BeenThere: calsify@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: Wed, 18 May 2011 14:15:30 -0000 Hi folks, The iCalendar-in-XMl spec has been updated to account for comments during the last call which ended last week. Changes are noted in the spec at . In regard to vcard-in-XML: please look at Section 5 which is how we agreed to deal with unrecognized property/parameter default values. I believe similar text and new XML value element is required in the vCard-in-XML spec too. One other thing, we ended up changing the date and time XML value formats to be more inline with the format used in XML schema: specifically adding "-" separators between the date components and ":" separators between the time components. This change was prompted by feedback from developers who wanted to be able to reuse xsd date/time types for validation and processing. This seemed like a reasonable request so we made the change. I would have thought a similar situation exists for vcard-in-XML so we may want to consider that. -- Cyrus Daboo From calsify-bounces@ietf.org Wed May 18 07:15:32 2011 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 136A8E0718; Wed, 18 May 2011 07:15:32 -0700 (PDT) X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A858E0718; Wed, 18 May 2011 07:15:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 YUGmSwy5PWXQ; Wed, 18 May 2011 07:15:29 -0700 (PDT) Received: from daboo.name (daboo.name [151.201.22.177]) by ietfa.amsl.com (Postfix) with ESMTP id B8CECE06A1; Wed, 18 May 2011 07:15:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id BE4748A559B; Wed, 18 May 2011 10:15:27 -0400 (EDT) X-Virus-Scanned: amavisd-new at daboo.name Received: from daboo.name ([127.0.0.1]) by localhost (chewy.daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEX2u-W+VGsP; Wed, 18 May 2011 10:15:23 -0400 (EDT) Received: from [17.45.162.218] (unknown [17.45.162.218]) by daboo.name (Postfix) with ESMTPSA id 23B898A5590; Wed, 18 May 2011 10:15:21 -0400 (EDT) Date: Wed, 18 May 2011 10:15:20 -0400 From: Cyrus Daboo To: CardDAV Message-ID: <5647EF58A6594053C5BE14E5@[17.45.162.218]> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Disposition: inline; size=1013 Cc: Calsify Subject: [calsify] iCalendar-in-XMlL updated X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org Hi folks, The iCalendar-in-XMl spec has been updated to account for comments during the last call which ended last week. Changes are noted in the spec at . In regard to vcard-in-XML: please look at Section 5 which is how we agreed to deal with unrecognized property/parameter default values. I believe similar text and new XML value element is required in the vCard-in-XML spec too. One other thing, we ended up changing the date and time XML value formats to be more inline with the format used in XML schema: specifically adding "-" separators between the date components and ":" separators between the time components. This change was prompted by feedback from developers who wanted to be able to reuse xsd date/time types for validation and processing. This seemed like a reasonable request so we made the change. I would have thought a similar situation exists for vcard-in-XML so we may want to consider that. -- Cyrus Daboo _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From calsify-bounces@ietf.org Fri May 20 21:04:55 2011 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323CBE06C1; Fri, 20 May 2011 21:04:55 -0700 (PDT) X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7985FE06D8 for ; Fri, 20 May 2011 21:04:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 5V2J1nXD3VJ6 for ; Fri, 20 May 2011 21:04:52 -0700 (PDT) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4842DE068E for ; Fri, 20 May 2011 21:04:52 -0700 (PDT) Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by QMTA11.westchester.pa.mail.comcast.net with comcast id m42e1g0010cZkys5B44s96; Sat, 21 May 2011 04:04:52 +0000 Received: from THARE ([71.203.98.77]) by omta10.westchester.pa.mail.comcast.net with comcast id m44r1g00E1gAkVz3W44rFw; Sat, 21 May 2011 04:04:52 +0000 From: "Tim Hare" To: "'Cyrus Daboo'" , "'CardDAV'" References: <5647EF58A6594053C5BE14E5@[17.45.162.218]> In-Reply-To: <5647EF58A6594053C5BE14E5@[17.45.162.218]> Date: Sat, 21 May 2011 00:04:50 -0400 Message-ID: <010401cc176c$3bcd9f60$b368de20$@net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcwVZg5wIs3JWSKKTUiu0puWZ3I7AACAkqfg Content-Language: en-us Cc: 'Calsify' Subject: Re: [calsify] iCalendar-in-XMlL updated X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org I have some questions, since I am not an XML expert in any way despite writing at least one XML-to-iCalendar transform: A. Is 3.2 trying to say that the element can contain another element? Or is it merely trying to say that once component such as can contain another component such as ? B. Is the property compatible with other geo-type tagging such as which I believe is from RDF? This comes from my belief that XML is so flexible that we ought to be able to use any combination of namespaces which provides a mapping to iCalendar. C. I think I missed, somewhere, why property parameters were not mapped to XML attributes? It seems a more direct mapping for example, to map PROPERTY-NAME;PARAMETER-NAME="param":value to value rather than: value D. Do URIs always have to be surrounded by pairs? As in C: why not ? Tim Hare Interested Bystander, Non-Inc. -----Original Message----- From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On Behalf Of Cyrus Daboo Sent: Wednesday, May 18, 2011 10:15 AM To: CardDAV Cc: Calsify Subject: [calsify] iCalendar-in-XMlL updated Hi folks, The iCalendar-in-XMl spec has been updated to account for comments during the last call which ended last week. Changes are noted in the spec at . In regard to vcard-in-XML: please look at Section 5 which is how we agreed to deal with unrecognized property/parameter default values. I believe similar text and new XML value element is required in the vCard-in-XML spec too. One other thing, we ended up changing the date and time XML value formats to be more inline with the format used in XML schema: specifically adding "-" separators between the date components and ":" separators between the time components. This change was prompted by feedback from developers who wanted to be able to reuse xsd date/time types for validation and processing. This seemed like a reasonable request so we made the change. I would have thought a similar situation exists for vcard-in-XML so we may want to consider that. -- Cyrus Daboo _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From timhare@comcast.net Fri May 20 21:04:53 2011 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7985FE06D8 for ; Fri, 20 May 2011 21:04:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 5V2J1nXD3VJ6 for ; Fri, 20 May 2011 21:04:52 -0700 (PDT) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4842DE068E for ; Fri, 20 May 2011 21:04:52 -0700 (PDT) Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by QMTA11.westchester.pa.mail.comcast.net with comcast id m42e1g0010cZkys5B44s96; Sat, 21 May 2011 04:04:52 +0000 Received: from THARE ([71.203.98.77]) by omta10.westchester.pa.mail.comcast.net with comcast id m44r1g00E1gAkVz3W44rFw; Sat, 21 May 2011 04:04:52 +0000 From: "Tim Hare" To: "'Cyrus Daboo'" , "'CardDAV'" References: <5647EF58A6594053C5BE14E5@[17.45.162.218]> In-Reply-To: <5647EF58A6594053C5BE14E5@[17.45.162.218]> Date: Sat, 21 May 2011 00:04:50 -0400 Message-ID: <010401cc176c$3bcd9f60$b368de20$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcwVZg5wIs3JWSKKTUiu0puWZ3I7AACAkqfg Content-Language: en-us Cc: 'Calsify' Subject: Re: [calsify] iCalendar-in-XMlL updated X-BeenThere: calsify@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: Sat, 21 May 2011 04:04:53 -0000 I have some questions, since I am not an XML expert in any way despite writing at least one XML-to-iCalendar transform: A. Is 3.2 trying to say that the element can contain another element? Or is it merely trying to say that once component such as can contain another component such as ? B. Is the property compatible with other geo-type tagging such as which I believe is from RDF? This comes from my belief that XML is so flexible that we ought to be able to use any combination of namespaces which provides a mapping to iCalendar. C. I think I missed, somewhere, why property parameters were not mapped to XML attributes? It seems a more direct mapping for example, to map PROPERTY-NAME;PARAMETER-NAME="param":value to value rather than: value D. Do URIs always have to be surrounded by pairs? As in C: why not ? Tim Hare Interested Bystander, Non-Inc. -----Original Message----- From: calsify-bounces@ietf.org [mailto:calsify-bounces@ietf.org] On Behalf Of Cyrus Daboo Sent: Wednesday, May 18, 2011 10:15 AM To: CardDAV Cc: Calsify Subject: [calsify] iCalendar-in-XMlL updated Hi folks, The iCalendar-in-XMl spec has been updated to account for comments during the last call which ended last week. Changes are noted in the spec at . In regard to vcard-in-XML: please look at Section 5 which is how we agreed to deal with unrecognized property/parameter default values. I believe similar text and new XML value element is required in the vCard-in-XML spec too. One other thing, we ended up changing the date and time XML value formats to be more inline with the format used in XML schema: specifically adding "-" separators between the date components and ":" separators between the time components. This change was prompted by feedback from developers who wanted to be able to reuse xsd date/time types for validation and processing. This seemed like a reasonable request so we made the change. I would have thought a similar situation exists for vcard-in-XML so we may want to consider that. -- Cyrus Daboo _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify From calsify-bounces@ietf.org Thu May 26 13:15:55 2011 Return-Path: X-Original-To: calsify-archive-feit0ahl@lists.ietf.org Delivered-To: ietfarch-calsify-archive-Feit0ahl@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55DAEE0767; Thu, 26 May 2011 13:15:55 -0700 (PDT) X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@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 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: [calsify] Fwd: [members] 30-day Public Review for Integrated Collaboration Object Model for Interoperable Collaboration Services Version 1.0, Committee Specification Draft 01 X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7426022349109812050==" Sender: calsify-bounces@ietf.org Errors-To: calsify-bounces@ietf.org --===============7426022349109812050== Content-Type: multipart/alternative; boundary="------------000308070703080302060204" Content-Transfer-Encoding: 7bit --------------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-- --===============7426022349109812050== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ calsify mailing list calsify@ietf.org https://www.ietf.org/mailman/listinfo/calsify --===============7426022349109812050==-- From bernard.desruisseaux@oracle.com Thu May 26 13:15:53 2011 Return-Path: X-Original-To: calsify@ietfa.amsl.com Delivered-To: calsify@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: [calsify] Fwd: [members] 30-day Public Review for Integrated Collaboration Object Model for Interoperable Collaboration Services Version 1.0, Committee Specification Draft 01 X-BeenThere: calsify@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--