Nick Kramer, a PM on the Avalon team, bursts into the blogging scene with his first post being about Avalon's various naming conventions. The primary need for these conventions is for discoverability through reflection. The primary “client” that needs to reflect on types using these patterns is the Avalon serialization architecture itself. However, these patterns can also be leveraged by design time tools to discover interesting aspects about Avalon based types.