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
Telephone was replaced by phone:PhoneNumber but telephone is still mentioned in some places in the doc:
2.3.3: "Email and telephone number based recipient identifier authentication are up to the relying party..."
6.2.4: "The resource server MAY respond with 400 BAD_REQUEST to reject data that is known immediately to not be acceptable by the platform, e.g. to reject a "telephone" property if the resource server cannot validate telephone numbers."
6.2.4 Example 12
The text was updated successfully, but these errors were encountered:
The IRI for phone is a little odd, as it refers to the same IRI as the type PhoneNumber. What is the intentionality behind the change from schema:telephone to an OB-scoped phone property?
The OB 2.0 spec required that the phone number be in E.164 format, but the 3.0 spec is less specific about how the string "representing a phone number" should be formatted. See phone.
Telephone was replaced by phone:PhoneNumber but telephone is still mentioned in some places in the doc:
2.3.3: "Email and telephone number based recipient identifier authentication are up to the relying party..."
6.2.4: "The resource server MAY respond with 400 BAD_REQUEST to reject data that is known immediately to not be acceptable by the platform, e.g. to reject a "telephone" property if the resource server cannot validate telephone numbers."
6.2.4 Example 12
The text was updated successfully, but these errors were encountered: