I too have been working with several extensions lately that need search capabilities, so this has been in my mind the last few days.
I don't have fully formed ideas on how how it would look, etc, but I would be
interested in experimenting with expanding (or drafting a replacement) XEP-0055
to include a node parameter to scope what is being searched and use that
instead.
Eg, with expanding the existing search XEP:
<query xmlns="jabber:iq:search" node="urn:xmpp:somethingappropriate">
<x xmlns="jabber:x:data" type="submit">
<field var="FORM_TYPE"><value>urn:xmpp:pubsub:search</value></field>
<field var="owner"><value>[email protected]</value></field>
</x>
</query>
Or with some new XEP similar to RSM to augment a normal query:
<query xmlns="http://jabber.org/protocol/disco#items";>
<search xmlns="urn:xmpp:search:0">
<x xmlns="jabber:x:data">
<field var="FORM_TYPE"><value>urn:xmpp:search:pubsub</value></field>
<field var="owner"><value>[email protected]</value></field>
</x>
</search>
</query>
As for disco node names with query parameters, it works and I know XEP-0303
uses it, but it opens up a can of worms of implementation details and
variations that I'd prefer to avoid if possible.
Lance
On Jan 25, 2013, at 2:31 PM, Dave Cridland <[email protected]> wrote:
> Hi folks,
>
> I have a use case for finding all pubsub nodes on a service for which the
> caller has an owner affiliation.
>
> I'm implementing this as a private extension comprising a "well-known" disco
> node, which when given a disco#items query would list such nodes.
>
> Is there any interest in standardizing:
>
> a) Such a node.
>
> b) A generalized mechanism for constructing node names programmatically to
> find such information? Say urn:xmpp:disco:[email protected] for
> example.
>
> Dave.
>
smime.p7s
Description: S/MIME cryptographic signature
