Description: ------------ How should we handle special cases of AF/AA/AE military "states" for the region() method? One easy solution would be to add the "AF", "AA", "AE" as supported "regions" in the region() method, but at the same time they are not actual regions, just proxy values. Should we add a postalRegion() to all Validate_* country-based validation packages that would handle such validation?

There are a bunch of extra abbreviations also Extras -------- AMERICAN SAMOA AS DISTRICT OF COLUMBIA DC FEDERATED STATES OF MICRONESIA FM GUAM GU MARSHALL ISLANDS MH NORTHERN MARIANA ISLANDS MP PALAU PW PUERTO RICO PR VIRGIN ISLANDS VI Military "State" Abbreviation ------------------------------ Armed Forces Africa AE Armed Forces Americas (except Canada) AA Armed Forces Canada AE Armed Forces Europe AE Armed Forces Middle East AE Armed Forces Pacific AP I think these should just be added to the region function - I also think we should include the full version of the region name - especially for states - so that if we're checking "Wyoming" it returns true since it is a valid state. what do you think?

I think the abbreviations recognized by the USPS should all be included. http://www.usps.com/ncsc/lookups/usps_abbreviations.html Maybe an option for validating against Military "States" i.e. function region($region, $military = false) could be included, as even the USPS separates them into their own special group, but it would be simpler to just validate all. To timmyg - Based on how postalCodeByRegion works, it would be foolish to have a function that validates "Iowa" unless we add "Iowa" to the cases in postalCodeByRegion. I think it would be easier to have a function that validates region_name and maybe a function that can take a valid region_name and return the state_code (or vice versa).