Resolution:
Metadata schema are useful in many situations where data change but the behavior of your application does not.

One example: Assume that your application wants to send the contents of a Customer table, including certain fields from the PeopleSoft database, to TIBCO MessageBroker. You can use metadata to specify exactly which fields you are interested in; your program will only download and publish the specified fields. If you update the database to a new version, or if the field names you are interested in change for some other reason, you only change the contents of the metadata. Your program itself remains unaffected.

A second example is when you are deploying a complex system with many components developed by multiple parties. The metadata class description serves as an explicit executable specification of the content for the data flowing through the system. Using metadata classes makes it possible to enforce that publishers and subscribers strictly comply with the same data. Since the metadata description is actually used by the running adapters, it further reduces the chances that the specification is misinterpreted by one of several parties and that an adapter publishes messages that have the wrong format.