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

subject


Click on the red underlined text to get to the source

... namespace declaration: 1. <subject/> 2. <body/> 3. <thread/> ...
... Subject ...
... The <subject/> element contains human-readable XML character data ...
... human-readable XML character data that specifies the topic of the message. The <subject/> element MUST NOT possess any attributes, with the exception of the 'xml:lang ...
... NOT possess any attributes, with the exception of the 'xml:lang' attribute. Multiple instances of the <subject/> element MAY be included for the purpose of providing alternate versions ...
... versions of the same subject, but only if each instance possesses an 'xml:lang' attribute with a distinct language ...
... xml:lang' attribute with a distinct language value. The <subject/> element MUST NOT contain mixed content (as defined in Section 3.2.2 of [XML ...


... Specifying a Message Subject ...
... A message stanza MAY contain one or more child <subject/> elements specifying the topic of the message (see Subject ...
... subject/> elements specifying the topic of the message (see Subject (Section 2.1.2.1)). Example: A message with a subject ...
... Subject (Section 2.1.2.1)). Example: A message with a subject: <message ...
... xml:lang='en'> <subject>I implore you!</subject> <subject ...
... xml:lang='en'> <subject>I implore you!</subject> <subject ...
... subject>I implore you!</subject> <subject xml:lang='cz'>&#x00DA;p&#x011B;nliv&#x011B; prosim!</subject ...
... subject xml:lang='cz'>&#x00DA;p&#x011B;nliv&#x011B; prosim!</subject> <body>Wherefore art thou, Romeo?</body> <body xml:lang ...


... received by the server from each of the contact's available resources (again, subject to privacy lists in force for each session ...
... full XML of that presence stanza (subject to privacy lists) but SHOULD NOT otherwise modify the contact's status regarding ...


... subscription request is delivered, the contact must decide whether or not to approve it (subject to the contact's configured preferences, the contact's client MAY approve or refuse the subscription request ...
... create a mutual subscription, the contact MUST send a subscription request to the user (subject to the contact's configured preferences, the contact's client MAY send ...
... matter when the subscription request is delivered, the user must then decide whether or not to approve it (subject to the user's configured preferences, the user's client MAY approve or refuse ...
... last presence stanza with no 'to' attribute received by the server from each of the user's available resources (subject to privacy lists in force for each session ...


... <xs:choice minOccurs='0' maxOccurs='unbounded'> <xs:element ref='subject'/> <xs:element ref='body'/> ...
... <xs:element name='subject'> <xs:complexType> <xs:simpleContent> ...
... <xs:choice minOccurs='0' maxOccurs='unbounded'> <xs:element ref='subject'/> <xs:element ref='body'/> ...
... <xs:element name='subject'> <xs:complexType> <xs:simpleContent> ...


... Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors ...



Google
Web
RFC-Ref