34. Formally reserve keys for private 'in-house' use Proposal:
For in-house, non-CPAN use, it would be nice to be able to extend META.yml to contain extra keys and data, but any extensions that we choose to make may one day clash with an official key not yet introduced. For this reason I'd like to formally define the acceptance of 'x-' prefixed key names. Clients that validate META.yml should ignore any and all keys starting with 'x-' and those keys should be formally declared as never being used in future extensions to the spec. Comments: * This seems like a fairly good way to allow experimentation with new features without changing the spec, and pretty non-controvertial in general --Adam K * I thought this was what key names containing a capital letter did? CSJewell
