-
assigned issue to
- changed status to open
Basic, Messages - Schema "backwards compatibility" statement not actionable
Issue #311
resolved
It's not the place of the standard to make statements about non-standard behaviors. The following statement is not actionable by Connect implementers:
If the value of this parameter is omitted, or not "openid", the response may be a proprietary schema to support backwards compatibility. Custom scheme names and responses are out of scope for this specification.
As this statement adds no value to implementers, it should be deleted.
Comments (2)
-
-
reporter - changed status to resolved
Fix
#311: Basic, Messages - Schema "backwards compatibility" statement not actionable - Log in to comment