namespace
Click on the red underlined text to get to the source
... real-time applications, which may be layered on top of the core
by sending application-specific data qualified by particular XML
namespaces [XML-NAMES]. This memo describes extensions to and
applications of the core features of XMPP ...
... jabber:client' and 'jabber:server' namespaces are defined in
[XMPP-CORE]. However, these namespaces ...
... namespaces are defined in
[XMPP-CORE]. However, these namespaces also define various child
elements, as well as values for the common 'type' attribute, that are
...
... client' or 'jabber:server'
namespace are used to "push" information to another entity. Common
uses in instant messaging ...
...
As described under extended namespaces (Section 2.4), a message
stanza MAY contain any properly-namespaced child element ...
... element.
In accordance with the default namespace declaration, by default a
message stanza is qualified by the 'jabber ...
... client' or 'jabber:server'
namespace, which defines certain allowable children of message
stanzas. If the message stanza ...
... stanza MAY contain any of the following child elements
without an explicit namespace declaration:
1. <subject ...
...
As described under extended namespaces (Section 2.4), a presence
stanza MAY contain any properly-namespaced child element.
...
... element.
In accordance with the default namespace declaration, by default a
presence stanza is qualified by the 'jabber ...
... client' or
'jabber:server' namespace, which defines certain allowable children
of presence stanzas. If the presence stanza ...
... semantics
required to complete particular use cases are defined in all cases by
an extended namespace (Section 2.4) (note that the 'jabber:client'
...
... client'
and 'jabber:server' namespaces do not define any children of IQ
stanzas other than the common <error/>). This memo defines two such
extended namespaces ...
... namespaces do not define any children of IQ
stanzas other than the common <error/>). This memo defines two such
extended namespaces, one for Roster Management (Section 7) and the
other for Blocking Communication ...
... Extended Namespaces ...
... client" or
"jabber:server" namespace (along with their attributes and child
elements) provide a basic level of functionality for messaging and
...
... elements) provide a basic level of functionality for messaging and
presence, XMPP uses XML namespaces to extend the stanzas for the
purpose of providing additional functionality. Thus a message or
...
... element MAY have any name
and MUST possess an 'xmlns' namespace declaration (other than
"jabber:client ...
... element.
Support for any given extended namespace is OPTIONAL on the part of
any implementation (aside from the extended namespaces defined
...
... Support for any given extended namespace is OPTIONAL on the part of
any implementation (aside from the extended namespaces defined
herein). If an entity does not understand such a namespace ...
... namespaces defined
herein). If an entity does not understand such a namespace, the
entity's expected behavior depends on whether the entity ...
... presence stanza that
contains XML data qualified by a namespace it does not
understand, the portion of the stanza that is in the unknown
...
... understand, the portion of the stanza that is in the unknown
namespace SHOULD be ignored.
* If an entity ...
... stanza whose only child element
is qualified by a namespace it does not understand, it MUST
ignore the entire stanza.
...
... stanza of type "get" or "set"
containing a child element qualified by a namespace it does not
understand, the entity SHOULD return an IQ stanza ...
... element
qualified by the 'urn:ietf:params:xml:ns:xmpp-session' namespace in
the stream features it advertises to a client ...
... element
qualified by the 'urn:ietf:params:xml:ns:xmpp-session' namespace:
Step 1: Client requests ...
... 'jabber:iq:register' namespace; the latter method is out of scope for
this memo, but is documented in [JEP-0077 ...
... element qualified by
the 'jabber:iq:roster' namespace, which in turn contains an
<item/> element that defines the new roster item ...
... element qualified by the 'jabber:iq:privacy' namespace that
contains an empty <active/> child element ...
... 'jabber:iq:privacy' namespace that contains an empty <default/> child
element possessing a 'name' attribute whose value is set to the
...
... 'jabber:iq:privacy' namespace that contains one <list/> child element
possessing a 'name' attribute whose value is set to the list name the
...
... 'jabber:iq:privacy' namespace that contains one empty <list/> child
element possessing a 'name' attribute whose value is set to the list
...
... error code sent from a client that does not understand the
namespace of an IQ get or set. IQ stanzas of other types SHOULD be
...
... 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
reply to the stanza ...
... IQ error. Specifically,
if the semantics of the qualifying namespace define a reply
that the server can provide, the server MUST reply to the
stanza ...
... well-known dictionary attacks, since this is the same error
condition that is returned if, for instance, the namespace of an
IQ child element is not understood, or if offline message storage
...
... XML Namespace Name for Session Data ...
...
A URN sub-namespace for session-related data in the Extensible
Messaging and Presence Protocol (XMPP ...
... Extensible
Messaging and Presence Protocol (XMPP) is defined as follows. (This
namespace name adheres to the format defined in The IETF XML Registry ...
... Specification: RFC 3921prop
Description: This is the XML namespace name for session-related data
in the Extensible Messaging and Presence Protocol ...
... Bray, T., Hollander, D., and A. Layman, "Namespaces in XML", W3C REC-xml-names, January 1999, <http://www.w3.org/TR/REC-xml-names>. ...
... elementFormDefault='qualified'>
<xs:import namespace='urn:ietf:params:xml:ns:xmpp-stanzas'/>
...
... element ref='thread'/>
</xs:choice>
<xs:any namespace='##other'
minOccurs='0'
maxOccurs='unbounded'/>
...
... elementFormDefault='qualified'>
<xs:import namespace='urn:ietf:params:xml:ns:xmpp-stanzas'/>
...
... element ref='thread'/>
</xs:choice>
<xs:any namespace='##other'
minOccurs='0'
maxOccurs='unbounded'/>
...