stuartpb
commented
6 years ago Previously discussed in opws/opws-dataset#149: before the form design for this stuff, there was a single accepts field that listed accepted combinations of factors.
Maybe a 2D proofs (or factors or something) array, where each list within the list describes a valid combination of inputs that's acceptable? Or bring back accepts, like the account.accepts structure, but have it be submit.accepts (or also.accepts), and two-dimensional?
One of the issues with this is that, frequently, the alternative list is just a completely separate list of factors that may not have tokens in the schema. (This is especially the case for many of the further.requirements notes listed in https://github.com/opws/opws-schemata/issues/1#issuecomment-344449391.)
This is one of the classes of note being pulled out of profiles with https://github.com/opws/opws-schemata/issues/1#issuecomment-344449391 (see also opws/opws-dataset#309):
password.reset.flow.request.form.notes("Also accepts a combination of first name, last name, Social Security number, and date of birth.")username.reminder.request.form.notes("Also accepts a combination of first name, last name, Social Security number, and date of birth.")password.reset.flow.request.form.notes("Also accepts a combination of first name, last name, and credit card number.")