Designing of Password Authenticated Key Exchange (PAKE) Schemes?
The definition of PAKE just suggests that one or more parties are exchanging keys with knowledge of a shared password that authenticates the exchanged key. There are definitely use-cases of PAKEs that extend beyond, say, a web application authentication process that requires registration. For example, there could exist two or more embedded systems with shared passwords built into the firmware during manufacturing but these systems want to exchange fresh keys for communication. There are PAKEs that do cover registration (e.g. SRP), but the "definition" of a PAKE does not really require a specification for a registration process.

Personally, I think PAKE authors should specify a password bootstrapping process, if possible! It could prevent implementors from rolling-their-own protocol extensions.