[standards-jig] extending disco#info result
Matthew A. Miller
linuxwolf at outer-planes.net
Wed Feb 25 14:49:40 UTC 2004
Just because my software doesn't understand what to do with the
particular fields within an x:data form (other than render them) doesn't
mean I don't understand what to do with it.
Building off the examples provided so far, let's say we get the form:
<x xmlns='jabber:x:data' type='result'>
<field var='FORM_TYPE' type='hidden'>
<value>The place for all good witches!</value>
<value>Fire Burn and Cauldron Bubble</value>
If my particular client turned this into some type of "properties" panel
or dialog to display to me, I would be able to tell that (in my
A) The room is intended for all good witches
B) They're currently burning and boiling stuff
C) There's three "people" already there
My client may not know what to do other than display it. However, I do
know what to do with this information, and I use it to aid me in
determining if I also want to enter the room.
If we went with "custom" structures, my client would need to understand
it in order to display it. If my software doesn't get it, I don't
either, even though I would "get it" better than most software would.
Richard Dobson wrote:
>But if clients do not already understand this extension should they be
>displaying any of this anyway??
>Is there any real value in displaying this in a generic GUI without first
>understanding what this data is and how to handle it, and if clients are
>coded to specifically understand what should be done with the data then
>there is no difference between understanding the custom namespace. The
>custom namespace has the benefit of not confusing things by being displayed
>by a client that does not understand it and is far simpler to process and
>just seems more in keeping with the way extensions are normally done.
>Standards-JIG mailing list
>Standards-JIG at jabber.org
More information about the Standards