|
Size: 3053
Comment: Describe gateway JID resolution and UX considerations
|
Size: 1029
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #format wiki | Hello, |
| Line 3: | Line 3: |
| This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways. | I trust this message finds you well. My name is Allen Scofield, and I am the owner of Allen Scofield Medical Equipment located at 3675 W Ninigret Dr, Salt Lake City, UT 84104, USA. |
| Line 5: | Line 5: |
| In every place where the UI would ask for a Jabber ID (most notably contact add, but possibly also invite to chatroom, create chatroom from 1:1 conversation, start voice/video call to non-contact, search view where a Jabber ID can be used, etc) it should scan the user's roster for JIDs which have `disco#info > identity[category=gateway]` and show some way of choosing to enter an identifier for that gateway instead of a Jabber ID. The simplest example might be a drop-down with `disco#info > identity[type]` and optional disambiguating `disco#info > idenity[name]` such as "sms (Cheogram)". | After careful consideration, I am interested in retaining your esteemed firm to handle legal matters pertaining to business and commercial law on behalf of Allen Scofield Medical Equipment. |
| Line 7: | Line 7: |
| If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt: | I believe that your expertise aligns with the specific legal needs that my business requires. |
| Line 9: | Line 9: |
| {{{ <iq type='get' to='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'/> </iq> |
To discuss this further and explore the possibility of engaging your services, I kindly request that you contact me via email at allen.scofield@executivesemail.online at your earliest convenience. |
| Line 14: | Line 11: |
| <iq type='result' from='gateway.tld' id='gate1'> <query xmlns='jabber:iq:gateway'> <desc> Please enter the Whatever of the person you would like to contact. </desc> <prompt>Whatever</prompt> </query> </iq> }}} |
I am eager to delve into the details of our potential collaboration and address any inquiries you may have. |
| Line 25: | Line 13: |
| This text may then be used as part of the UX as makes sense to help the user feel comfortable. Getting a success here and not an error also means that `jabber:iq:gateway` can be used in the next step. | I appreciate your prompt attention to this matter and look forward to the opportunity of working together. |
| Line 27: | Line 15: |
| NOTE: it is also acceptable (and in some UX may be preferred or even necessary) to pre-emptively ask all gateways for the prompt, instead of only once one is selected. | Best regards, |
| Line 29: | Line 17: |
| If an identifier is (or might be, depending on UX) one for a particular gateway, use the following procedure to map it to a Jabber ID and then perform the in-context relevant action on that Jabber ID as though it had been entered directly: 1. If a prompt was got for `jabber:iq:gateway` above then use that protocol to finish resolution: {{{ <iq type='set' to='gateway.tld' id='gate2'> <query xmlns='jabber:iq:gateway'> <prompt>(555) 123-4567</prompt> </query> </iq> <iq type='result' from='gateway.tld' id='gate2'> <query xmlns='jabber:iq:gateway'> <jid>+15551234567@gateway.tld</jid> </query> </iq> }}} 2. If an error is received in response to `jabber:iq:gateway` protocol, print the error message to the user and allow them to try again. This allows the gateway to provide useful feedback about format errors to the user. 3. If an error was received in response to fetching the `jabber:iq:gateway` prompt, then the gateway does not support this protocol. Look for a `disco#info > feature[var="jid\20escaping"]` and if found construct a JID using XEP-0106 escaping on the user input concatenated with `@gateway.tld` 4. If `jabber:iq:gateway` and `jid\20escaping` are both unsupported, replace any `@` in the user input with `%` and concatenate `@gateway.tld` NOTE: If the result of this procedure is a string that is not a valid Jabber ID, it should be rejected just as if a user manually keyed in an invalid Jabber ID. |
Allen Scofield Owner Allen Scofield Medical Equipment 3675 W Ninigret Dr, Salt Lake City UT 84104 USA |
Hello,
I trust this message finds you well. My name is Allen Scofield, and I am the owner of Allen Scofield Medical Equipment located at 3675 W Ninigret Dr, Salt Lake City, UT 84104, USA.
After careful consideration, I am interested in retaining your esteemed firm to handle legal matters pertaining to business and commercial law on behalf of Allen Scofield Medical Equipment.
I believe that your expertise aligns with the specific legal needs that my business requires.
To discuss this further and explore the possibility of engaging your services, I kindly request that you contact me via email at allen.scofield@executivesemail.online at your earliest convenience.
I am eager to delve into the details of our potential collaboration and address any inquiries you may have.
I appreciate your prompt attention to this matter and look forward to the opportunity of working together.
Best regards,
Allen Scofield Owner Allen Scofield Medical Equipment 3675 W Ninigret Dr, Salt Lake City UT 84104 USA