Hi Ivan, On Donnerstag, 26. April 2018 14:03:15 CEST Ivan Vučica wrote: > Today I learned about XEP-0068 which seems to specify an IDL-like XML > for data forms. It also defines a registry for FORM_TYPEs maintained > by the XMPP Registrar. I feel this could be very useful to client > libraries, which can generate code with structs for predefined types > a-la protocol buffers or thrift or -- presumably that was the > intention. > > Is anyone using the <form_type/> definitions for code generation? If > so, for which language are you generating the stubs?
Yes. aioxmpp has an (inofficial and not shipped) utility for this [1]. It works and has been used for the MUC config form for example. > So: Should these /at least/ include the <form_type/> definition? > Should this be then updated in the registry? My understanding is that the registry will normally be updated once a XEP enters Draft status. > Next up: XML version of the registry (formtypes.xml) would be much > more useful if it included the <form_types/> themselves. How are the > HTML and XML versions generated? The XML data is in [2]. kind regards, Jonas [1]: https://github.com/horazont/aioxmpp/blob/devel/utils/ form_type_to_code.py [2]: https://github.com/xsf/registrar/blob/master/formtypes.xml
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
