2009/2/17 brianv <[email protected]>: > > Thanks Ray. I hadn't seen that reference, I had been looking in the > generic api doc, which says: > > "You can add extended properties (arbitrary name-value pairs) to > Calendar events. These can be used to store application-specific IDs > or other small amounts of information your application needs when > interacting with a Google Calendar. The name of a property can contain > up to 47 characters, and the value can contain up to 1024 > characters." > > I missed the part about the URI. Any idea why the name is supposed to > be a URI? I've implemented with just an 'arbitrary' name, and it works > fine but I'm wondering if it's going to break someday in the future.
To my knowledge, you don't have to use a URI. However, you should use something that is guarenteed to be unique for your application. I usually like to use a reverse DNS entry (such as net.tjohns.myapp.foo), though a URL would work as well assuming it fits within the size constraints. You just want to avoid naming your property something generic, like "myData" or "rating", since that name could collide with another application that uses a similarly named field. -- Trevor Johns --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
