You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description
There is some inconsistency between the definition of an AppId here in CAMARA NBI, and AppId in GSMA EWBI. Here is it a UUID, but in EWBI it is a string, specifically ^[A-Za-z][A-Za-z0-9_]{7,63}$.
Expected behavior
Identifiers for the same thing should be consistent between NBI and EWBI, otherwise we'll get into messy conversions back and forth.
Alternative solution
Additional context
This needs further discussion on which approach to use, and how we can coordinate keeping these two APIs in sync given their different governing bodies.
The text was updated successfully, but these errors were encountered:
gainsley
added
the
correction
Suggesting corrections of API specification or indicating misalignment with API design guidelines
label
Jun 7, 2024
Problem description
There is some inconsistency between the definition of an AppId here in CAMARA NBI, and AppId in GSMA EWBI. Here is it a UUID, but in EWBI it is a string, specifically
^[A-Za-z][A-Za-z0-9_]{7,63}$
.Expected behavior
Identifiers for the same thing should be consistent between NBI and EWBI, otherwise we'll get into messy conversions back and forth.
Alternative solution
Additional context
This needs further discussion on which approach to use, and how we can coordinate keeping these two APIs in sync given their different governing bodies.
The text was updated successfully, but these errors were encountered: