For the integration of data there are many techniques of using SQLXML and .net the sql client data provider supports execute xml reader it can consume directly the result of it to do the xml query the user can use xml directly, the role of XML query in reinventing the wheel is very large the overlap between the xquery and xslt is too great for W3C to recommend both as separate languages if the XSLT is not considered enough as an XML query language then its development should be built from the same and semantic syntactic base as XSLTThe most
This short description is about the work of XForms. Before talking about XForms it's important to understand the concept of forms. Forms are to collect the data so we should not get surprised if we say XForms is basically depending on instance data. Instance data are these data which are based on XML. The data are defined in the terms of XPath's internal tree illustration and dispensation of XML.
It may look odd at first to relate XPath with XForms. However, XPath is the well-known as the ordinary layer between XSLT and XPointer. Since XForms
Forms are for collecting data, so it's not surprising that the most important concept in XForms is "instance data", an internal representation of the data mapped to the familiar "form controls". Instance data is based on XML and defined in terms of XPath's internal tree representation and processing of XML.
It might seem strange at first to associate XPath and XForms. XPath is best known as the common layer between XSLT and XPointer, not as a foundation for web forms. As XForms evolved, however, it became apparent that forms needed greater structure