Jabber
Click on the red underlined text to get to the source
... specification in mind, since the base protocol evolved through an
open development process within the Jabber open-source community
before RFC 2779 ...
... addressing many other functionality areas have been defined in the
Jabber community, such protocols are not included in this memo
because they are not required by [IMP-REQS].
...
... semantics and common attributes of XML stanzas qualified by
the 'jabber:client' and 'jabber:server' namespaces ...
... stanzas qualified by the 'jabber:client' or 'jabber:server'
namespace are used to "push" information to another entity ...
... namespace declaration, by default a
message stanza is qualified by the 'jabber:client' or 'jabber:server'
...
... stanza is qualified by the 'jabber:client' or 'jabber:server'
namespace, which defines certain allowable children of message
...
... namespace declaration, by default a
presence stanza is qualified by the 'jabber:client' or
'jabber ...
... jabber:client' or
'jabber:server' namespace, which defines certain allowable children
of presence stanzas ...
... required to complete particular use cases are defined in all cases by
an extended namespace (Section 2.4) (note that the 'jabber:client'
and 'jabber ...
... jabber:client'
and 'jabber:server' namespaces do not define any children of IQ
stanzas other than the common <error/>). This memo defines two such
...
... "jabber:client", "jabber:server", or
"http://etherx.jabber.org/streams") that defines all data contained
...
... client", "jabber:server", or
"http://etherx.jabber.org/streams") that defines all data contained
within the child element.
...
... method is out of scope for
this memo, but is documented in [JEP-0077], published by the Jabber
Software Foundation [JSF].
...
... query/> element qualified by
the 'jabber:iq:roster' namespace, which in turn contains an
<item/> element ...
... If the type is "jid", then the 'value' attribute MUST contain a valid
Jabber ID. JIDs SHOULD be matched in the following order:
...
... query/> element qualified by the
'jabber:iq:privacy' namespace that contains an empty <default/> child
...
... query/> element qualified by the
'jabber:iq:privacy' namespace that contains one <list/> child element ...
... query/> element qualified by the
'jabber:iq:privacy' namespace that contains one empty <list/> child
...
... 2426prop [VCARD] is in common use
within the Jabber community to provide such information but is out of
scope for XMPP (documentation of this protocol is contained in
...
... XMPP (documentation of this protocol is contained in
[JEP-0054], published by the Jabber Software Foundation [JSF]).
...
... B.2 jabber:server ...
... B.5 jabber:iq:roster ...
... xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='jabber:iq:roster'
xmlns='jabber ...
... XMPP has been adapted from the protocols originally developed in the
Jabber open-source community, which can be thought of as "XMPP 0.9".
...
... open-source community, which can be thought of as "XMPP 0.9".
Because there exists a large installed base of Jabber implementations
and deployments, it may be helpful to specify the key differences
...
... and deployments, it may be helpful to specify the key differences
between the relevant Jabber protocols and XMPP in order to expedite
and encourage upgrades of those implementations and deployments ...
... The client-to-server authentication protocol developed in the Jabber
community assumed that every client is an IM client ...
... resource
binding, which are performed simultaneously (documentation of this
protocol is contained in [JEP-0078], published by the Jabber Software
Foundation [JSF]). XMPP maintains a stricter separation between core
...
...
The Jabber community began to define a protocol for communications
blocking (privacy lists) in late 2001, but that effort was deprecated
...
... defined under Blocking Communication (Section 10) is the only such
protocol defined for use in the Jabber community.
...
...
Most of the core aspects of the Extensible Messaging and Presence
Protocol were developed originally within the Jabber open-source
community in 1999. This community was founded by Jeremie Miller, who
released source code for the initial version ...
...
Peter Saint-Andre (editor)
Jabber Software Foundation
EMail ...