Patrik Olsson (ECS | 3 Mar 08:35 1998
Picon
Picon

PIM Synchronizing

Hi!

My name is Patrik Olsson and I'm working with a program to be used for
PIM synchronizing.

I have a few questions regarding the iCalendar standard:

* Is it intended to be used for PIM synchronizing software?

* My software is going to be written in Java. Is it possible to use
TCP/IP as the carrier for the commands?

* Where can I turn to get more information and where can I find some
samples of code (prefferably synch code)?

* Are ther any books yet on the subject.

Thanks
Patrik Olsson
patrik.olsson <at> ecs.ericsson.se

Wolfgang Spraul | 3 Mar 18:18 1998

RE: PIM Synchronizing

Patrik:

Check out these URLs:

CAP:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-calsch-capreq-00.txt

Bayou:
http://www.parc.xerox.com/csl/projects/bayou/

Access Replication:
http://www.research.microsoft.com/~gray/WingMan_Replicas.doc

Replication Techniques:
http://www.wkap.nl/book.htm/0-7923-9800-9

Good luck - you can contact me if you need anything else.
Wolfgang

-----Original Message-----
From:	Patrik Olsson (ECS) [SMTP:Patrik.Olsson <at> ecs.ericsson.se]
Sent:	Tuesday, March 03, 1998 8:36 AM
To:	'ietf-calendar <at> imc.org'
Subject:	PIM Synchronizing

Hi!

My name is Patrik Olsson and I'm working with a program to be used for
PIM synchronizing.

(Continue reading)

Steve Silverberg (Exchange | 5 Mar 22:05 1998
Picon

RE: Status of proposed calendar access protocol standard

I would expect to see a new calendar access protocol draft in '98 and and
RFC in '99

-----Original Message-----
From: deanna <at> codestorm.com [mailto:deanna <at> codestorm.com]
Sent: Thursday, March 05, 1998 12:54 PM
To: ietf-calendar <at> imc.org
Subject: Status of proposed calendar access protocol standard

I'm trying to find out for a colleague the status of IETF's calendaring
access proposals.

Based on the goals and milestones listed in IETF-Calendar's charter on the
IMC web site, am I correct to assume that the calendaring standards are at
the proposed draft stage (as of August 1997) and will not be submitted as a
proposed standard until April 1998?

Please let me know if this schedule is expected to change.

Yours gratefully,

Deanna Toews
<deanna <at> codestorm.com>

Deanna Toews | 5 Mar 21:54 1998

Status of proposed calendar access protocol standard

I'm trying to find out for a colleague the status of IETF's calendaring
access proposals.

Based on the goals and milestones listed in IETF-Calendar's charter on the
IMC web site, am I correct to assume that the calendaring standards are at
the proposed draft stage (as of August 1997) and will not be submitted as a
proposed standard until April 1998?

Please let me know if this schedule is expected to change.

Yours gratefully,

Deanna Toews
<deanna <at> codestorm.com>

Frank Dawson | 5 Mar 22:37 1998
Picon
Picon

Re: Status of proposed calendar access protocol standard

The WG focus has been on iCalendar, iTIP and iMIP. I expect that CAP won't
be getting much attention until later in 1998. Maybe a RFC in 1999?

- - Frank

John Sun | 6 Mar 03:10 1998
Picon

Couple of questions

    A couple of comments of the spec.

Can the Related-To property appear MORE than once in a VEvent, VTodo,
VJournal?
Can the URL property appear MORE than once in a VEvent, VTodo, VJournal?

I ask this because a beta version of iCal Core Spec 0.6 (Feb. 20)  I
have differs from
what iCal Core Spec 0.5 says about these properties.

Also in the Feb.20 iCal Core 0.6 Spec, there is a typo in 4.8.2.3
Contact Example.
The last example has ALTREP spelled as ALREP.
Attachment (vcard.vcf): text/x-vcard, 463 bytes
Frank Dawson | 6 Mar 20:43 1998
Picon
Picon

Re: Couple of questions

On Thursday, March 05, 1998 9:18 PM, John Sun wrote, in part:

>Can the Related-To property appear MORE than once in a VEvent, VTodo,
>VJournal?

Yes. You would need to be able to specify more than one RELATED-TO to point
to your parent and your siblings for a related set of calendar components.

For example, to show that a parent VEVENT is related to two child VEVENT
definitons and also a single child VTODO definition, you might specify:

   BEGIN:VCALENDAR
   ...required calendar properties
   METHOD:PUBLISH
   BEGIN:VEVENT
   ...required component properties
   UID:<uid1 <at> host.com>
   SUMMARY:General Announcement of CalendarConnect I
   RELATED-TO;RELATE=CHILD:<uid2 <at> host.com>
   RELATED-TO;RELATE=CHILD:<uid3 <at> host.com>
   RELATED-TO;RELATE=CHILD:<uid4 <at> host.com>
   END:VEVENT
   END:VCALENDAR

   BEGIN:VCALENDAR
   ...required calendar properties
   METHOD:PUBLISH
   BEGIN:VEVENT
   ...required component properties
   UID:<uid2 <at> host.com>
(Continue reading)

Internet-Drafts | 17 Mar 16:54 1998
Picon

I-D ACTION:draft-ietf-calsch-itip-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring and Scheduling Working Group of the IETF.

	Title		: iCalendar Transport-Independent Interoperability
                          Protocol (iTIP) Scheduling Events, BusyTime, To-dos 
                          and Journal Entries
	Author(s)	: R. Hopson, S. Mansour, F. Dawson  Jr., S. Silverberg
	Filename	: draft-ietf-calsch-itip-03.txt
	Pages		: 97
	Date		: 16-Mar-98
	
This document specifies how calendaring systems use iCalendar objects to
interoperate with other calendar systems. It does so in a general way so
as to allow multiple methods of communication between systems.
Subsequent documents specify interoperable methods of communications
between systems that use this protocol.

The document outlines a model for calendar exchange that defines both
static and dynamic event, to-do, journal and free/busy objects. Static
objects are used to transmit information from one entity to another
without the expectation of continuity or referential integrity with the
original item. Dynamic objects are a superset of static objects and will
gracefully degrade to their static counterparts for clients that only
support static objects.

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-calsch-itip-03.txt".
A URL for the Internet-Draft is:
(Continue reading)

Internet-Drafts | 17 Mar 16:54 1998
Picon

I-D ACTION:draft-ietf-calsch-imip-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring and Scheduling Working Group of the IETF.

	Title		: iCalendar Message-based Interoperability 
                          Protocol (iMIP)
	Author(s)	: F. Dawson, S. Mansour, S. Silverberg
	Filename	: draft-ietf-calsch-imip-04.txt
	Pages		: 15
	Date		: 16-Mar-98
	
This document specifies a binding from the iCalendar Transport-
independent Interoperability Protocol [ITIP] to Internet email-based
transports. Calendaring entries defined by the iCalendar Object Model
[ICAL] are composed using constructs from [RFC-822], [RFC-2045], [RFC-
2046], [RFC-2047], [RFC-2048] and [RFC-2049].

This document is based on the calendaring and scheduling model defined
by [ICMS].

This document is based on discussions within the Internet Engineering
Task Force (IETF) Calendaring and Scheduling (CALSCH) working group.
More information about the IETF CALSCH working group activities can be
found on the IMC web site at http://www.imc.org, the IETF web site at
http://www.ietf.org/html.charters/calsch-charter.html. Refer to the
references within this document for further information on how to access
these various documents.

Distribution of this document is unlimited. Comments and suggestions for
improvement should be sent to the authors.

(Continue reading)

Internet-Drafts | 17 Mar 16:54 1998
Picon

I-D ACTION:draft-ietf-calsch-ical-06.txt

A Revised Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring and Scheduling Working Group of the IETF.

	Title		: Internet Calendaring and Scheduling 
                          Core Object Specification (iCalendar)
	Author(s)	: F. Dawson, D. Stenerson
	Filename	: draft-ietf-calsch-ical-06.txt
	Pages		: 111
	Date		: 16-Mar-98
	
   There is a clear need to provide and deploy interoperable calendaring
   and scheduling services for the Internet. Current group scheduling
   and Personal Information Management (PIM) products are being extended
   for use across the Internet, today, in proprietary ways. This memo
   has been defined to provide the definition of a common format for
   openly exchanging calendaring and scheduling information across the
   Internet.

   This memo is formatted as a registration for a MIME media type per
   [RFC 2048]. However, the format in this memo is equally applicable
   for use outside of a MIME message content type.

   The proposed media type value is ''text/calendar''. This string would
   label a media type containing calendaring and scheduling information
   encoded as text characters formatted in a manner outlined below.

   This MIME media type provides a standard content type for capturing
   calendar event, to-do and journal entry information. It also can be
   used to convey free/busy time information. The content type is
   suitable as a MIME message entity that can be transferred over MIME
(Continue reading)


Gmane