Not yet. While certainly in the range of the atom protocol, and the gData implementaiton of it, the calendar backend right now does not allow to store arbitrary schema extensions. There are some good reasons for it, but we are investigating the possibility of extending this, but as always, this will be driven by customer demand.

My advice, therefore, just voice it, with a good case, to the calendar feature request page... I did submit it internally already though.

Frank Mantek

On 7/11/06, Cab0 <[EMAIL PROTECTED]> wrote:

Thanks for checking. I can set them in one uri for now.

Is there any other way to persist meta data? Is introducing my own
schema element a possibility as mentioned above?



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to