Re: [OpenSIPS-Devel] New OpenXCAP release 2.0.0 with support for OMA XDM SIP SIMPLE specifications
2010/10/8 Saúl Ibarra Corretgé s...@ag-projects.com: * Check entry-ref entries in resource-lists OMA prohibits the usage of entry-ref. Just external-ref is allowed. entry-ref just exists in IETF's incomplete specs. What does OpenXCAP implement exactly? Can you point me to the document where that is stated please? I'm sorry but I can't remember it. But for sure I've read it in some OMA spec. In fact you won't find 'entry-ref' in any XCAP document defined by OMA. -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] New OpenXCAP release 2.0.0 with support for OMA XDM SIP SIMPLE specifications
Hi Iñaki, * Check external references for pres-rules and resource-lists How such check is done? There is a new configuration setting: allow_external_references, which by default is No. The external references must point to the same server and user in this case. * Don't allow external-ref paths which don't point to an 'entry' What about if that 'entry' is deleted later after the external-ref path is created? It's the client application responsibility to remove the reference. OpenXCAP will just check the XPATH expression. * Check entry-ref entries in resource-lists OMA prohibits the usage of entry-ref. Just external-ref is allowed. entry-ref just exists in IETF's incomplete specs. What does OpenXCAP implement exactly? Can you point me to the document where that is stated please? Thanks for the feedback! -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] New OpenXCAP release 2.0.0 with support for OMA XDM SIP SIMPLE specifications
On Oct 1, 2010, at 2:12 AM, Iñaki Baz Castillo wrote: 2010/9/29 Adrian Georgescu a...@ag-projects.com: Hello, There is a new release of OpenXCAP, version 2.0.0 It contains many bug fixes and buddy lists management based on OMA XDM specifications related to SIP SIMPLE presence. Hi, let me some comments inline: * Added OMA XDM support for Buddy Lists Management AFAIK OMA specs for buddylist management is not adopted. Instead IMS uses RCS specs which includes some changes to OMA specs, specially in buddylist management. Perhaps I am wrong and there are clients implementing OMA specs for buddylist? Yes, keep the faith. * Check external references for pres-rules and resource-lists How such check is done? We simply won't allow external references, all resource must be local and belong to the same user. * Don't allow external-ref paths which don't point to an 'entry' What about if that 'entry' is deleted later after the external-ref path is created? I am not sure what this means. You may check the commit for that change to get the insight of what it does. * Check entry-ref entries in resource-lists OMA prohibits the usage of entry-ref. Just external-ref is allowed. entry-ref just exists in IETF's incomplete specs. What does OpenXCAP implement exactly? We support both OMA and non-OMA requests. Regards. -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] New OpenXCAP release 2.0.0 with support for OMA XDM SIP SIMPLE specifications
Hello, There is a new release of OpenXCAP, version 2.0.0 It contains many bug fixes and buddy lists management based on OMA XDM specifications related to SIP SIMPLE presence. openxcap (2.0.0) unstable; urgency=low * Added OMA XDM support for Buddy Lists Management * Unquote external references in resource-lists and pres-rules * Fixed resource lists and RLS services schemas * Added test case for conditional PUT with If-Match * Use allow_external_references setting also for entry-ref elements * Fixed PUT with If-Match header * Fixed UTF-8 encoding/decoding in SIPThor backend * Don't allow relative URIs to link to another users' resource list entry * Check external references for pres-rules and resource-lists * Use a single appusage for pres-rules * Don't allow external-ref paths which don't point to an 'entry' * Check entry-ref entries in resource-lists * Added test case for testing If-None-Match * in PUT requests * Don't allow PUT for xcap-caps * Added XPath tests to the test suite * Raise DocumentSelectorError if selector doesn't start with slash * Use appusages 'id' attribute as the AUID * Fixed support for XCAP default document namespace * Generate NodeParsingError when specified namespace is not found * Merged xcap-directory application definition with other applications * Fixed directory application AUID * Updated sample OpenSIPS mysql dburi To update your installation see: http://www.openxcap.org/wiki/Installation Regards, Adrian ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
