[Standards] Clarification for XEP-0054: private fields

Peter Saint-Andre stpeter at mozilla.com
Fri Sep 20 18:21:09 UTC 2019

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 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.

Perhaps it's time to move forward with XEP-0292?


More information about the Standards mailing list