[Standards] Clarification for XEP-0054: private fields

Matthew Wild mwild1 at gmail.com
Thu Sep 19 07:24:14 UTC 2019

On Thu, 19 Sep 2019 at 08:10, Wichert Akkerman <wichert at wiggy.net> 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 draft-dawson-vcard-xml-dtd-01, or c) be liberal and preserve unknown elements?
> This appears to be a fairly common question for ejabberd, which allowed unknown fields up to 16.11, after which it started throwing them away.

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 would also get discarded.
However I also see that there is a defined way to handle unknown
fields in conversion ( https://tools.ietf.org/html/rfc6351#section-6
), so it's not impossible to preserve them.

That said, our vcard4 implementation largely handles the submitted
vcard as an XML blob also - putting stuff into a custom namespace is
totally possible.


More information about the Standards mailing list