At Google we are starting to release more guidelines for conveying creator/author/person information but the lack of a type for account makes the markup awkward.

There has been previous discussion for something like a user account or social profile account or whatever we want to scope it (see #267). There is no representation AFAIK for something like that in schema.org. Representationally this leads to problems figuring out how to represent domain-specific information that is separate from the real-world person that the account/profile represents. Some examples:

• How do we represent when a profile was created? That's not when the person was created. At Google we are recommending hanging that on a ProfilePage node (so the page implicitly is created when the account is created) but that is not ideal.
• Naming is confusing distinguishing between a system handle and a real world name. There is little specification for whether name (or alternateName) represents the canonical representation of the thing in its system context or something more objective.
• Ambiguity in entity type. Some systems cannot tell whether something is a Person or Organization and yet many of our author properties have to use a specific type to be valid.