BNF Grammar does not describe evolutions
justinaray opened this issue · comments
Need to correctly describe evolutions for version compare in NPM, yarn, etc.
BNF probably is not the best way to describe evolutions. We will most likely need to write a reference implementation for language implementers. Or perhaps we can create a micro-service for PokeVer, call it PokeVer-as-a-service (PaaS; checked, it's not an existing acronym). Also we can add authentication and machine learning so that based on previous evolutions software engineers can know how quickly they should be iterating for maximum productivity.
The machine learning angle is intriguing as it could also be used to discover new evolutions and series of Pokemon to keep the spec ever growing. Though, this would require the series (or another type of bin) to be the major version identifier.