DynamoDB keys vs CloudFormation examples

I'm trying to reconcile this:

``` python
class PrimaryKey(AWSProperty):
props = {
'HashKeyElement': (Element, True),
'RangeKeyElement': (Element, False),
}

class Table(AWSObject):
type = "AWS::DynamoDB::Table"

props = {
'KeySchema': (PrimaryKey, True),
'ProvisionedThroughput': (ProvisionedThroughput, True),
'TableName': (basestring, False),
}
```

with:

``` json
"KeySchema" : [
{
"AttributeName" : "Album",
"KeyType" : "HASH"
},
{
"AttributeName" : "Artist",
"KeyType" : "RANGE"
}
],
```

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-dynamodb-keyschema.html

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html#cfn-dynamodb-table-keyschema

This doesn't seem to match up - is it wrong, out of date or am I misunderstanding something?

Start with the PrimaryKey and Table definitions shown in the issue, then compare their KeySchema shape with the linked AWS CloudFormation examples. Determine whether troposphere's schema or the CloudFormation examples are outdated, and document the agreed correction with a regression check if the project identifies one.

Written by the indexing model from the issue text.