semantic
Click on the red underlined text to get to the source
... element MUST be treated
as opaque by entities; no semantic meaning may be derived from it,
and only exact comparisons may be made against it. The <thread/>
element ...
... presence stanza.
For detailed information regarding presence semantics and the
subscription model used in the context of XMPP ...
... a server SHOULD consider the priority to be zero. For information
regarding the semantics of priority values in stanza routing ...
... IQ stanzas provide a structured request-response mechanism. The
basic semantics of that mechanism (e.g., that the 'id' attribute is
REQUIRED) are defined in [XMPP-CORE], whereas the specific semantics ...
... semantics of that mechanism (e.g., that the 'id' attribute is
REQUIRED) are defined in [XMPP-CORE], whereas the specific semantics
required to complete particular use cases are defined in all cases by
an extended namespace ...
... Syntax and Semantics ...
... <iq to='juliet@example.com/balcony' type='result' id='roster_2'/>
As required by the semantics of the IQ stanza kind as defined in
[XMPP-CORE ...
... stanzas are
not shown in the following examples but are required by the IQ
semantics defined in [XMPP-CORE]).
...
... Syntax and Semantics ...
...
If the type is "subscription", then the 'value' attribute MUST be one
of "both", "to", "from", or "none" as defined under Roster Syntax and
Semantics (Section 7.1), where "none" includes entities that are
totally unknown to the user and therefore not in the user's roster at
all.
...
... privacy list.
These "privacy list pushes" adhere to the same semantics as the
"roster pushes" used in roster management, except that only the
...
... deliver the IQ stanza to any of the available resources.
Specifically, if the semantics of the qualifying namespace
define a reply that the server can provide, the server MUST
...
... IQ result or an IQ error. Specifically,
if the semantics of the qualifying namespace define a reply
that the server can provide, the server MUST reply to the
...
...
o All server-related instant messaging and presence syntax and
semantics defined in this document, including presence broadcast
on behalf of clients ...
...
o Generation and handling of the IM-specific semantics of XML
stanzas as defined by the XML schemas, including the 'type'
...
... o All client-related instant messaging syntax and semantics defined
in this document, including presence subscriptions, roster
management ...