Update docs and implementation for Coordination Number about activelogin.identity HOT 3 OPEN

Month can't be 60 right? It's Month = 0 and Day = 60, I think.

We also need to update the CoordinationNumber test-data to include numbers with month=0 and day=60, and remove numbers with days > DaysInMonth.

We should be able to handle the hints as you suggest.

from activelogin.identity.

Also, I think there still is a missing requirement, but I am not sure if we can extract any more information from Skatteverket unless we want to end up on some list for blocked emails ;)

This is just an edge case, so maybe we can decide on it ourselves:

For a coordination day the valid MIN is 60.
For a coordination day the valid MAX is 60 + (DaysInMonth for month n). (where n is 1-12).
For a coordination day the valid MAX is ?? when month is 0.

Or have they actually confirmed that the only valid day is 60 if month is 0? I.e. can you know the day of birth, but not the month?

We can't be too strict here, because it could mean that we could parse a (potentially) valid coordination number as invalid, so without further input from Skatteverket I think we need to allow for any day number 60-91 if the month is 0.

from activelogin.identity.

Month can't be 60 right? It's Month = 0 and Day = 60, I think.

Correct!

We also need to update the CoordinationNumber test-data to include numbers with month=0 and day=60, and remove numbers with days > DaysInMonth.

Yes!

We can't be too strict here, because it could mean that we could parse a (potentially) valid coordination number as invalid, so without further input from Skatteverket I think we need to allow for any day number 60-91 if the month is 0.

I think you are right - After the numerous emails just to get here I'm quite sure this isn't specified. I agree that we should not be too strict here.

from activelogin.identity.