The first example we will cover it the Document Object Model. This example is a remake of a more detailed example, I have reduced the information provided in the example in order to express on the important features of the model. This example can be seen below:
By looking at the example provided above, we can clearly see the process in which the Document Object Model is used. The sample model is designed to show us the way in which the document is linked to each element and the coinciding text that is linked to those elements..
Now we will take a quick look at a simple component object model example. This particular example has been based on one of the models provided by window themselves.
On the example above you see two different types of arrows. The solid arrows are used to indicate the USES, where as the dashed arrows are used to represent the OPTIONALLY USES. The boxes with green out lined text are there to represent the aspects provided with WDTF. The blue high lighted text is you Implement or Modify example. The red is expressing the implementation of your own action interface, and the text high lighted in black indicates your operating systems or driver API. By viewing this sample of the Component Object Model, we can see how the components are linked and the way in which they communication between one another.
So after exploring the Object model we can safely come to the conclusion that the Object model does serve an important purpose that no model before it was able to grasp. Though the model has been modified to fit with specific instances the main use is to model object data.
Windows is one of the more notable vendors who have put the Object Model in the limelight; it will be interesting to see what heights this model reaches with their assistance. I will be keeping a close eye out for the next evolutionary change in the Object Model.
First Page: The Object Model