Hi Philipp,

Happy Holiday! Sorry for the long delay due to holiday vacation.

The following describes what and how to use sequence, uid and syncEvent to
do syncing.

gCal:sequence
Indicates the revision sequence number of the event as defined in Section
4.8.7.4 of RFC 2445. Must be non-negative
Properties
ex.  <gCal:sequence value='1'/>

gCal:uid
Indicates the globally unique identifier(UID) of the event as defined in
Section 4.8.4.7 of RFC 2445.
Must be a globally unique string and must follow specifications in Section
4.8.4.7 of RFC 2445.
ex.  <gCal:uid value='t9d6o9stha0j0cblaoi4s5l29c'/>

gCal:syncEvent
Indicates whether this is a sync scenario where we allow setting the
gCal:uid, gCal:sequence and the organizer of an event.
This property makes sense only while inserting and updating events. This
property should primarily be used in a sync scenario.
ex.  <gCal:syncEvent value="true" />

Hope it helps,
Austin

On Jan 2, 2008 1:36 AM, Philipp Kewisch <[EMAIL PROTECTED]> wrote:

>
> So it seems, gCal:uid is not settable. I thought this could be the
> solution to iTIP/iMIP problems. It would be great if setting the ID
> was possible. I'll file an issue on that. I'm still interested if its
> possible to search the UID via url in any way, i.e if its safe to
> assume http://www.google.com/calendar/feeds/user/public/basic/$url or
> such. Also I'm still not sure what gCal:syncEvent is?
>
> On Dec 27 2007, 8:54am, Philipp Kewisch <[EMAIL PROTECTED]> wrote:
> > I'm interested what gCal:syncEvent is? The new gCal properties might
> > be just what I need. Also, is gCal:uid settable and can it be searched
> > via url?
> >
> > Philipp
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to