>A pattern seems to have emerged from some standard organizations in which they try to construct their data exchanges based off of existing paper forms. Unfortunately, this tends to lead to a very inflexible model, that conveys one particular view point of the data.
Instead, modeling should be based on the requirements of the community, and not necessarily the paper forms that are being used today. Modeling the requirements as they exist now, allows the model to be used regardless of the existing paper forms that may be used currently. A paper form in many ways can not be as expressive as a data model, so we shouldn’t constrain the system by what is being done by paper.
In many ways, we need to take a step back and just look at requirements. The rest will work itself out once the modeling process starts.