Inconsistency of data types in various schema

[nils-work]

Description

There are minor differences in how some header types are defined in the Register API Specification, compared to Banking and others.

Area Affected

For example:

Register: Get Data Holder Brands

x-v, x-min-v, page and page-size appear as integer:

The corresponding sample reflects the integer type:

Banking: Get Accounts

x-v and x-min-v appear as string, while page and page-size appear as PositiveInteger.

The corresponding sample reflects the string type:

Change Proposed

Agree on the most appropriate convention and apply it consistently.

[biza-io]

Biza supports the alignment of specifications between the CDR Data APIs and the Register. Specifically we recommend aligning as follows:

1. Adopt page and page-size as PositiveInteger which we believe to be most appropriate and for which error handling behaviour is nuanced based on this (Invalid Field vs. Invalid Page)
2. The headers should be aligned to a string as this is aligned to the upstream standard governing headers (ie. HTTP 1.0/1.1).

[nils-work]

Standards version 1.25.0 has now been published, incorporating this change.