2.2.7.1.4 body Element

The body XML element specifies a string using attributes or nested text, optionally combined with nested parameter elements that SHOULD be used by the AsyncUI client as the displayable description of a printer event.

If any of the strings specified by attributes or nested text contains position parameter replacement tags, the client MUST replace the parameters with strings that are constructed from the sequence of parameter elements.

If a single notification contains multiple body elements, the client MUST concatenate the text resulting from the processing of each successive body element to determine the complete displayable description. The client SHOULD interpose a single space character between each pair of concatenated strings.

 <xs:element name="body">
   <xs:complexType
     mixed="true"
   >
     <xs:sequence>
       <xs:element
         minOccurs="0"
         maxOccurs="unbounded"
         ref="parameter"
        />
     </xs:sequence>
     <xs:attribute name="stringID"
       type="xs:integer"
       use="optional"
      />
     <xs:attribute name="resourceDll"
       type="xs:string"
       use="optional"
      />
   </xs:complexType>
 </xs:element>

Child Elements

Element	Type	Description
parameter	parameter	See section 2.2.7.1.5.

Attributes

Name	Type	Description
stringID	xs:integer	The value of this optional attribute, if present, is the key of a string resource in the resource file specified by the resourceDll attribute. If the resourceDll attribute is not specified, stringID MUST be used as the key of a string resource in the default resource file. String resources that are present in the default resource file are specified in section 2.2.6.
resourceDll	xs:string	The value of this optional attribute, if present, is the driver-file name of a resource file on the client system that contains the string resources used in this message. If no value is specified, a default resource file MUST be used.

If the stringID attribute is not specified, the text content in the body element MUST be present, and it MUST be used by the client as the string to display.

If the stringID attribute is specified, then the body element MUST NOT contain nested text and the client MUST treat the presence of such text as an error.

Nested text MUST NOT follow a parameter element.