...
- simple and compact enough to be easily understood and used, but broad enough to not leave out something someone needs to conduct business (simple vs complete)
- generic enough to be accepted from an international perspective, but still be able to support the capture & communication of necessary region-specific data (generic vs specific)
- able to express data in a controlled vocabulary (so everyone can understand what it means), but still allow that controlled vocabulary to be continually changing to support match the dynamic nature of data requirements (static & stable vs fluid & dynamic)dynamic)
Internationalization is important for this work, but conflicting requirements must be reconciled:
ADM developers must seek universality, staying free of regionally specific clutter. However, different geographies’ business processes involve context specific data (e.g., USA EPA product numbers.) If this data not accommodated, the ADM’s relevance suffers.
Additionally, it is desirable to use a controlled vocabulary. However, the dynamic nature of business and regulation requires this vocabulary to be easily extensible. If this controlled vocabulary is allowed to become "stale", again, the ADM’s relevance suffers.
General Goal (of the paper)
...