[
http://opensource.atlassian.com/projects/hibernate/browse/HV-491?page=com...
]
Hardy Ferentschik commented on HV-491:
--------------------------------------
Great idea. Any chance you want to contribute a patch ;-)
Here are some thoughts from my side. Maybe it would make sense to have a _Mod11_
constraint and as parameter we pass the mod11 algorithm type. If we go down this path it
makes sense to re-work our _CreditCardNumber_ constraint. It implements the Luhn algorithm
which is effectively Mod10. _CreditCardNumber_ can then use constraint composition.
In fact we could also just have one single _ModCheck_ constraint and implement the
different mod10 and mod11 algorithms there. WDYT?
Add support for MOD11 Algorithm
-------------------------------
Key: HV-491
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-491
Project: Hibernate Validator
Issue Type: Improvement
Components: validators
Reporter: George Gastaldi
It would be nice to add support for the MOD11 algorithm. It is described on
http://joselop.es/mod-11 or
http://en.wikipedia.org/wiki/MSI_Barcode#Mod_11_Check_Digit
and it is widely used on Brazil, such as CPF (Cadastro de Pessoa Física -
http://en.wikipedia.org/wiki/Cadastro_de_Pessoas_F%C3%ADsicas), CNPJ (Cadastro de Pessoa
Jurídica - National Registry of Corporations) and Título de Eleitor (Voter ID card)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira