There isn't a Twitter equivalent. You'll have to accept the fact that using the Twitter specific meta tags will break validation or lay a glimmer of hope in the following snippet:
[...] If you're already using OpenGraph to describe data on your page, it’s easy to generate a Twitter card without duplicating your tags and data. When the Twitter card processor looks for tags on your page, it first checks for the Twitter property, and if not present, falls back to the supported Open Graph property. This allows for both to be defined on the page independently, and minimizes the amount of duplicate markup required to describe your content and experience.
Their example follows on with this:
<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@nytimesbits">
<meta name="twitter:creator" content="@nickbilton">
<meta property="og:url" content="http://bits.blogs.nytimes.com/2011/12/08/a-
twitter-for-my-sister/">
<meta property="og:title" content="A Twitter for My Sister">
<meta property="og:description" content="In the early days, Twitter grew so
quickly that it was almost impossible to add new features because engineers
spent their time trying to keep the rocket ship from stalling.">
<meta property="og:image" content="http://graphics8.nytimes.com/images/2011/12/
08/technology/bits-newtwitter/bits-newtwitter-tmagArticle.jpg">
So while you will still use Twitter meta tags, the validation report will a tad less broken because you're using some Open Graph tags that should pass through. Provided you do include that namespace that accounts for the OGP tags.