The next approach uses named complex types and then generates the element structures from them. In this example, the types are typically declared together at the beginning of the document and then referenced later on. Our example formulated this way looks like this:
In this model, each element is declared separately. However, the model of the element content (the complexType) is declared independently of the element name (the element declaration itself). This can lead to some headaches if elements with matching names have different content models. The third approach resolves this by using global element declarations, referenced using the ref attribute on the actual element declarations:
![]()
![]() | Security considerations for mobile hardware by Alan Zeichick, principal analyst, Camden Associates. Intel Corp. ... |
![]() | Multithreaded technology and multi-core processors by Craig Szydlowski, Infrastructure Processor Division, Intel Corp. ... |
If you're interested in this topic, these articles may be helpful:
![]() | Data points: modeling relational data in XML, part 2 by Kevin Williams, founder and CEO, Blue Oxide Technologies. Intel Cor... |
![]() | Final Cut Pro XML Interchange Format Apple Inc. The Final Cut Pro XML Interchange Format provides extens... |
![]() | XML Web services: the long-term security risks by Andrew Yang, senior director of project management, Westbridge Tech... |
![]() | Oracle Database 10g XML & SQL, Chapter 7: Putting It All Together with XML Pipeline, JSPs, and XSQL by Mark Scardina, Ben Chang, and Jinyu Wang. McGraw-Hill Osborne Med... |
![]() | Scaling XML parsing on Intel architecture By Andy Longshaw, Content Master Ltd. Intel Corp. XML provides many b... |
![]()
Related Jobs:


