On Wed, 2007-12-12 at 15:26 +0100, Ralph Meijer wrote:
> > [..snip..]
> 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?
So after discussing a bit with David Cridland, we came to the conclusion
that RFC 4622 does not allow this particular syntax. However, the ABNF
does accept the following:
xmpp:[EMAIL PROTECTED];node=f9451384-e23e-449f-8a8b-918649205f3c
That is, putting the NodeID in the query component, with iquerytype
being empty.
In line with XEP-0147, I would like to register the empty string as a
XMPP URI/IRI Querytype for the purpose of pointing to a specific note
without implying a particular action.
David also noticed that the keys and value of the query parameters may
be empty. That's probably not right.
--
Groetjes,
ralphm
--
Groetjes,
ralphm
