DMNFTF — metamodel for structured ItemDefinitions doesn't work

Consider an ItemDefinition (ID) for an Invoice that contains 2 sub-items, shippingAddress and billingAddress, both of type Address, containing sub-items street and city, both strings, etc.

Clearly, Invoice, Address, and string are all IDs. But shippingAddress, billingAddress, street, and city are not IDs. Rather, they are InformationItems. The MM in Figure 26 of the spec has an itemComponentRef from ID to ID. This is an attempt to model a compound ID like Invoice as a collection of sub-IDs. This incorrect. Invoice is a collection of 2 sub-InformationItems, shippingAddress and billingAddress. Both these IIs refer to the Address ID. The Address ID in turn is a collection of IIs for street, city, etc. These have an ID of string.

Proposal: replace itemComponentRef (in Figure 26) with a composition from ID to II named itemComponent.

The ID (e.g. Invoice) owns its itemComponents (e.g. shippingAddress and billingAddress).

Removed the ItemComponentRef attribute and added an ItemComponent class