XEP-0292 uses the XML format defined in RFC 6351. Section 11.3 has an example
vCard. Near the bottom is the "logo" element with a child "uri" element. RFC
6352 defines the logo element as containing a child element of value-uri. This
is defined as an element named "uri" that is any URI type. In the example, a
data URI is being used.
I am not overly familiar with the data URI format but when I looked it up it
says the format requires you to specify the encoding. The example in section
11.3 of the XEP does not do this. It has the following:
<uri>data:image/jpeg;{data}</uri>
Where "{data} is the base 64 encoded image. My research shows that the data
URI should look more like this:
data:image/jpeg;base64,{data}
Can someone let me know which is correct? I thought maybe it would just
default to base 64 if omitted but the article I read said it defaults to
something else entirely.
On a slightly related not, the examples in XEP-0292 show the "n" element as
containing a child element of "middle". The xCard specification (RFC 6351)
indicates only the following children (surname, given, additional, prefix,
suffix) all of which are mandatory (but can be empty). This seems to be a
conflict.
I know XEP-0292 is currently deferred but we have a need for this. I wouldn't
mind any insight on whether I am just reading them wrong as that is always a
possibility. I would also be happy to provide any additional feedback or make
additional suggestions related to this XEP in order to bring it out of
"deferred" status.
