CF implementation assumes all dictionary values are strings

[bdrister]

This is not necessarily the case; for instance, a quantity field might reasonably be an integer (and e.g. the Ruby version will happily generate such integer values in the plist).

Need to decide whether this is something that we are willing to stand behind as a requirement. Either the generators need to be updated to only generate strings, or the validators need to be updated to use the strings out of the XML tags instead of the parsed plist.