Open yellowbean opened 4 months ago
For each asset, there should be one more extra Optional field obligor
obligor
object shall have three optional fields:
User now are able to apply performance assumption by:
In Python wrapper:
("ByObligor"
,("EqID",[<ID>...],<Asset Performance Assumption> )
,("hasAnyTag",[<Tag>],<Asset Performance Assumption> )
,("hasAllTag",[<Tag>],<Asset Performance Assumption> )
,("EqTag",[<Tag>], <Asset Performance Assumption> )
,("subsetTag",[<Tag>],<Asset Performance Assumption> )
,("Rest", <Asset Performance Assumption> )
,....
)
Tag on asset can be very flexible , just act like a map[str, str] , ie
or
Because in the CLO transaction , or other transaction, it requires to query sum balance of assets with certain criteria. which suggest, the tagging can be anything. The engine should able to query by type of string.
This will impose strict requirement on the inputs and complex internal query function .
But it seems inevitable .