> I think you misunderstood what was being referred to as extended presence information. This is about multiple <x xmlns="http://jabber.org/protocol/muc#user"/> elements not being
> allowed. Other information can certainly be included in presence (e.g., MUC avatars are advertised using presence). You are free to have your own custom XML. Ah, I see in the spec now - only presence information "about roles, affiliations, full JIDs, or status codes qualified by the 'http://jabber.org/protocol/muc#user' namespace (based on information the service knows about occupants, e.g., roles, or as a result of actions taken by a moderator or room administrator)". Thanks for the clarification! Karthik Karthik Kailash | Product SocialVision, Online Television Becomes a Social Experience CELL . 408.768.7704 | WEB . www.socialvisioninc.com | FACEBOOK . <http://www.facebook.com/socialvision> facebook.com/socialvision | TWITTER . <http://twitter.com/socialvision> twitter.com/socialvision
