RFC 3921:Extensible Messaging and Presence Protoco...
RFC-Ref

XML character data


Click on the red underlined text to get to the source

... subject/> element contains human-readable XML character data that specifies the topic of the message. The <subject/> element ...
... The <body/> element contains human-readable XML character data that specifies the textual contents of the message; this child element is ...
... The <thread/> element contains non-human-readable XML character data specifying an identifier that is used for tracking a conversation ...
... The OPTIONAL <show/> element contains non-human-readable XML character data that specifies the particular availability status of an entity or specific resource. A presence stanza ...
... element. The <show/> element MUST NOT possess any attributes. If provided, the XML character data value MUST be one of the following (additional availability types could be defined through a properly-namespaced child element ...
... The OPTIONAL <status/> element contains XML character data specifying a natural-language description of availability status. It is ...
... priority/> element contains non-human-readable XML character data that specifies the priority level of the resource. The value MUST be an integer ...


... stanza MAY (and often will) contain a child <body/> element whose XML character data specifies the primary meaning of the message (see Body (Section 2.1.2.2)). ...


... elements, for use in collecting roster items into various categories. The XML character data of the <group/> element is opaque ...



Google
Web
RFC-Ref