plcs-ccb-admin

I will let others comment on the potential problems for implementations. The issue here is a classic one: An ID should keep a bond to the ID-owner. Requirement, specifications, contract clauses, faults etc should be referenced by a persistent ID. The ID of the owner is the primary ID, all others should keep that as a foreign key(=ID). So when two, or more parties, are involved in an exchange - they should all use the ID assigned by the owner, and map internally to their own system(s)' IDs for the...

REJECT: Explicits can make it easier to understand how a particualr need is to be cater for by the model. However there are no end to the list of possible explicits that could be included in th model. Hence the policy is to avoid explicts. The recommende modeling style is to support explicits by means of classifications and reference data. This approach results in a cleaner model and supports full flexiblity for the various business needs.

yes, differnt org will have differnt needs here too.... So IF such conversions are...

I understand that Rob have a business need and Phil suggest addressing it by "assigning...

agree.