On 4/1/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > How does that sound as a policy?
Sounds good to me. Based on that, I'll whip up a US SSN field, and I think that following this it will: 1. Validate the number of digits (9). 2. Validate that the number is not one which is known to be permanently invalid (there aren't many of these and they're easy to test for). And leave it at that. Sound good to everyone? Also, @Malcolm: in theory, a US SSN validator could tell which state/territory you were in when you applied for the number (which in most cases will be the state/territory in which you were born), but I don't think it needs to go that far; we'll let the Nordic SSN arms race continue unchallenged ;) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
