From 3cd61d738cce735d863c195e43bc7e41ca983896 Mon Sep 17 00:00:00 2001 From: Licaon_Kter Date: Thu, 9 Jan 2020 15:27:42 +0000 Subject: [PATCH 1/2] Fix typos in 379 --- xep-0379.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/xep-0379.xml b/xep-0379.xml index 4f919791..c71c25cb 100644 --- a/xep-0379.xml +++ b/xep-0379.xml @@ -71,10 +71,10 @@ register with some server. Now, Romeo only needs to create a mutual presence subscription with her, without yet knowing her JID.

This specification allows Romeo to create an out-of-band link (URI) which, - when opened in Juilet's (or another user's) client, will:

+ when opened in Juliet's (or another user's) client, will:

The perceivable effect is that with a single click, Romeo and Juliet @@ -93,7 +93,7 @@

  1. Generation of invitation link
  2. Out-of-band transmission and presentation of the link
  3. -
  4. Subcription request to the user by the link receiver (new contact)
  5. +
  6. Subscription request to the user by the link receiver (new contact)
  7. Approval by the user and mutual subscription request
  8. Approval by the new contact
@@ -281,7 +281,7 @@ https://juicyxmpp.example/i/#romeo@montague.net?roster;preauth=1tMFqYDdKhfe2pwp; as if no preauth token was contained.

- +

When sending a pre-authenticated subscription request, the contact's client MUST NOT expect an immediate successful approval. If the user's issuing client is currently offline, or if the token has expired, a manual @@ -359,8 +359,8 @@ https://juicyxmpp.example/i/#romeo@montague.net?roster;preauth=1tMFqYDdKhfe2pwp;

Some mobile device platforms allow an app to register itself as a - handler for cetain URIs. This allows an XMPP client to register for xmpp: - URIs, but also to redirect handling of cetain HTTP/HTTPS URIs. A mobile + handler for certain URIs. This allows an XMPP client to register for xmpp: + URIs, but also to redirect handling of certain HTTP/HTTPS URIs. A mobile client SHOULD register for the associated landing page URIs and properly handle the contained invitations. For example, the JuicyXMPP client should register a handler for https://juicyxmpp.example/i/*, and present @@ -375,7 +375,7 @@ https://juicyxmpp.example/i/#romeo@montague.net?roster;preauth=1tMFqYDdKhfe2pwp; SHOULD be indicated by the client UI to Romeo.

If a client allows customization of the validity time or the number of uses for a given invitation token, it SHOULD provide clear language - to inidcate that.

+ to indicate that.

When a new contact is added automatically by the client, it SHOULD From ebed16873001bcc509dba83cf18157bb65374a5c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Tue, 14 Jan 2020 18:44:42 +0100 Subject: [PATCH 2/2] XEP-0379: add revision block --- xep-0379.xml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/xep-0379.xml b/xep-0379.xml index c71c25cb..2f04f18b 100644 --- a/xep-0379.xml +++ b/xep-0379.xml @@ -28,6 +28,12 @@ georg@op-co.de georg@yax.im + + 0.3.2 + 2020-01-14 + licaon-kter + Fix a bunch of typos. + 0.3.1 2018-11-03