-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancements to Banking documentation #395
Comments
I question whether the description should have this sort of info in it. Does a boolean need an explanation? For the "if absent" parts it could be just as well served with the openapi |
That's a good point @perlboy. Most Booleans do have simpler descriptions than that one though, and some have additional qualifying text for a default. We could consider simplifying as we go through, but would need to be more careful with any rewording to ensure the interpretation doesn't change and further guidance on specific fields is not needed. Do you think changing this description for the
to this, would be an improvement?:
Many Banking fields do have a
|
The changes incorporated with this issue include:
Also note:
|
The Banking Candidate Standards included a number of minor documentation enhancements that can be incorporated into the main Standards without changing meaning.
Aligning these changes would improve the binding Standards and make any comparison between the two versions more straightforward.
For example, the current statements:
would become:
OPEN
,CLOSED
orALL
. If absent thenALL
is assumedtrue
if extended information is available using the transaction detail endpoint.false
if extended data is not availableThe text was updated successfully, but these errors were encountered: