AuthenticationId clarification

[bigludo7]

Problem description
AuthenticationId example and length suggests UUID but no format constraint, no indication of uniqueness guarantees:

    AuthenticationId:
      type: string
      description: unique id of the verification attempt the code belongs to.
      maxLength: 36
      example: ea0840f3-3663-4149-bd10-c7c6b8912105

Possible evolution
Provide a format.

Alternative solution

Additional context

[ChinaUnicomXiaoDongrui]

@bigludo7 hello Robert, it seems we've got in touch again. I saw that the OTP API has a stable version. Congratulations! I'm very interested in your OTP API. There's a question I think we can discuss.

I found that our API is provided by operators with the ability to generate verification codes and code verifications. This is a great idea. Operators offer rich functions to customers, but how to ensure the security of customers (such as banks), for example, we have a bank customer. We provide verification code generation and verification for the bank to help people complete bank transactions (such as payments or withdrawals). This will be a huge risk and responsibility for the operator. I have no idea how I was thinking about generating verification codes for customers at that time.

This is my consideration. I really hope to discuss the details of this API with you. I wonder if you understand what I want to say. I hope to get your reply. Thank you

At the same time, whether apis with verification codes can be added can give customers more choices

Since I don't have your email address, I'm here to discuss with you. Meanwhile, Christmas is coming soon. Wish you a happy holiday