Order of Headers/Paths/Queries

[simonmeyerm]

Would it makes sense to order the Headers, Paths and Queries in a defined order for all APIs?

bLink suggestion would be to arrange it alphabetically with:

• Headers required
• Headers optional
• Paths required
• Paths optional
• Queries required
• Queries optional

For bLink the order would look like this:

• bLink Headers required
• bLink Headers optional
• General Headers required
• General Headers optional
• Paths required
• Paths optional
• Queries required
• Queries optional

[juergen-petry]

Feedback on behalf of UBS: We have a neutral view: not against, nor in favor of it, but would support this proposal since it’s a purely cosmetic change.
This is a matter of preference and other ordering criteria are equally valid.

[svenbiellmann]

All SFTI API specifications will follow the proposed naming conventions. For more details please see here: https://github.com/swissfintechinnovations/.github/wiki/Naming-Conventions. Therefore this issue will be closed.