This wiki has undergone a migration to Confluence found Here
Difference between revisions of "UML ITS Policy"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
==Summary== | ==Summary== | ||
− | The | + | The UML ITS is a technical infrastructure for making V3 wire formats easier to implement. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | [[RBM]] <--'''Policies'''--> [[XUM]] [[Implementable Models]] (UML diagram <-> Schema) | |
− | + | One of the important things about the XUM is that it makes the implicit transforms that | |
− | + | happen between the [[RBM]] and the actual wire format explicit. Some of these transforms | |
− | + | are required by the existing methodology, but a number of possible tranforms and policy | |
− | + | decisions that might improve the implementation experience for some users have been | |
+ | identified. | ||
− | + | We must decide whether to: | |
+ | * [[flatten the instances]] | ||
+ | * [[Use business names in the instance]] | ||
+ | * [[Send fixed and default values]] | ||
+ | * [[Support By References and By Value]] | ||
− | + | And we must also decide which kind of model(s) to create XUM's for. The [[XUM Creation Level]] | |
− | + | document considers this most important issue in depth. | |
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 00:46, 15 September 2006
Summary
The UML ITS is a technical infrastructure for making V3 wire formats easier to implement.
RBM <--Policies--> XUM Implementable Models (UML diagram <-> Schema)
One of the important things about the XUM is that it makes the implicit transforms that happen between the RBM and the actual wire format explicit. Some of these transforms are required by the existing methodology, but a number of possible tranforms and policy decisions that might improve the implementation experience for some users have been identified.
We must decide whether to:
- flatten the instances
- Use business names in the instance
- Send fixed and default values
- Support By References and By Value
And we must also decide which kind of model(s) to create XUM's for. The XUM Creation Level document considers this most important issue in depth.