On Wed, Dec 08, 2004 at 02:26:30PM -0700, Peter Saint-Andre wrote:
> In article <[EMAIL PROTECTED]>,
> Ralph Meijer <[EMAIL PROTECTED]> wrote:
>
> > On Wed, Nov 17, 2004 at 10:02:40AM -0700, Peter Saint-Andre wrote:
> > > Two further issues/questions:
> > >
> > > (1) The more I look at, the more I think that it would be best to
> > > encapsulate disco/pubsub NodeIDs in the query component, e.g., something
> > > like ?disco&node=foo. This seems simpler than putting it in the path,
> > > which strikes me as unnecessarily complicated.
> >
> > Yes, I agree. In XMPP, the node is also 'just' an attribute of some specific
> > action (like disco).
> >
> > For the moment we can leave out path segment parameters entirely, but maybe
> > we should reserve the allowed reserved characters for future use? Did that
> > parse?
>
> Hmm, but designing for unknown use cases is probably not a good idea.
Well, after a bit over three years [*], I am finding me disagreeing with
myself.
Within the work on federating social networks, I am looking at linking
to publish-subscribe nodes from HTML and Atom documents like so:
<link rel='xmpp' href='xmpp:...'/>
The rel 'xmpp' is debatable, but as far as I know there is no one
referring to XMPP entities from HTML yet. In this case it could refer
to any kind of xmpp entity: users (' accounts), MUC rooms, servers, etc.
The problem I have is that there is no nice way to encapsulate the
combination JID + NodeID in a URI without specifying an action.
I would like to avoid specifying an action because I believe it is
better if a consumer of such an URI would maybe use service discovery on
the JID/NodeID and then provide possible actions based on that. For
pubsub nodes, that might be subscribing, but also maybe retrieving
previously published items.
So I am tempted to come back to my original proposal of using URI Path
Component parameters looking like this:
xmpp:[EMAIL PROTECTED];node=f9451384-e23e-449f-8a8b-918649205f3c
Opinions?
I'm cross posting to [email protected] because I'm not sure if anyone reads
this list anymore.
[*] If you don't have the whole archive handy, refer to the archive of
the xmppwg mailing list for the thread that starts here:
http://mail.jabber.org/pipermail/xmppwg/2004-November/002215.html
Beware botching of all the examples by replacement of the at-sign
by ' at '. In that thread I explain the concept of URI Path
Component parameters and give some more examples.
--
Groetjes,
ralphm
