[Fwd: [regrep-cc-review] Core Components Issue: Representation of AggregateCore Components]

Forwarding Duane's response to Serm's posting - please see my comments
below.

<Quote1>
It is important to note that Buyer.Address != Seller. Address.

The distinguishing factor between the two is the context of Role.  Role 
is only one of 8 context drivers.
</Quote1>

Yes!

<Quote2>
The registry can easily store the metadata for these and include the 
relationships.
</Quote2>

Yes!

<Quote3>
The relationships are:

1. Buyter.Addres and Seller.Address and both both "used" within "Order".
2. Both have the same physical structure (dependant on other contexts 
such a geo-political)
3. Both inherit from an ACC called "address"
4. Both may be represented in many forms as instance data (*EDI, XML
etc.)
</Quote3>

Yes - #3 is a great point - they "inherit from" an ACC called "Address".
That is, "BuyerAddress. Details" and "SellerAddress. Details" are
created from an ACC called "Address. Details" by:

(1) Classifying "Address. Details" according to node of the "Role"
classification schema
(2) Adding an Object Class Qualifier ("Buyer" or "Seller") to the (what
is now an) ABIE

My recent proposal was that the Object Class Qualifier be included in a
Slot that is associated with the Classification node, so that it is
automatically inserted as the Object Class Qualifier in the resultant
ABIE when the classification is done.

Thoughts?

Joe