BCC as RIM Association

Forwarded on behalf of Diego.

Diego Ballvé wrote:
> 
> Joe,
> 
> I'm trying to build some basis for my last proposal, BCC as
> RIM Associattion. Please check this text while looking at CCTS
> 1.9, page 75, Figure 7-1. Alsoattached a possible UML diagram
> for this way to see CCTS.
> 
> Regards,
> Diego
> 
> ----------------------------
> 
> From botton right, with XML analogy, CCT - Core Component Type:
> Gives the primitive type (decimal, int, string, data, binary)
> for the information (ContentComponent, XML Element's text),
> plus primitive type for extra info (Supplementary Component,
> XML Element's attributes).
> 
> Currently we've settled for having CCT, ContentComponent and
> SupplementaryComponent as different ExtrinsicObjects, though
> there is a doubt wether CCT and ContentComponent could be
> stored in the same RegistryObject.
> 
> Next, DataType further restricts the CCT. Restrictions for both
> Content and Supplementary Content. Restriction types are limited
> to a few types (Check page 80, table 7.1, of CCTS 1.9).
> 
> Current mapping overview, 3 different RegistryObjects for
> DataType, ContentComponentRestrictions and
> SupplementaryComponentRestriction, connected by RIM Associations.
> 
> In the middle of the picture, we've eliminated those 1 to 1
> relations and merged the objects, keeping the name as xCC.
> So (we need an UML for this):
> - BasicCoreComponent (BCC) also contains Basic CCProperty fields;
>   AggregateCoreComponent references ASCC directly (not via prop)
> - AssociationCoreComponent (ASCC) also contains Association
>   CCProperty fields; AggregateCoreComponent references ASCC
>   directly (not via prop).
> 
> With this last change I'm not saying that we should modify CCTS
> 1.9. We just see it in a different way when storing it.
> Attached is a modified UML diagram (sample! done with paint).
> See the similarities between ASCC and BCC.
> 
>   ------------------------------------------------------------------------
>                                          Name: figure7-1-newInterpretation.jpg
>    figure7-1-newInterpretation.jpg       Type: JPEG Image (image/jpeg)
>                                      Encoding: base64
>                                   Description: figure7-1-newInterpretation.jpg