Section 7.1.3 - This version of standards is not ready for any type adoption or implementation due to lack of Access control, provisioning, retrivals, insertions, deletion, GET and allocation or clarification of services.

This specification is an information model, not an application profile. Added language to specifically dicuss this, and to make it more difficult to mis-apply parts of this specification as a completed transaction model. 2.4 Security Considerations Section 1 describes an information model. The information models can be expressed in any interaction, using any protocol. There are no security aspects of the information model. Section 2 defines RESTful interactions for exchanging WS-Calendar conformant information elements with calendar stores. While this specification is informed by the operations defined in CalDAV [RFC4791] , it is not built on, nor does it use CalDAV. REST interactions have their own security approaches which are not redefined herein. Section 3 defines SOAP operations for exchanging WS-Calendar conformant information elements with calendar stores. SOAP communications offer a palette of security techniques and technologies; none of them are prescribed or proscribed herein. Specifications which claim conformance with WS-Calendar may wish to specify security approaches or techniques. Security choices must be based on the business requirements and operational risks of the interaction that those specifications define. As this specification defines a general information model, for use in many interactions, it specifies no security approach.