What I am seeing in my actual data for the sample repository I am working with is
Name = "Stereotypes" and Type = "element property" or "connector property" with an Description which looks something like @STEREO;Name=oeInclude;GUID={A10BA680-0109-45ab-AD7F-3B95AC6F801C};@ENDSTEREO; and there is a Client GUID, but no Supplier. The GUID in the description is the GUID of the stereotype. In this particular case, the Client is the GUID of the corresponding t_object. I suppose that I can tell which table to find the Client in by what the stereotype is a stereotype of?
or
Name = "Custom Properties" and Type = "element properties", "connector property", "connectorDestEnd property", or "connectorSrcEnd property" and the Description is something like @PROP=@NAME=isDerived@ENDNAME;@TYPE=Boolean@ENDTYPE;@VALU=false@ENDVALU;@PRMT=@ENDPRMT;@ENDPROP;
Again, a Client GUID and no Supplier. Again, I suppose that I can deduce the table of the Client GUID from the Type and the syntax of the Description seems apparent enough.
Now, all I guess I am missing, is why.
In the case of the stereotype, the object itself has the stereotype, so what is added by this additional connection?
In the case of the custom properties, where do these come from? Things missing from the schema? E.g., in this specific case, this is a foreign key association between two tables.
