The WIJIS URI Schema. A collection management directive. This attribute, if present and true in the root of the invocation message, requires the deletion, *before any other processing takes place*,of all existing elements in the collection that fall within a defined "domain". (this is a well-understood strategy for collection management.) The domain must be defined in the particular service definition. A service execution directive. This attribute, if present and true in the root of the invocation message, requires that all operations be treated transactionally (including a "deleteAllPrevious" directive if present.) It is senseless, and a design error, to set this attribute if any of the Service invocation consequences cannot be rolled back. The general form for a service invocation response. The general form for a response when a service was fulfilled according to the contract. The general form for a response when a service experienced errors that prevented a fulfillment of the service contract. The general form for a response when a collection-management service fulfilled the terms of its service contract. The general form for a response when a collection-management service experienced errors that prevented a fulfillment of the service contract. A collection of Informational Items pertaining to the satisfaction or processing of a Service request. The "submitterURI" attribute is available because it can establish a "default Submitter" context for any contained Info Items that are linked to specific Records. A collection of informational Items (whether Error or Info) pertaining to the satisfaction or processing or failure of a Service request. The "submitterrURI" attribute is available because it can establish a "default Submitter" context for any contained Error or Info Items that are linked to specific Records. Not consequential, but bears investigation: something's not right. Never sufficient to cause a transaction to be rolled back. A consequential error, affecting processing outcome; sufficient to cause a transaction to be rolled back, but not to halt non-transactional processing. A production problem of sufficient gravity to halt non-transactional (as well as transactional) processing. An assertion that a service fulfilled its service contract without consequential error. ("consequential error" means an error that affects the contractually specified outcome. An example of a non-consequential error would be a network outage that was eventually overcome via normal retry behavior, thus permitting processing to continue.) An assertion that a service encountered consequential error while attempting to fulfill its contract. A count of records directly involved in a Service request or response. In a confirmation, it could serve as "Records Affected"; in a query about a record count, it could serve as the actual content of the response; in a message containing multiple records, it can act as useful metadata for the benefit of processing entities; in an error message, it might be used to describe the number of records that didn't properly execute (or alternatively, how many *did*.) It's essential that every usage of the "recordsAffected" attribute be documented in the Service contract if there's any potential ambiguity as to its particular meaning in the case.