Having a lot of meaningless options doesn't make meta data any more clear. Well, they are not meaningless, but their role is fully fulfilled by other options (Author and Maintainer fields in this particular case).
The use case for the Author field is that if Author wants to be contacted, (s)he leaves email. That's it. This use case should be described in the meta-data along with the format that are expected to be recognized by the software:
Author: anatoly techtonik
Here the field content defines its type - it's like duck typing for specification, which make specifications more pythonic.
Is it good?