A container for special metadata that may be difficult or impossible to reliably determine from the message's actual data content. This provides a mechanism for clearly signalling conditions that may have salient processing consequences. A choke operation is defined as an interaction between a data node and an authenticated user. No other information should be required at the operational level. Includes the request parameters in a Service Response type. The "recordCount" attribute value is not defined and should be set to some kind of reasonable default in concrete subtypes. Indicates that the choke operation completed correctly The "recordCount" attribute value should be set to zero as a default. this named element contains an XML node that is being evaluated for restriction. No attempt is made to restrict the content of that node. This Type provides a way to enumerate the rules used in processing a choke. All rules are identified by WIJIS URIs. This is an enumerated type whose values are all WIJIS URIs. An affirmative directive to provide the content to the user. A directive to omit the content from the material provided to the user, AND to hide the fact of the content's existence. In a Document-level Node, this would mean to act as though the Dcoument did not exist; For a child Node, this would mean to omit the Node from the returned content. A directive to omit the content from the material provided to the user, BUT to admit the fact of the content's existence. In a Document-level Node, this would mean to return a message stating that the Document has been withheld; For a child Node, this would mean to omit the Node's content, and to annotate it as being "redacted". A directive to deny all knowledge of content unless/until an authorized human being signs off on it. If there is no mechanism for delayed delivery, this would mean to treat the outcome as a "Deny/" result. If there is a mechanism for delayed delivery, the information (as otherwise modified by the choke process) should be forwarded to said authorized human being; if the human's decision is to grant the information, the content should be provided to the user in a "push" transaction. A directive to admit existence of content, but not the content itself, unless/until an authorized human being signs off on disclosure of the content as well. If there is no mechanism for delayed delivery, this would mean to treat the outcome as a "Withhold/" result. If there is a mechanism for delayed delivery, the information can be treated in two ways: 1.) the choke information should be forwarded to said authorized human being; if the human's decision is to grant the information, the content should be provided to the user in a "push" transaction. 2.) the content should be provided to the user with all instances of withheld content clearly identified, and a contact channel for the authorized human. This would permit the user to elect to petition the authorized human for release of the information. Either of the two alternatives would be a correct implementation; however, it's important to ensure that the user is aware of the operational context, in order to evaluate any information received.