[standards-jig] UPDATED: JEP-0004

Ryan Eatmon reatmon at jabber.org
Wed Sep 25 17:34:39 UTC 2002


Because his definition of a form and our definition are different.  He 
wants field types, tab order, keyboard accellerators, positioning, etc...

While all we are trying to do is provide a simple method for asking 
for/passing around data.


Joe Hildebrand wrote:

>Ok, now *I'm* confused.  Why can't you use an x:data form in a
><message/> to pop up forms and do dialog exchanges?  That's just a
>potential use of the protocol.  All your client needs to do is render
>forms as they come in, which a couple of clients already do.
>
>
>Ralph Siemsen <ralphs at blueairnetworks.com> writes:
>
>  
>
>>Thomas Muldowney wrote:
>>    
>>
>>>A quick question so I can better reply to your position.  Are you
>>>comparing this to XForms or HTML Forms?  You're previous reply made it
>>>seem like you were comparing to the weak HTML Forms, but now it seems
>>>more like XForms.
>>>      
>>>
>>Neither and both, really... I think there are strengths and
>>weakenesses in both, and I'm not really trying to advocate using
>>either one directly in jabber... however, for many of the applications
>>I am working on, it would be tremendously helpful if I could pop up
>>forms and do dialog exchanges via jabber.  I initially thought that
>>x:data was the means to doing this, but have been corrected in my
>>thinking.
>>
>>-R
>>
>>_______________________________________________
>>Standards-JIG mailing list
>>Standards-JIG at jabber.org
>>http://mailman.jabber.org/listinfo/standards-jig
>>    
>>
>
>  
>

-- 

Ryan Eatmon                   reatmon at jabber.org 
------------------------------------------------
Jabber.org - Perl Team    jid:reatmon at jabber.org





More information about the Standards mailing list