> B) Content Location - Since alignment of Code and Name is required in 
> the IIM implementation, I suggest that this dictates an XMP bag array 
> structure to maintain the alignment.
> 
> Iptc4xmpIIM:ContentLocation bag ContentLocationDetails (structure)
> 
> ContentLocationDetails (structure)
>- Code           Text
>- Name         Text

The goal of the "IIM Schema for XMP" is not to add any functionality over IIM. I agree to your 
design thoughts but as no sub-structure for Code/Name exists in IIM no such structure was 
adopted for the XMP schema

** The structure of  Code/Name pairs is defined in the IIM spec, bottom of page 31, "must immediately follow and correspond to it". The bag structure is the direct technique to implement this required relationship in XMP. 

> 
> C) Reference - 2:45, 47, and 50 are repeatable in "sequential 
> triplets" in IIM. I suggest that this dictates an XMP seq array 
> structure to maintain the alignment of the triplets.
> 
> Iptc4xmpIIM:Reference seq ReferenceDetails (structure)
> 
> ReferenceDetails (structure)
>- Service        Text
>- Date            Date
>- Number     Text
> 

See my note above, the same applies here.

** The structure of  Service/Date/Number "triplet" is defined in the IIM spec page 34, "2:45 ... Must be followed by 2:47 and 2:50". The seq structure is the direct technique to implement this required relationship in XMP.