Re: Bug 1852: support creation of xmpp: field types in OGo

> To close the issue from my side, if you feel that its useful, please  
> commit it. After all the user has to configure the extended  
> attributes to enable the feature and do not get them automagically.

I'm playing with this patch, and I have an extended attribute configured
like: { defaultUrlScheme = "xmpp:"; key = "jabberid";  type = 20; }

It works, at least 'technically'

But -
(a) The links rendered for XMPP are not actually compliant with RFC4622
[ http://www.ietf.org/rfc/rfc4622.txt ].  A link to send to an address
from the default XMPP account should look like -
xmpp:[email protected]?message  - or at least that is how I interpret
section:

   As an example, an XMPP IRI/URI intended to launch an interface for
   sending a message to the XMPP entity "[email protected]" might
   be represented as follows:

      xmpp:[email protected]?message

   Similarly, an XMPP IRI/URI intended to launch an interface for
   sending a message to the XMPP entity "[email protected]" with
   a particular subject might be represented as follows:

      xmpp:[email protected]?message;subject=Hello%20World

  It doesn't seam clear what a xmpp:{address} should actually do, unless
I'm missing something.

(b) I haven't been able to find/configure a browser/client combo that
actually deals with an XMPP URL in the expected fashion.  You can
configure FF like:
1. Type "about:config" in the url bar
2. Right-click and select New->String
3. Enter "network.protocol-handler.app.xmpp" as the preference name
4. Enter the application to run 
 - and enter the client (gaim, psi, etc...) as the handling application.
But doing so doesn't seem to get you anything other than to start the
application - which I can do from the "Start" menu. :)

Any pointers on (b) would be appreciated.


>From the XMPP RFC I think the best form for a XMPP URL is like -
xmpp://[email protected]/[email protected]?message - where guest@ is
the user's IM address and support@ is the address you want to send to.

Ideally I think the solution would be to add the imAddress attribute to
the web interface and a Default to specify what type of link it should
be (MSN, XMPP, etc...) or just be draconian and render it as XMPP. :)
Then render the link, if XMPP,  as xmpp://{user's imAddress}/{imAddress
value}?message   That seems like it would be straight forward to
implement.

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss