At first glance the MetaView browser might be considered simply as a generic database browser for a given GPO model.

But it is more than this.

From the standard Inspector you can access not only the direct properties of the specific object but also the associated objects. If a set has been classified, then a simple and intuitive interface is provided to allow efficient navigation of the classification structure to access the objects referenced.

You can also access creation methods of object instances to create new objects and in a similar way access any business methods.

Ontological Design Principals

If you have read the notes on design you should understand that to enable effective exploitation of any system, the user needs to have an effective model with which to interact with the system.

Generated Model

Since the GPO model is generated from a simple (as possible) XML description, and the MetaView interacts with this generated model, it is possible to pretty much guarantee the consistency of the model and the type of interactions produced.

This consistency is an aid to the user as they become used to a particular interaction style.

Impedance Mismatch - #2

The GPO model has already removed the classic impedance mismatch between in-memory and on-disk representation structures.

The direct MetaView user interaction with the generated model now further removes the another impedance mismatch, one that is not usually considered, and that is the impedance mismatch between the user interaction structures and the system model.

Change the Model - Change the Interface

If the interaction does not seem correct. Then it may be that the underlying object model is not correct. So simply change the underlying model.