fosterlynn
commented
9 years ago This also applies to our "use cases" (which might be more like exchange types). So we have Purchase and Expense, which are basically the same as Sale, except reversed inward vs outward. Would be good to reconcile/normalize this to be vanilla REA irrespective of context. (I think. Even if we don't, we can still put it out in LOD in a normalized way. But still, it is bothersome conceptually and ontologically.)
We currently have an agent association behavior for customer and one for supplier, and also create an association for each of those as defaults in the data. Really this is one association, from different ends. It works OK for us now because we have an inside and outside perspective based on the installation of network context agents. But it isn't right, and it could be that context agents would have a trading relationship between them, which would require 2 relationships instead of one.
A bit of analysis needed.