Hi, RFC 4826 allows the usage of <entry-ref> and <external>: The <external> element is similar to the <entry-ref> element. Like <entry-ref>, it is only meaningful in documents obtained from an XCAP server. It too is a reference to content stored elsewhere. However, it refers to an entire list, and furthermore, it allows that list to be present on another server.
I've realized that OMA and RCS specifications just do usage of <external>. I don't agree the "advantage" mentioned above for <external>, as the XCAP servers can know by itself the exact location of a XCAP resource/application without the need of inspecting the server URI and port. And also the usage of <external> introduces a complexity: if the server domain/port changes the document becomes unreachable. So, why to use <external> rather than <entry-ref>? -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
