Version Naming Convention / Namespaces

We had wanted to use a version number naming convention to indicate
successive versions of user data types, for example if we define an Avro
"Employee" record we intended to name this:

Employee.V1_0
Employee.V1_1

to indicate successive changes to the schema.

However we have found that some of the Avro tooling (for example, code
generation, and naming of embedded schema types) interprets the "." to be a
namespace separator, and generates a namespace of "Employee" and a record
name of "V1_0", which obviously is not what we intended.

Have others encountered this issue - is there a way around it? Or is there
an alternative common convention for version naming in Avro?

Thanks.