Iñaki Baz Castillo wrote: > 2010/5/25 Klaus Darilion <[email protected]>: >> What about using "classes". E.g. by specifying class=calendar for person >> elements created by the calender presence user agent the watcher might be >> smart enough to render the data as "this is what his calender says, but of >> course he might be somewhere else". > > Such field is not standarized so just a propietary implementation > would understand the meaning you propose.
Sorry, it is named <class> and is already defined. http://tools.ietf.org/html/rfc4480#section-3.3 regards klaus _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
