Re: XMPP URI regexes

In article <20050215124456.GA39175 <at> localhost>,
 Ralph Meijer <jabber.org <at> ralphm.ik.nu> wrote:

> On Tue, Feb 01, 2005 at 02:29:51PM -0700, Joe Hildebrand wrote:
> > Of course, there was a bug.  These cases are also currently valid:
> > 
> > xmpp://boo <at> bar
> > xmpp://boo <at> bar#frag
> > xmpp://boo <at> bar?message
> > xmpp://boo <at> bar?message&subject=Hi
> > xmpp://boo <at> bar?message&subject=Hi#frag
> > 
> > Although, as stpeter and I were just discussing IRL, querytype shouldn't be
> > allowed if there is no path-xmpp, since it just wouldn't make sense.
> 
> Maybe the above examples don't make sense, but what about iq's to the local
> server? In XMPP we do this by leaving of a 'to' attribute. Not having a
> path component seems similar, to me.

Well, sure. But do such URIs make sense? Here's a little thought 
experiment. Let's say you are using a groupware application that 
interfaces with XMPP services in order to be informed when other 
people's calendars change (see draft-hildebrand-webdav-notify-01). 
Perhaps you would click an XMPP URI to launch such an application, and 
use Bookmark Storage (JEP-0048) to keep track of the URLs for each 
person's iCal object. And perhaps such an application could be launched 
by clicking on a link encpasulating a URI of the following form (I'm not 
saying this is exactly how such a URI would look, this is just a thought 
experiment after all):