XML Parser Architecture for Windows Mobile
A version of this page is also available for
4/8/2010
The XML parser on Windows phones is a componentized version of the Microsoft XML Parser (MSXML) version 3.0 SP1. The XML parser is divided into several Catalog items, which are dependent on other technologies both inside and outside Windows Mobile XML functionality.
Note
The software development kit (SDK) for your particular Windows phone may or may not contain the individual XML parser Catalog items. The functionality in your target device depends on the Catalog items that the hardware manufacturer selected. To determine the functionality available on your and in individual custom SDKs, select the appropriate Catalog items link in the See Also section of this topic. If your Help browser takes you to the documentation for the Catalog item then the Catalog item has been included in this SDK.
The following illustration shows the architecture of the XML functionality.
.gif "Aa923357.1038ae29-791f-4a23-bf93-bb03f500653d(en-us,MSDN.10).gif")
The XML Core Services and DOM Catalog item provides core XML parsing functionality and is required by all of the other XML Catalog items. The DOM uses a tree-based document object model. An alternative set of APIs for XML parsing; the Simple API for XML (SAX) Catalog item uses a stream-based model. With the stream-based model, you can process larger XML documents. Also, the model has better memory performance characteristics than DOM.
The XML Query Language (XQL) Catalog item provides a mechanism for retrieving and interpreting XML data. Extensible Stylesheet Language Transformation (XSLT), which requires XQL to be included in the OS design, provides a method for converting XML data into different formats. You can use XSLT to convert XML into HTML for display in a browser, or to convert XML data from one schema to another.
With XML HTTP, you can post XML data using HTTP. XML HTTP requires the URL Moniker Services (URLMON) Catalog item, which, in turn, requires WinInet. URLMON and WinInet provide Internet capabilities.
Because Core Services and DOM require Internet functionality, all the other XML Catalog items receive Internet functionality. If XML HTTP is included in the platform, then WinInet is also included. If XML HTTP is not included in the platform, then either Windows Internet Services (WinInet) or HTTPLite will be included in the platform. WinInet is included when using one of the Internet Appliance design templates. Internet Appliance design templates are used for full-featured target devices that usually include monitor support. The HTTPLite Catalog item is typically included on target devices, such as routers, that use one of the Headless design templates.
See Also
Reference
Other Resources
XML Core Services and Document Object Model
XML Query Language (XQL)
XML Stylesheet Language Transformations (XSLT)
XML SAX
WinInet Application Development
URL Moniker Services Application Development