XML data binding: Difference between revisions

Revision as of 23:29, 23 July 2004

Revision as of 20:19, 4 August 2004

Line 1:

XML data binding refers to the process of representing the information in an [[XML]] document as an [[object]] in computer memory. This allows [[application|applications]] to access the data in the XML from the object rather than using the [[DOM]] to retrieve the data from a direct representation of the XML itself.

Ronald Bourret has a very good and thorough article on the subject (updated: June 23, 2004):

An XML data binder accomplishes this by creating a mapping between elements of the [[XML schema]] of the document we wish to bind and [[members]] of an [[object schema]] to be represented in memory.

http://www.rpbourret.com/xml/XMLDataBinding.htm

When this process is applied to convert an XML document to an object, it is called [[marshalling]]. The reverse process, to serialize an object as XML, is called [[unmarshalling]].

{{substub}}

Because XML is inherently sequential and objects are (usually) not, XML data binding mappings often fail to preserve all the information in an XML document. Specifically, information like [[comments]], [[entity-references]], and [[sibling order]] will fail to be preserved in the object representation created by the binding application. This is not necessarily true; sufficiently complex data binders are capable of preserving 100% of the information in an XML document.

==External Links==

Ronald Bourret has a very good and thorough [http://www.rpbourret.com/xml/XMLDataBinding.htm article] on the subject (updated: June 23, 2004):

{{stub}}