Hello, I am reviewing the XEP now and I am frightened with the complexity that has reached the data forms feature in XMPP. Unfortunately, I can't come up with any better solution than described in the XEP I'll try to think about it later and I welcome anybody to a discussion on the topic.
Now some notices: 1. Example 7 is not a valid XML: tag <cancel> is never closed. 2. Do we really need the <xdd:cancel/> tag? I think it looks as a real mess. Maybe we can move the xdd session identifier to some another place outside a form instead? 3. Why do we need the <cancelResponse> tag? Why can't we use usual error reporting mechanism (<iq type="error">) instead? Thanks for your work and good luck. On 07/25/2013 08:25 PM, XMPP Extensions Editor wrote: > The XMPP Extensions Editor has received a proposal for a new XEP. > > Title: Data Forms - Dynamic Forms > > Abstract: > This specification provides extensions to the data forms model > defined in previous XEPs that permits enhanced end-user interaction and > a better user experience. It permits forms to react on user input > by permitting the addition, updating or removal of fields in the form, > server-side validation of fields as well as define new > states making it possible to display disabled controls, > controls with undefined values or error messages, while still > being backwards compatible with the existing data form model with available > extensions. > > > URL: http://xmpp.org/extensions/inbox/dynamic-forms.html > > The XMPP Council will decide in the next two weeks whether to accept this > proposal as an official XEP. > > -- With best regards, Sergey Dobrov, XMPP Developer and JRuDevels.org founder.
