Notifications optional and required fields

Hello! I want to parse json, which you send in notifications v2, but have some questions about required and optional fields (actually I may do all the fields, which are non obvious for me optional, but that's not suitable).

It would be really amazing if you will update your docs with this info! And it would be cool if you'll add some examples of the whole notification structure (it would be more convinient) with different types (and refer to example for concrete field like here is "revocationDate", it appears in case of "REVOKE" event and may be found here: <example reference> - it would be perfect!)

Main questions are:

• does signedRenewalInfo always appear here or it doesn't if it's consumable notification?
• does bundleId either always appear or it may not if it is deleted somewhere somehow?
• do i understand right that "empty subtype" doesn't mean empty string but means absence of field in json?
• does autoRenewStatus always appear here or it may be absent?
• do purchaseDate and originalPurchaseDate from here always appear or there are some cases (revocation maybe) when they may be missed?
• does transactionId field always appear or there are some exceptions (revocation?)?
• does inAppOwnershipType from here always appear?
• is quantity (from the same struct) required field?
• is webOrderLineItemId (from the same struct) a required field?