A class called "JobServer" in the schema is sent as "jobserver" over the wire.  Ken says this is due to the behavior of the qmf code generator.

I think this is a bad practice, though it's not a terrible state of affairs, and it's apparently difficult to fix now.

As to why it's bad: it recently served as the background for a bug in mint.  In an effort to recapture the original class names, mint had logic in place to take the value of ClassKey.getClassName() and capitalize its initial letter so it would match the metadata, which contains classes by their as-written (capitalized) form.

This worked until JobServer came along.  It has a cap in the middle.  (I've now introduced a lowercased index of classes to use instead, so the problem is addressed in a general fashion.)

Nonetheless, mangling class names causes unnecessary confusion for implementors.