From 0f649efde07ffa07270bbd90d2bc98e1c7e55220 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 20 Oct 2008 22:20:45 +0000 Subject: [PATCH] PDF fixes git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2415 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0037.xml | 5 +++-- xep-0048.xml | 2 +- xep-0054.xml | 2 +- xep-0060.xml | 2 +- xep-0124.xml | 2 +- xep-0136.xml | 2 +- xep-0198.xml | 2 +- xep-0206.xml | 2 +- xep-0209.xml | 2 +- xep-0244.xml | 2 +- 10 files changed, 12 insertions(+), 11 deletions(-) diff --git a/xep-0037.xml b/xep-0037.xml index 3ca61f97..93db485b 100644 --- a/xep-0037.xml +++ b/xep-0037.xml @@ -1,8 +1,9 @@ - + + %ents; ]> +
DSPS - Data Stream Proxy Service diff --git a/xep-0048.xml b/xep-0048.xml index 69ad4d7b..fb2bfa3e 100644 --- a/xep-0048.xml +++ b/xep-0048.xml @@ -283,7 +283,7 @@

No action by the ®ISTRAR; is required, since the 'storage:bookmarks' namespace is already included in the protocol namespaces registry (see &NAMESPACES;).

- + diff --git a/xep-0054.xml b/xep-0054.xml index e7074dfc..d2b6ecf2 100644 --- a/xep-0054.xml +++ b/xep-0054.xml @@ -306,7 +306,7 @@ xmpp:romeo@montague.net?vcard ]]> - +

Note the following:

  • The correct capitalization of the wrapper element is <vCard/> (and XML element names are case-sensitive).
    • diff --git a/xep-0060.xml b/xep-0060.xml index 7fe05c66..14f8136a 100644 --- a/xep-0060.xml +++ b/xep-0060.xml @@ -4099,7 +4099,7 @@ And by opposing end them? ]]>

    The service MUST check the "pubsub#allow" field to see if the subscription should be allowed or denied. If the owner cancels the Data Form, then the subscription request MUST remain in the pending state.

    - +

    A node owner may want to request all of the pending subscription requests for all of their nodes at a service. It is OPTIONAL for a service to implement this feature.

    This feature MUST be implemented using the &xep0050; protocol, where the command name ('node' attribute of the command element) MUST have a value of "http://jabber.org/protocol/pubsub#get-pending".

    diff --git a/xep-0124.xml b/xep-0124.xml index df2642cd..21037e5a 100644 --- a/xep-0124.xml +++ b/xep-0124.xml @@ -387,7 +387,7 @@ Content-Length: 88 xmlns='http://jabber.org/protocol/httpbind'/>]]>

    The connection manager MUST wait and respond in the same way as it does after receiving stanzas from the client.

    - +

    When responding to a request that it has been holding, if the connection manager finds it has already received another request with a higher 'rid' attribute (typically while it was holding the first request), then it MAY acknowledge the reception to the client. The connection manager MAY set the 'ack' attribute of any response to the value of the highest 'rid' attribute it has received in the case where it has also received all requests with lower 'rid' values.

    diff --git a/xep-0136.xml b/xep-0136.xml index ff2b7dd1..7109e02c 100644 --- a/xep-0136.xml +++ b/xep-0136.xml @@ -233,7 +233,7 @@

    The <item/> element specifies the settings for both the OTR Mode and Save Mode with regard to a particular entity. The element MUST be empty and MUST include a 'jid' attribute, an 'otr' attribute, and a 'save' attribute. The element MAY include an 'expire' attribute.

    - +

    If the 'save' attribute is not set to 'false' then is RECOMMENDED to also include an 'expire' attribute, which indicates how many seconds after messages are archived that the server SHOULD delete them.

     diff --git a/xep-0198.xml b/xep-0198.xml index 26159e19..174ac74a 100644 --- a/xep-0198.xml +++ b/xep-0198.xml @@ -123,7 +123,7 @@ S: ]]> - +

    To enable use of stream management, the client sends an <enable/> command to the server. If it wants to be allowed to resume the stream, it includes a boolean 'resume' attribute, which defaults to false &BOOLEANNOTE;.

    diff --git a/xep-0206.xml b/xep-0206.xml index f1e641ab..40951dfa 100644 --- a/xep-0206.xml +++ b/xep-0206.xml @@ -306,7 +306,7 @@ Content-Length: 68 ]]>     - +

    It is possible that a connection manager will receive a stanza for delivery to a client even though the client connection is no longer active (e.g., before the connection manager is able to inform the XMPP server that the connection has died). In this case, the connection manager would return an error to the XMPP server; it is RECOMMENDED that the connection manager proceed as follows, since the situation is similar to that addressed by point #2 of Section 11.1 of RFC 3921:

    1. If the delivered stanza was &PRESENCE;, silently drop the stanza and do not return an error to the sender.
      2. diff --git a/xep-0209.xml b/xep-0209.xml index 34386cf8..3788a0e3 100644 --- a/xep-0209.xml +++ b/xep-0209.xml @@ -127,7 +127,7 @@ Similarly, to remove a metacontact all that is required is to remove the meta tags which contribute to the metacontact. - +

      Although it is unavoidable that multiple contacts within a metacontact MAY have the same order (due to potentially unavailable information from other accounts), clients SHOULD NOT apply the same order to multiple members of the same metacontact where it is possible to avoid it. If multiple members of a metacontact have the same order, the behaviour is dependent upon the client; it MAY apply rules itself to determine which member to communicate with (based upon presence, recent activity or other methods) it MAY present the user with the option to sort the members such that the orders are again unique, or it MAY employ another appropriate action.

      As the order attribute is optional, clients need a method for determining which member contact to use where the metacontact consists entirely of unordered members. When ordered and unordered members are present, unordered members SHOULD be considered to have the lowest order.

       diff --git a/xep-0244.xml b/xep-0244.xml index 41532a8d..7c3167ef 100644 --- a/xep-0244.xml +++ b/xep-0244.xml @@ -262,7 +262,7 @@ if (function instanceof IoDataFunction) {       - +

      <desc> -- a textual description of the IO Data data container (xs:string).

      <in> -- contains the input. Valid for Transaction Type 'input' and 'io-schemata-result' only. May contain any XML data (XML Schema, XML Document ...).

      <out> -- contains the output. Valid for Transaction Type 'output' and 'io-schemata-result' only. May contain any XML data (XML Schema, XML Document ...).