Should TX_Vesting_Start Reference the VestingTerms obj id?

[JSv4]

The current spec for the VestingStart requires two IDs - 1) the security_id and 2) the vesting_condition_id. Implicit to this, then, is that the vesting_condition_id must be globally unique for the issuer. I don't think that's necessarily likely, and it's also not documented. The id field for VestingCondition simply says "reference identifier for this condition."

If, for example, you created two VestingTerms objects (two "Vesting Schedules") with the same VestingStartTrigger VestingCondition id of "start", you couldn't start either schedule properly, I don't think. The TX_Vesting_Start transaction would not have a unique condition id to resolve. I think for this (and other reasons - such as easier lookup) we should consider ALSO referencing the VestingTerm obj id too.