If you delete something, like Asset, that has 'children' of various types, delete for the children does not trigger because:

• 'you already know' so it would be inefficient for you
• and that would be slow, in some cases extremely slow.

So:

When you delete an asset:

• the Specifications on the asset will be deleted,
• but there will be no 'Asset Specification delete' trigger triggered.
• If the asset has child assets, the Asset Delete trigger won't be called 10,000 times; won't be called on the 10,000 children that are being deleted at the same time.

Compare this to if you go into an asset and delete the specification,

• an 'Asset Specification Delete' trigger will be triggered.

The delete trigger is called after the delete of the item, asset, has been completed.