You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Benedikt Ritter <br...@apache.org> on 2017/02/12 15:54:26 UTC
[VALIDATOR] Release 1.5.2?
Hello Sebb,
Are you about to create an RC for 1.5.2? If not, please let me know when you’re finished with your latest changes. I’d like to push out a new release soon.
Thank you!
Benedikt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VALIDATOR] Release 1.5.2?
Posted by Benedikt Ritter <br...@apache.org>.
> Am 12.02.2017 um 19:01 schrieb sebb <se...@gmail.com>:
>
> On 12 February 2017 at 15:54, Benedikt Ritter <br...@apache.org> wrote:
>> Hello Sebb,
>>
>> Are you about to create an RC for 1.5.2? If not, please let me know when you’re finished with your latest changes. I’d like to push out a new release soon.
>
> I'm working towards getting it ready for a new release.
> Another few days at most, I hope.
>
> Whether the RM is me or you, I don't mind.
If you’re up for it, please go ahead.
>
> Though maybe it needs to be 1.6 rather than 1.5.2?
Looking at the Clip report, this looks like a 1.6 to me. I’m changing the version in svn and lira.
Benedikt
>
>
>
>> Thank you!
>> Benedikt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VALIDATOR] How to handle credit card number length (Was:
[VALIDATOR] Release 1.5.2?)
Posted by Benedikt Ritter <br...@apache.org>.
> Am 13.02.2017 um 10:45 schrieb sebb <se...@gmail.com>:
>
> On 13 February 2017 at 08:27, Benedikt Ritter <britter@apache.org <ma...@apache.org>> wrote:
>>
>>> Am 13.02.2017 um 01:36 schrieb sebb <se...@gmail.com>:
>>>
>>> On 12 February 2017 at 18:01, sebb <se...@gmail.com> wrote:
>>>> On 12 February 2017 at 15:54, Benedikt Ritter <br...@apache.org> wrote:
>>>>> Hello Sebb,
>>>>>
>>>>> Are you about to create an RC for 1.5.2? If not, please let me know when you’re finished with your latest changes. I’d like to push out a new release soon.
>>>>
>>>> I'm working towards getting it ready for a new release.
>>>> Another few days at most, I hope.
>>>
>>> I have come to a stop for now.
>>>
>>> There are some requests to update the CreditCardValidator which could
>>> perhaps be done, but it's difficult getting definitive information.
>>>
>>> Should we be as strict as possible with lengths, or should we allow a
>>> range of lengths even if there don't seem to be any cards with all of
>>> them yet?
>>>
>>> The Discover network is also a bit tricky as it includes many other cards.
>>> Also in some areas it includes additional cards, e.g. China Union Pay,
>>> which are handled independently elsewhere.
>>>
>>> How should these be handled?
>>
>> I think we should be as strict as we can be on basis of the available documentation. Better reject something that is valid and let users build their custom validator on top of ours than silently accepting invalid cards, causing hard to find bugs in client code.
>
> The code cannot know which actual cards are in use; that has to be
> done by the issuer or the processing network.
>
> However it can ensure that the number is possibly valid, by validating
> the syntax, length and check digit.
>
> There are now generic validators which validate syntax, length and the
> check digit only.
> And it is now possible to build additional validators without needing
> to use REs.
>
> But I'm wondering what is the point of the IIN checks?
> If these are too strict, they will reject valid cards, possibly
> preventing a sale?
> If they are too lax, they will allow invalid cards, but these will be
> rejected later
> Maybe we need to ask for some use cases from the people wanting updates.
One way or the other there will be users complaining that either we rejected valid cards or we did not reject invalid cards… :-) Don’t know which option is better.
Benedikt
>
>> Benedikt
>>
>>>
>>>> Whether the RM is me or you, I don't mind.
>>>>
>>>> Though maybe it needs to be 1.6 rather than 1.5.2?
>>>>
>>>>
>>>>
>>>>> Thank you!
>>>>> Benedikt
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <ma...@commons.apache.org>
> For additional commands, e-mail: dev-help@commons.apache.org <ma...@commons.apache.org>
Re: [VALIDATOR] How to handle credit card number length (Was:
[VALIDATOR] Release 1.5.2?)
Posted by sebb <se...@gmail.com>.
On 13 February 2017 at 08:27, Benedikt Ritter <br...@apache.org> wrote:
>
>> Am 13.02.2017 um 01:36 schrieb sebb <se...@gmail.com>:
>>
>> On 12 February 2017 at 18:01, sebb <se...@gmail.com> wrote:
>>> On 12 February 2017 at 15:54, Benedikt Ritter <br...@apache.org> wrote:
>>>> Hello Sebb,
>>>>
>>>> Are you about to create an RC for 1.5.2? If not, please let me know when you’re finished with your latest changes. I’d like to push out a new release soon.
>>>
>>> I'm working towards getting it ready for a new release.
>>> Another few days at most, I hope.
>>
>> I have come to a stop for now.
>>
>> There are some requests to update the CreditCardValidator which could
>> perhaps be done, but it's difficult getting definitive information.
>>
>> Should we be as strict as possible with lengths, or should we allow a
>> range of lengths even if there don't seem to be any cards with all of
>> them yet?
>>
>> The Discover network is also a bit tricky as it includes many other cards.
>> Also in some areas it includes additional cards, e.g. China Union Pay,
>> which are handled independently elsewhere.
>>
>> How should these be handled?
>
> I think we should be as strict as we can be on basis of the available documentation. Better reject something that is valid and let users build their custom validator on top of ours than silently accepting invalid cards, causing hard to find bugs in client code.
The code cannot know which actual cards are in use; that has to be
done by the issuer or the processing network.
However it can ensure that the number is possibly valid, by validating
the syntax, length and check digit.
There are now generic validators which validate syntax, length and the
check digit only.
And it is now possible to build additional validators without needing
to use REs.
But I'm wondering what is the point of the IIN checks?
If these are too strict, they will reject valid cards, possibly
preventing a sale?
If they are too lax, they will allow invalid cards, but these will be
rejected later
Maybe we need to ask for some use cases from the people wanting updates.
> Benedikt
>
>>
>>> Whether the RM is me or you, I don't mind.
>>>
>>> Though maybe it needs to be 1.6 rather than 1.5.2?
>>>
>>>
>>>
>>>> Thank you!
>>>> Benedikt
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
[VALIDATOR] How to handle credit card number length (Was: [VALIDATOR]
Release 1.5.2?)
Posted by Benedikt Ritter <br...@apache.org>.
> Am 13.02.2017 um 01:36 schrieb sebb <se...@gmail.com>:
>
> On 12 February 2017 at 18:01, sebb <se...@gmail.com> wrote:
>> On 12 February 2017 at 15:54, Benedikt Ritter <br...@apache.org> wrote:
>>> Hello Sebb,
>>>
>>> Are you about to create an RC for 1.5.2? If not, please let me know when you’re finished with your latest changes. I’d like to push out a new release soon.
>>
>> I'm working towards getting it ready for a new release.
>> Another few days at most, I hope.
>
> I have come to a stop for now.
>
> There are some requests to update the CreditCardValidator which could
> perhaps be done, but it's difficult getting definitive information.
>
> Should we be as strict as possible with lengths, or should we allow a
> range of lengths even if there don't seem to be any cards with all of
> them yet?
>
> The Discover network is also a bit tricky as it includes many other cards.
> Also in some areas it includes additional cards, e.g. China Union Pay,
> which are handled independently elsewhere.
>
> How should these be handled?
I think we should be as strict as we can be on basis of the available documentation. Better reject something that is valid and let users build their custom validator on top of ours than silently accepting invalid cards, causing hard to find bugs in client code.
Benedikt
>
>> Whether the RM is me or you, I don't mind.
>>
>> Though maybe it needs to be 1.6 rather than 1.5.2?
>>
>>
>>
>>> Thank you!
>>> Benedikt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VALIDATOR] Release 1.5.2?
Posted by sebb <se...@gmail.com>.
On 12 February 2017 at 18:01, sebb <se...@gmail.com> wrote:
> On 12 February 2017 at 15:54, Benedikt Ritter <br...@apache.org> wrote:
>> Hello Sebb,
>>
>> Are you about to create an RC for 1.5.2? If not, please let me know when you’re finished with your latest changes. I’d like to push out a new release soon.
>
> I'm working towards getting it ready for a new release.
> Another few days at most, I hope.
I have come to a stop for now.
There are some requests to update the CreditCardValidator which could
perhaps be done, but it's difficult getting definitive information.
Should we be as strict as possible with lengths, or should we allow a
range of lengths even if there don't seem to be any cards with all of
them yet?
The Discover network is also a bit tricky as it includes many other cards.
Also in some areas it includes additional cards, e.g. China Union Pay,
which are handled independently elsewhere.
How should these be handled?
> Whether the RM is me or you, I don't mind.
>
> Though maybe it needs to be 1.6 rather than 1.5.2?
>
>
>
>> Thank you!
>> Benedikt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VALIDATOR] Release 1.5.2?
Posted by sebb <se...@gmail.com>.
On 12 February 2017 at 15:54, Benedikt Ritter <br...@apache.org> wrote:
> Hello Sebb,
>
> Are you about to create an RC for 1.5.2? If not, please let me know when you’re finished with your latest changes. I’d like to push out a new release soon.
I'm working towards getting it ready for a new release.
Another few days at most, I hope.
Whether the RM is me or you, I don't mind.
Though maybe it needs to be 1.6 rather than 1.5.2?
> Thank you!
> Benedikt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org