mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-24 02:02:16 -05:00
xhtml fixes
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@588 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
68c13efb9c
commit
bdf56193ba
10
xep-0025.xml
10
xep-0025.xml
@ -141,13 +141,12 @@
|
||||
the identifier. The server must always return a 200 response code,
|
||||
sending any session errors as specially-formatted identifiers.
|
||||
</p>
|
||||
<p>
|
||||
The client sends requests with bodies in the following format:
|
||||
<p>The client sends requests with bodies in the following format:</p>
|
||||
<example caption="Request Format">
|
||||
identifier ; key [ ; new_key] , [xml_body]
|
||||
</example>
|
||||
If the identifier is zero, key indicates an initial key. In this case,
|
||||
new_key should not be specified, and must be ignored.
|
||||
<p>If the identifier is zero, key indicates an initial key. In this case,
|
||||
new_key should not be specified, and must be ignored.</p>
|
||||
<table caption="Request Values">
|
||||
<tr>
|
||||
<th>Identifier</th>
|
||||
@ -264,8 +263,7 @@
|
||||
</p>
|
||||
</section1>
|
||||
<section1 topic="Usage">
|
||||
<p>
|
||||
The following is the sequence used for client communication
|
||||
<p>The following is the sequence used for client communication:</p>
|
||||
<ol>
|
||||
<li>
|
||||
The client generates some initial K(0, seed) and runs the algorithm
|
||||
|
@ -62,7 +62,6 @@
|
||||
</ol>
|
||||
<p>JIDs are encoded UTF-8. A grammar will be presented first, followed by specific clarifying and further restricting remarks.</p>
|
||||
<section2 topic='Grammar'>
|
||||
<p>
|
||||
<code>
|
||||
<JID> ::= [<node>"@"]<domain>["/"<resource>]
|
||||
<node> ::= <conforming-char>[<conforming-char>]*
|
||||
@ -78,7 +77,6 @@
|
||||
<any-char> ::= [#x20-#xD7FF] | [#xE000-#xFFFD] |
|
||||
[#x10000-#x10FFFF]
|
||||
</code>
|
||||
</p>
|
||||
</section2>
|
||||
<section2 topic='Domain Identifier'>
|
||||
<p>A domain identifier is a standard DNS hostname as specified in RFC952 <note><link url='http://www.ietf.org/rfc/rfc952.txt'>http://www.ietf.org/rfc/rfc952.txt</link></note> and RFC1123. <note><link url='http://www.ietf.org/rfc/rfc1123.txt'>http://www.ietf.org/rfc/rfc1123.txt</link></note> It is case-insensitive 7-bit ASCII and limited to 255 bytes. It is the only required component of a JID.</p>
|
||||
|
Loading…
Reference in New Issue
Block a user