moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-28 04:02:20 -05:00
Code Issues Releases Wiki Activity

xhtml fixes

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@588 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-02-16 00:05:31 +00:00
parent 68c13efb9c
commit bdf56193ba
2 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0025.xml
View File

@ -141,13 +141,12 @@
the identifier. The server must always return a 200 response code, the identifier. The server must always return a 200 response code,
sending any session errors as specially-formatted identifiers. sending any session errors as specially-formatted identifiers.
</p> </p>
<p> <p>The client sends requests with bodies in the following format:</p>
The client sends requests with bodies in the following format:
<example caption="Request Format"> <example caption="Request Format">
identifier ; key [ ; new_key] , [xml_body] identifier ; key [ ; new_key] , [xml_body]
</example> </example>
If the identifier is zero, key indicates an initial key. In this case, <p>If the identifier is zero, key indicates an initial key. In this case,
new_key should not be specified, and must be ignored. new_key should not be specified, and must be ignored.</p>
<table caption="Request Values"> <table caption="Request Values">
<tr> <tr>
<th>Identifier</th> <th>Identifier</th>
@ -264,8 +263,7 @@
</p> </p>
</section1> </section1>
<section1 topic="Usage"> <section1 topic="Usage">
<p> <p>The following is the sequence used for client communication:</p>
The following is the sequence used for client communication
<ol> <ol>
<li> <li>
The client generates some initial K(0, seed) and runs the algorithm The client generates some initial K(0, seed) and runs the algorithm

2
xep-0029.xml
View File

@ -62,7 +62,6 @@
</ol> </ol>
<p>JIDs are encoded UTF-8. A grammar will be presented first, followed by specific clarifying and further restricting remarks.</p> <p>JIDs are encoded UTF-8. A grammar will be presented first, followed by specific clarifying and further restricting remarks.</p>
<section2 topic='Grammar'> <section2 topic='Grammar'>
<p>
<code> <code>
&lt;JID&gt; ::= [&lt;node&gt;"@"]&lt;domain&gt;["/"&lt;resource&gt;] &lt;JID&gt; ::= [&lt;node&gt;"@"]&lt;domain&gt;["/"&lt;resource&gt;]
&lt;node&gt; ::= &lt;conforming-char&gt;[&lt;conforming-char&gt;]* &lt;node&gt; ::= &lt;conforming-char&gt;[&lt;conforming-char&gt;]*
@ -78,7 +77,6 @@
&lt;any-char&gt; ::= [#x20-#xD7FF] | [#xE000-#xFFFD] | &lt;any-char&gt; ::= [#x20-#xD7FF] | [#xE000-#xFFFD] |
[#x10000-#x10FFFF] [#x10000-#x10FFFF]
</code> </code>
</p>
</section2> </section2>
<section2 topic='Domain Identifier'> <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> <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>