Re: [Standards] Disco Search

2013-01-25 Thread Justin Karneges 
On Friday, January 25, 2013 10:31:32 PM Dave Cridland wrote:
 b) A generalized mechanism for constructing node names programmatically to
 find such information? Say urn:xmpp:disco:search?owner=d...@jabber.org for
 example.

XEP-303 suggests something exactly like this: 'A dynamic node accepts 
additional parameters by appending the parameters to the node name using a 
query-like notation. Parameters and values in the query string MUST be 
percent-encoded.'

I think this would be a useful concept to share across pubsub-based specs.

Justin

Re: [Standards] Disco Search

2013-01-25 Thread Lance Stout 
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_TYPEvalueurn:xmpp:pubsub:search/value/field
field var=ownervalued...@jabber.org/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_TYPEvalueurn:xmpp:search:pubsub/value/field
  field var=ownervalued...@jabber.org/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 d...@cridland.net 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:search?owner=d...@jabber.org for 
 example.
 
 Dave.
 



smime.p7s
Description: S/MIME cryptographic signature