OK: the response was returned successfully. Not Found: The targeted resource was not found. Warning: A response returned but may be incomplete No Access: no access to the targeted resource(s) Service Stopped: service is (temporarily) unavailable Error: some sort of failure Requests have this as the base type. Responses have this as the base type. If the request had an id attribute its value will be set as the response id attribute value. Fetch the XRD object for the targeted resource. The target may be the system itself ("/"), a principal, a collection resource or an entity. Respond to the get-properties request Type returned in an XRD object to define the allowable component types within a collection or supported by the system. Request a freebusy report on the targeted principal. This is a scheduling freebusy request which incorporates information such as availability etc. As such the response may depend on information not visible to the caller. Respond to the freebusy request. Returned icalendar data will be an icalendar entity containing a vfreebusy object. Note that the time period returned may not be as requested. The server is at liberty to extend or truncate the period. Used in a calendar query to specify that all properties be returned. What "all" really means is defined in the specification. Calendar data returned as response. Depending on the requested format it will be returned as a string value or an icalendar element prop element type in propstat Contains prop elements with the same status One part of a Multistatus Contains multiple MultistatResponseElementType Base type for query or multiget. Message to query a calendar. Response to a calendar query or multiget. Message to fetch multiple calendar entities. Message to create a calendar item. Response to message to add an item. Message to fetch a calendar item. Response to message to fetch an item. Message to delete a calendar item. Response to message to delete an item. Used to contain updates to components. These updates are: zero or more of selections of sub-components to update zero or more additions or removals of components Removals MUST be processed ahead of additions. Used to contain a selection of a single component. There are no changes that can be applied directly to components. They are containers for properties or other components. Used to contain a new value. Used to contain updates to properties. These updates are either a selection of a property to apply a change and/or to update the parameters or addition or removal of properties. Removals MUST be processed ahead of additions. Used to contain a selection of a single property. This selection can be to apply a value change and/or to update the parameters. Used to contain a new value for change, a new property for add or identify the property for remove. Used to contain updates to parameters. These updates are either a selection of a parameter to apply a change or addition or removal of parameters. Removals MUST be processed ahead of additions. Used to contain a selection of a single parameter. This selection is only to apply a value change. Used to contain a new value. Message to update a calendar item. The supplied etoken MUST match the etoken held by the service. Response to message to update an item. The server will return an etoken value which should replace the value currently held by the client. A structure containing all the operations allowed within a MultiOpType This type is a wrapper around a number of sub-operations allowing complex structures to be updated in a single, atomic operation. Each sub-operation is one of the other possible operations, e.g. updateItem, deleteItem etc. Inclusion of a multiOp is disallowed. The response is a MultiOpResponseType which wraps one response per sub-operation. It will terminate on the first failure and all updates to that point rolled back. Inclusion of an id attribute in the sub-operation request will aid in associating responses with requests. A structure containing all the responses from a MultiOpType operation Response to a multi-op message. This is a sequence of responses to each operation. The multi-op operation itself has a status which is almost always success. Each embedded response needs to be examined to determine if it succeeded or failed.