[standards-jig] extending disco#info result

Ian Paterson ian.paterson at clientside.co.uk
Fri Feb 20 12:24:59 UTC 2004


Now that infobits has gone, can we decide between extending disco#info
results (JEP-30) generically with x:data or with different namespaces
depending on the entity?

Here is a MUC example with x:data. The <identity/> element should give the
client enough information to correctly interpret the name/value pairs in
each <field/>:

<iq type='result'
    from='darkcave at macbeth.shakespeare.lit'
    to='hag66 at shakespeare.lit/pda'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    <identity
        category='conference'
        type='text'
        name='A Dark Cave'/>
    <feature var='http://jabber.org/protocol/muc'/>
    <feature var='muc_temporary'/>
    <feature var='muc_unmoderated'/>
    <feature var='muc_nonanonymous'/>
    <x xmlns='jabber:x:data' type='result'>
      <field var='desc'><value>The place for all good
witches!</value></field>
      <field var='subject'><value>Fire Burn and Cauldron
Bubble</value></field>
      <field var='occupants'><value>3</value></field>
    </x>
  </query>
</iq>


Here is the same example with a MUC namespace:

<iq type='result'
    from='darkcave at macbeth.shakespeare.lit'
    to='hag66 at shakespeare.lit/pda'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    <identity
        category='conference'
        type='text'
        name='A Dark Cave'/>
    <feature var='http://jabber.org/protocol/muc'/>
    <feature var='muc_temporary'/>
    <feature var='muc_unmoderated'/>
    <feature var='muc_nonanonymous'/>
    <roominfo xmlns='http://jabber.org/protocol/muc#room'
        desc='The place for all good witches!'
        subject='Fire Burn and Cauldron Bubble'
        occupants='3'/>
  </query>
</iq>





More information about the Standards mailing list