Naming conventions for interfaces vs schemas in documentation
the schema doc examples create an interface for a schema directly below it with the same name - I think that is messing with other code that is trying to use the schema to make an arbtrary. What's the naming convention for interfaces vs schemas?
