Hi, RFC 4826 just defines a few XML fields for each buddy entry to get stored
in XCAP server, basically:
<entry uri="sip:j...@example.com">
<display-name>Joe Smith</display-name>
</entry>
RFC 4482 (CIDID) adds some more:
<xs:element name="card" type="xs:anyURI"/>
<xs:element name="display-name" type="xs:string"/>
<xs:element name="homepage" type="xs:anyURI"/>
<xs:element name="icon" type="xs:anyURI"/>
<xs:element name="map" type="xs:anyURI"/>
<xs:element name="sound" type="xs:anyURI"/>
However they are not enough at all. Most of the applications containing
contact list also allow other common attributes as mail, phone phone, mobile,
organization, role...
How could a SIP UA store these attributes using XCAP? I hope that each vendor
won't include its own propietary XML schema to accomplish this purpose so we
would get *again* the same => NO INTEROPERABILITY.
Is there any RFC describing such XML schema to be used in XCAP storage?
Thanks.
--
Iñaki Baz Castillo <i...@aliax.net>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
