"Klotz, Leigh" wrote:
>  
> ...XForms is not a standalone
>  document format, and is intended to be used with other XML languages such as
>  XHTML and SVG and so on.  I personally think it would be a good summer
>  project for someone to look at a host language that uses XForms vocabulary
>  with WSDL; as you point out, WSDL and XForms would share a Schema.

I would expect it to be easier to reuse the schema by inclusion!

>  As for the GET/POST/SOAP/REST collection of issues, when you submit an
>  XForms instance, it can be POSTed over HTTP in a variety of serialization
>  formats -- the structure can be flattened to multipart/form-data or
>  application/x-www-form-urlencoded, or it can be posted as XML as the body of
>  the POST.  XForms can also submit an instance by a GET over HTTP, with the
>  data flattened and serialized according to roughly HTML rules, module some
>  I18N issues.  (XForms is just past last call, so I'm speaking personally
>  about XForms generically here, not about a specific draft revision.)
> 
>  However, note that the XForms spec allows for some extensibility in the
>  submission method and serialization method; I'd be personally interested in
>  hearing if anyone has given thought to other serialization methods that
>  might simplify interaction with XML-based services such as WSDL/SOAP or a
>  nascent WSDL+REST or something else such as XML-RPC. 

REST does not prescribe any particular variant of XML so I'd say that
XForms is already 100% compatible with REST.

 Paul Prescod

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>