Joshua Hannan

Thanks for the feedback @bluesign! I did move the standard views back into `MetadataViews` and moved the `Resolver` and `ResolverCollection` interfaces into the `ViewResolver` contract. I also just pushed some...

@bjartek yep, it is in both proposals already: https://github.com/onflow/flow-nft/pull/126/files#diff-0aa93a6098e86167b39c0a5202f7cbdc953e8bd7ee949b594c2d2695b67372a8R120-R125

Just want to leave a note here that it might not be a good idea to include [this default implementation](https://github.com/onflow/flow-nft/blob/3acffe2472a3d2792a05a166e8177af3c8176ab8/contracts/NonFungibleToken-v2.cdc#L112-L114 ) because existing projects who upgrade might forget to include...

Good suggestions! For the first one, I think that would be nice, but since we don't have nested type requirements any more, we can't enforce that certain events are included...

Addressed this in #163

Based on the poll [here](https://forum.onflow.org/t/streamlined-token-standards-proposal/3075/54?u=flowjosh), it looks like there is a decent amount more support for this change than for event inheritance. So we should probably move forward with a...

I just thought of something. We've thought about including type information and important metadata views in the standard events. If we have the interfaces emit the events, will that information...

oh, I was assuming that we'd put the events in the `Receiver` and `Provider` interfaces, but it sounds like you're saying they should be in the `Vault` and `Collection` interfaces...

@bluesign have you gotten the chance to start on this FLIP yet? Do you need any help?

closing this PR now because we have these features in #321