operation-data

<operation-data> is used to allow policies to inject an additional custom data payload to be carried along with any event or command. It is stripped off of the event or command before it is submitted to the application shim and then reassociated with any corresponding response elements (as determined by matching event-id) after they are returned to the DirXML (ie. an application shim shouldn't ever have to deal with it.)

The content of the <operation-data> can be any well formed XML but it is recommended that any elements and attributes used be placed in a custom namespace to avoid having them confused with standard DirXML operations.

The typical use for <operation-data> is to be able to create a policy that supplies additional context on an operation that may be needed by the policy that handles the results of that operation.

Note that for operations whose content is normally PCDATA there should only be at most one <operation-data> and it should be after any character data. This is contrary to the content rule specified by the DTD because DTD's for mixed content do not allow more precise specification.

Example

<operation-data xmlns:mystuff="http://mystuff.operation.data">
 <mystuff:notify>admin@fred.com</mystuff:notify>
</operation-data>