This chapter describes Oracle Communications Evolved Communications Application Server's compliance with the IETF RFC 4825 document.
Table 5-1 represents the Protocol Implementation Conformance Statement (PICS) for OCECAS with respect to the IETF document RFC 4825, "Extensible Markup Language (XML) Configuration Access Protocol (XCAP)."
| Section Number | Section Title | Product Release | Release caveats |
|---|---|---|---|
|
1 |
Introduction |
7.1.0 |
NA |
|
2 |
Overview of Operation |
7.1.0 |
NA |
|
3 |
Terminology |
7.1.0 |
NA |
|
4 |
Definitions |
7.1.0 Partial |
Compliant, except for Capability support |
|
5 |
Application Usages |
7.1.0 |
NA |
|
5.1 |
Application Unique ID (AUID) |
7.1.0 |
NA |
|
5.2 |
Default Document Namespace |
7.1.0 |
NA |
|
5.3 |
Data Validation |
7.1.0 |
NA |
|
5.4 |
Data Semantics |
7.1.0 |
NA |
|
5.5 |
Naming Conventions |
7.1.0 |
NA |
|
5.6 |
Resource Interdependencies |
7.1.0 |
NA |
|
5.7 |
Authorization Policies |
7.1.0 |
NA |
|
5.8 |
Data Extensibility |
7.1.0 |
NA |
|
5.9 |
Documenting Application Usages |
7.1.0 |
NA |
|
5.10 |
Guidelines for Creating Application Usages |
7.1.0 |
NA |
|
6 |
URI Construction |
7.1.0 |
NA |
|
6.1 |
XCAP Root |
7.1.0 |
NA |
|
6.2 |
Document Selector |
7.1.0 |
NA |
|
6.3 |
Node Selector |
7.1.0 Partial |
Compliant, with the following two exceptions. If the node selector matches multiple elements, all elements are updated - provided a valid schema results. Additional whitespace is not preserved in the ECAS configuration. |
|
6.4 |
Namespace Bindings for the Selector |
7.1.0 |
NA |
|
7 |
Client Operations |
7.1.0 Partial |
Compliant, except that idempotency of operations is not enforced by ECAS. |
|
7.1 |
Create or Replace a Document |
7.1.0 |
NA |
|
7.2 |
Delete a Document |
7.1.0 |
NA |
|
7.3 |
Fetch a Document |
7.1.0 |
NA |
|
7.4 |
Create or Replace an Element |
7.1.0 Partial |
Compliant, except that idemptotency is not enforced. |
|
7.5 |
Delete an Element |
7.1.0 Partial |
Compliant, except that idemptotency is not enforced. |
|
7.6 |
Fetch an Element |
7.1.0 |
Note that needed namespace declarations from parent elements are included |
|
7.7 |
Create or Replace an Attribute |
7.1.0 |
Compliant, except that idemptotency is not enforced. |
|
7.8 |
Delete an Attribute |
7.1.0 |
NA |
|
7.9 |
Fetch an Attribute |
7.1.0 |
NA |
|
7.10 |
Fetch Namespace Bindings |
7.1.0 |
NA |
|
7.11 |
Conditional Operations |
7.1.0 |
NA |
|
8 |
Server Behavior |
7.1.0 |
NA |
|
8.1 |
POST Handling |
7.1.0 |
NA |
|
8.2 |
PUT Handling |
7.1.0 |
NA |
|
8.2.1 |
Locating the Parent |
7.1.0 |
NA |
|
8.2.2 |
Verifying Document Content |
7.1.0 |
NA |
|
8.2.3 |
Creation |
7.1.0 Partial |
Compliant, with the following exceptions. Positional selection is supported, however insertion may not be at the exact position specified. This also affects idempotency. Redundant namespace declarations may be removed. |
|
8.2.4 |
Replacement |
7.1.0 Partial |
Compliant, except that idemptotency is not enforced. |
|
8.2.5 |
Validation |
7.1.0 |
NA |
|
8.2.6 |
Conditional Processing |
7.1.0 |
NA |
|
8.2.7 |
Resource Interdependencies |
7.1.0 |
NA |
|
8.3 |
GET Handling |
7.1.0 Partial |
Compliant, except that the return content is well-formed XML - so _will_ have any necessary namespace bindings declared in ancestor elements. |
|
8.4 |
DELETE Handling |
7.1.0 Partial |
Compliant, except that idemptotency is not enforced. |
|
8.5 |
Managing Etags |
7.1.0 |
NA |
|
9 |
Cache Control |
7.1.0 |
NA |
|
10 |
Namespace Binding Format |
7.1.0 |
NA |
|
11 |
Detailed Conflict Reports |
7.1.0 |
NA |
|
11.1 |
Document Structure |
7.1.0 |
NA |
|
11.2 |
XML Schema |
7.1.0 |
NA |
|
12 |
XCAP Server Capabilities |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.1 |
Application Unique ID (AUI) |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.2 |
XML Schema |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.3 |
Default Document Namespace |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.4 |
MIME Type |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.5 |
Validation Constraints |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.6 |
Data Semantics |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.7 |
Naming Conventions |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.8 |
Resource Interdependencies |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
12.9 |
Authorization Policies |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
13 |
Examples |
7.1.0 |
NA |
|
14 |
Security Considerations |
7.1.0 |
NA |
|
15 |
IANA Considerations |
7.1.0 |
NA |
|
15.1 |
XCAP Application Unique IDs |
7.1.0 |
NA |
|
15.2 |
MIME Types |
Non-Compliant |
Not relevant for XCAP |
|
15.2.1 |
application/xcap-el+xml MIME Type |
||
|
15.2.2 |
application/xcap-att+xml MIME Type |
||
|
15.2.3 |
application/xcap-ns+xml MIME Type |
||
|
15.2.4 |
application/xcap-error+xml MIME Type |
||
|
15.2.5 |
application/xcap-caps+xml MIME Type |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
15.3 |
URN Sub-Namespace Registrations |
7.1.0 |
NA |
|
15.3.1 |
urn:ietf:params:xml:ns:xcap-error |
7.1.0 |
NA |
|
15.3.2 |
urn:ietf:params:xml:ns:xcap-caps |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
15.4 |
XML Schema Registrations |
7.1.0 |
NA |
|
15.4.1 |
XCAP Error Schema Registration |
7.1.0 |
NA |
|
15.4.2 |
XCAP Capabilities Schema Registration |
Non-Compliant |
XCAP Server Capabilities is not supported. |
|
16 |
Acknowledgements |
7.1.0 |
Noted |
|
17 |
References |
7.1.0 |
Noted |
|
17.1 |
INormative References |
7.1.0 |
Noted |
|
17.2 |
Informative References |
7.1.0 |
Noted |