bian-official / public Goto Github PK

Hello again. As stated in other issue, I am using version 11 to generate contract tests using your standard, and I imported your OpenAPI definitions in and used the schema objects to validate API request bodies and responses, and none of your schema objects have any required properties--this results in AJV just returning TRUE for all tests.

I see you have the required properties parameters, are you planning on adding them to your schema? Or do you have any other machine-readable schema that can be used to automate the setting of these properties? Without knowing the standard, the work would be impossible for me.

In the same file CurrentAccount.yaml
There is two different spellings for Bill. One 1 and two l, can there be some consistency please
example:
BillPayMandateReference:
BilPayMandateSettings:

Do you happen to have any Spectral Rules for BIAN? I am going to produce a ruleset for all your standards and wanted to make sure there wasn't already a set before I did the work.

why is there an extra n? in processing?

Hello there. I am working on some API contract validation demos for Wells Fargo, and after importing all of the version 11 OpenAPIs into a workspace and producing contract tests from them, I am noticing a number of OpenAPI validation issues:

      type: string
      format: string

and

      type: string
      format: object

Just to highlight a couple. Upon import into Postman, these errors are severe enough to cause it to fail. I have cleaned them up, and tested them to make sure they are valid OpenAPI specs.

I am happy to submit a pull request against your repo with the fixes, but I don't want to do the work if it won't be used. Let me know if you are interested.

I notice you are using OpenAPI 3.0.1, any plans to support 3.1? As it supports the latest JSON Schema standard, it will really make a difference when it comes to testing BIAN-compliant APIs. I am happy to help, feel free to reach out if you need support from Postman or the OpenAPI Initiative.

Elsewhere this is Capitalised, here for some reason it is lowercase

Here is an example https://app.swaggerhub.com/apis/BIAN-3/CustomerBehaviorInsights/11.0.0 . This has 4 CRs and 3BQs. The diagram view https://bian.org/servicelandscape-11-0-0/views/view_36656.html has 6 CRs and 11 BQs. Version 11.0.0.

Is there a reason why some Payment endpoints differ?
In Current Account you have '/Payment/Initiate': while in Corporate Current Account its '/Payments/Initiate':

There doesnt seem to be a standardisation for this across multiple files. Why?