On 9/19/19 1:01 AM, Wichert Akkerman wrote:
> I am looking for a clarification on XEP-0054. The history description
> for the XEP mentions that it essentially encapsulates
> draft-dawson-vcard-xml-dtd-01 over XMPP, with changes to using
> xuppercase for elements and adding JABBERID and
> DESC.
On 9/19/19 1:24 AM, Matthew Wild wrote:
> Prosody also historically preserved everything (it basically treated
> the vcard as an XML blob). However now we have moved to vcard4, our
> compatibility code can obviously only convert fields it knows and
> understands - therefore any custom fields
On Thu, 19 Sep 2019 at 08:10, Wichert Akkerman wrote:
> My question is: are implementation of XEP-0054 supposed to a) strictly use
> the DTD from XEP-0054, and thus required throw away any extra elements not
> mentioned there, b) support private fields since they are mentioned in
>
Hi everyone,
I am looking for a clarification on XEP-0054. The history description for the
XEP mentions that it essentially encapsulates draft-dawson-vcard-xml-dtd-01
over XMPP, with changes to using xuppercase for elements and adding JABBERID
and DESC. draft-dawson-vcard-xml-dtd-01 also
