Re: [Standards] XEP-0054 (vcard-temp) Issues

2011-10-27 Thread Peter Saint-Andre
On 10/27/11 3:19 PM, Bala Pitchandi wrote: > I agree with you on xCard/XEP-0292. I would rather implement that > than implementing XEP-0054 but like you said no one (*cough* Google > *cough*) has implemented it yet. To be fair, vCard4 is new. But we need to figure out how to bootstrap implementati

Re: [Standards] XEP-0054 (vcard-temp) Issues

2011-10-27 Thread Bala Pitchandi
PM To: XMPP Standards Cc: Bala Pitchandi Subject: Re: [Standards] XEP-0054 (vcard-temp) Issues On 10/27/11 3:03 PM, Bala Pitchandi wrote: > The implementation note (pasted below) does not say that VERSION > element is optional: > > Some Jabber implementations add a 'version&

Re: [Standards] XEP-0054 (vcard-temp) Issues

2011-10-27 Thread Peter Saint-Andre
On 10/27/11 3:03 PM, Bala Pitchandi wrote: > The implementation note (pasted below) does not say that VERSION > element is optional: > > Some Jabber implementations add a 'version' attribute to the > element, with the value set at "2.0" or "3.0". The DTD is incorrect, > and the examples in draft-

Re: [Standards] XEP-0054 (vcard-temp) Issues

2011-10-27 Thread Bala Pitchandi
From: standards-boun...@xmpp.org [mailto:standards-boun...@xmpp.org] On Behalf Of Peter Saint-Andre Sent: Thursday, October 27, 2011 4:58 PM To: XMPP Standards Cc: Bala Pitchandi Subject: Re: [Standards] XEP-0054 (vcard-temp) Issues On 10/27/11 2:54 PM, Bala Pitchandi wrote: > The DTD in section 9

Re: [Standards] XEP-0054 (vcard-temp) Issues

2011-10-27 Thread Peter Saint-Andre
On 10/27/11 2:54 PM, Bala Pitchandi wrote: > The DTD in section 9 > mandates that the element vCard must contain VERSION, FN, N but the > examples in section 3.1 do not comply. Particularly the vCard retrieval > request (Section 3.1, example 1) has an

[Standards] XEP-0054 (vcard-temp) Issues

2011-10-27 Thread Bala Pitchandi
The DTD in section 9 mandates that the element vCard must contain VERSION, FN, N but the examples in section 3.1 do not comply. Particularly the vCard retrieval request (Section 3.1, example 1) has an empty vCard element.

Re: [Standards] XEP-0054: vcard-temp

2009-07-30 Thread Joe Hildebrand
By the way, XSF folks interested in vcard should be tracking draft-perreault-vcarddav-vcardxml in the IETF's vcarddav working group. We've had an interesting discussion here in Stockholm this week about extensibility and bi-directional mapping to the non-XML format. http://tools.ietf.org/html/draf

Re: [Standards] XEP-0054: vcard-temp

2009-07-29 Thread Waqas Hussain
On Wed, Jul 29, 2009 at 11:14 PM, Daniel Willmann < dan...@totalueberwachung.de> wrote: > Hi, > > I just noticed a discrepancy between handling of the ext. address field > in vcards. > > The XEP specifies that the value should be saved in tags and > this is what jabberd2 seems to be expecting. >

[Standards] XEP-0054: vcard-temp

2009-07-29 Thread Daniel Willmann
Hi, I just noticed a discrepancy between handling of the ext. address field in vcards. The XEP specifies that the value should be saved in tags and this is what jabberd2 seems to be expecting. Both Psi and Gajim though seem to be using . This doesn't bother ejabberd since it just saves the xml,