En/na Vikram Chhibber ha escrit:
This information can be carried in PIDF by means of XCAP or SIP protocol.
Information that is more of a characteristics of a person as per RFC
4479, large in size and does not change with time is most likely to be
updated and distributed using XCAP mechanism. See also RFC 4483. For
example:
The url to user's icon/display image can be carried using "status-icon" as defined in RFC 4480 gping under "dm:person"
His customized text can be part of "dm:note" under "person" element.
The image upload at server-end is done using non-SIP mechanism like HTTP PUT.
Other informaiton which is time sensitive and changes more frequently
goes as part of SIP PUBLISH/NOTIFY mechanism. For example:
The user status (can be customized one) is carried under "activities" element.
This display name can be carried over as "name" attribute in rlmi
document-RFC 4662.
IMO: This is more of a mutual understanding among vendors on what and
how this information has to be structured and distributed. There is no
standard that mandates any uniformity.
Hi,
An example of this interoperability agreement could be the GSMA
RCS initiative; check the technical
realization for examples on how they propose to use the status icon
and the free text (which is in fact what Vikram said).
Hope it helped,
Arnau
|
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
