Document Object Model Analogy: In many ways, the Document Object Model (DOM) can be compared to the schematic of a house. A house's schematic details the relation and placement of objects within a house. For instance, within a schematic, you are able to understand the relationship of the sink to the wall, as well as the corresponding plumbing. In other words, the schematic defines the relationship of one object to another and often, illustrates the rules by which they are governed. HTML and XML documents are also composed of objects, and although these objects may not be physical, like a sink, their organisation and interaction is still coordinated by a set of rules. In this case, the DOM acts as a foundation for the placement and interaction of objects within a document. Whether the object is a table, a piece of information, or a script, the DOM specifies a model for the interaction of these objects. For developers, a thorough understanding of these relationships is paramount, and often, it forms the basis for a system's development.Über den Autor:
Joe Marini (San Francisco, CA) is the founder of Lepton Technologies, a third-party development company. Prior to forming Lepton Technologies, he was a senior software engineer at Macromedia, where he was one of the architects of the Dreamweaver Extensibility mechanism. Joe is responsible for the extensibility architectures of several other popular software programs, such as mFactory's mTropolis multimedia application and Quark Inc.'s QuarkXPress. He lives and works in San Francisco, CA with his wife, Stacy, and dog, Milo.
„Über diesen Titel“ kann sich auf eine andere Ausgabe dieses Titels beziehen.