Instances of LINQ to XSD types are referred to as XML objects because the generated classes model typed
views on untyped XML trees. Another way to say it is that the generated classes use properties to access
the untyped XML trees.
An instance of LINQ to XSD is a set of classes that form wrappers around an instance of the LINQ to
XML XElement class.
353
Appendix C: LINQ to XSD
Mapping Rules
When a schema is mapped to an object type, LINQ to XSD requires that the mapping meet
several constraints:
??‘ The mapping is understandable to the developer.
??‘ The mapping does not rely on any customization by default.
??‘ The mapping must derive classes that are close to the expectation of an OO programmer.
??‘ The mapping covers all of the XML schema.
??‘ The mapping facilitates round-tripping of instance data.
??‘ The mapping conveys, where possible, most schema objectives into the object models.
This systematic rule mapping ensures a clean, precise mapping, and is assumed by LINQ to XSD. The
following is a list of most of the mapping rules that are utilized by LINQ to XSD to map XML schemas to
.
Pages:
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545