1. Steps to integrate XML How does XML processing work? Simple uses of passive DOM objects Adding behaviour to information A converter and translator subsystem The DNA of a large system The one and only requirement

2. XML File to XML Application XML file XML ParserEntity Manager DB Storage manager Http Storage manager XML Application Events

3. XML Application Can do on-the-fly processing Can build a tree of Document Object Model nodes in memory Can use a DOM Factory to get the nodes

4. XML Application to DOM XML App startElementEvent(“memo”); DOM Factory contains different node types createElement( “memo”,…) Element : Node Tree of DOM nodes

5. Simple memo.xml as DOM tree

6. Simple uses of passive DOM objects System configuration Repository/meta information Debug and trace formats Semantic data streams composite message pattern

7. Advantages of XML information Code savings because only one format Standard tools can handle everything from config files to debug output, from editing to publishing Symbolic interfaces are more flexible but are still under control Information can evolve without code changes

8. Adding behaviour to information DOM node Observable Interface implements DOM node, observable Supplier client Consumer client write update Simple blackboard implementation, enables information sharing and event driven processing without coupling clients

9. A converter and translator subsystem Company A Company B Binary formats, business logic and formats hardcoded Converter framework XML/DOM representation in terms of company A XML/DOM representation in terms of company B Converter framework Translator framework, provides wrappers that translate from DOM A to DOM B, uses command object plug-ins for calculated mappings

10. The DNA of a large System Factories use XML information to build and assemble objects Objects use XML information to learn what they are supposed to do System behaviour emerges from cycles of transcribing XML into objects and those objects turning around and transcribing more XML “DNA” into further objects.

11. The one and only requirement Represent knowledge explicitly, in a human and machine readable form. This is true for application domain knowledge as well as for the processing system internals.