Minor changes (typos, clarifications, ..)

[Nicolas Aillery]

‌

typo:
-
MANDATORY. Statement made by the User Questioning.
+
MANDATORY. Statement made by the Questioned User.


typo:
-
<section title='Proccessing the Response'>
+
<section title='Processing the Response'>


typo:
-
<section title='Proccessing the Polling Resquest'>
+
<section title='Processing the Polling Request'>


typo (in <section title='User Questioning Polling Endpoint'>):
-
<t>In order to detect that User Questioning Response is ready, the Client MUST request the User Questioning Polling Endpoint.
If User Questioning Response is ready, it will be returned in the response.
+
<t>In order to detect that the User Questioning Response is ready, the Client MUST request the User Questioning Polling Endpoint.
If the User Questioning Response is ready, it will be returned in the response. 


update:
-   
<date day='6' month='March' year='2017'/>
+
<date day='11' month='June' year='2020'/>


update:
-
<t>Copyright (c) 2017 The OpenID Foundation.</t>
+
<t>Copyright (c) 2020 The OpenID Foundation.</t>


new title:
-
<section title='Successful Polling Response'>
+
<section title='Successful Response'>


new title:
-
<section title='Successful Response with User Questioning Response'>
+
<section title='Successful Response'>


new wording:
-
The parameters are included in the entity-body of the HTTP 200 OK
using the "application/json" media type as defined by <xref target="RFC4627"/>. The
+
As defined by <xref target="RFC4627"/>, the parameters are included in the entity-body of the HTTP 200 OK using the "application/json" media type. The


new wording:
-
The parameters are included in the entity-body of the HTTP 200 OK
using the "application/json" media type as defined by <xref target="RFC4627"/>. The
+
As defined by <xref target="RFC4627"/>, the parameters are included in the entity-body of the HTTP 200 OK using the "application/json" media type. The


new wording:
-
The parameters are included in the entity-body of the HTTP POST
using the "application/json" media type as defined by <xref target="RFC4627"/>. The
+
As defined by <xref target="RFC4627"/>, the parameters are included in the entity-body of the HTTP POST using the "application/json" media type. The


new pagination:
-
{
"user_statement_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImt
pZCI6ImsyYmRjIn0.eyJxdWVzdGlvbl9pZCI6Ijk4NGRjYzdkM2Q0ZDRiMGY5Zj
gwMjJlMzQ0ZjkiLCJpc3MiOiJodHRwczovL3NlcnZlci5leGFtcGxlLmNvbSIsI
mF1ZCI6WyJzOFYzd204SVhNVzZUYm9helhaWCJdLCJzdWIiOiJnMTE3WUJ0Q1pP
M21BS1BRS1A4byIsInVzZXJfaWQiOiIrMzM2MTIzNDU2NzgiLCJ1c2VyX2lkX3R
5cGUiOiJtc2lzZG4iLCJxdWVzdGlvbl9kaXNwbGF5ZWQiOiJXaGljaCBpcyAuLi
4_IiwiZGlzcGxheWVkX3N0YXRlbWVudHMiOlsiYmx1ZSIsInJlZCIsInllbGxvd
yJdLCJzdGF0ZW1lbnQiOiJyZWQiLCJzdGF0ZW1lbnRfZGF0ZSI6MTMxMTI4Mjk3
NSwidXNlZF9hY3IiOiIyIiwidXNlZF9hbXIiOlsiQ0xJQ0tfT0siXX0.bbDeU13
rouABOOGrvIdQ4BN6GZtHvf1_oZEtGMrMoF9y2l66Dnyv_LL0eip2eCT56N7nH8
iACNoJawCG_O2nYfUfJTU8t-tu-MNLe9p69PtUQkxShFzvWXPQfri_OXQSs1zdt
Z5NNVUX0ulPLm7QOniNFvY4sHwAkci4V1Czj72FGsxcUsUS6KUJRY7B2znP5ykl
7m75iCp0Ydx72NshWCWzQxDfXPdQpuJoB96OXDuuukYIrOY1yZOqkUGE6AqPcmM
UJEWmT7OCHNi0Acsr0jU-fwxoAfYxQ641pW203PfVHXVRd06Ly0xHT3b50FM1jn
JM4tq98j78zu1cxVc2ww"

}
+
{
"user_statement_token":"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtp
ZCI6ImsyYmRjIn0.eyJxdWVzdGlvbl9pZCI6Ijk4NGRjYzdkM2Q0ZDRiMGY5Zjgw
MjJlMzQ0ZjkiLCJpc3MiOiJodHRwczovL3NlcnZlci5leGFtcGxlLmNvbSIsImF1
ZCI6WyJzOFYzd204SVhNVzZUYm9helhaWCJdLCJzdWIiOiJnMTE3WUJ0Q1pPM21B
S1BRS1A4byIsInVzZXJfaWQiOiIrMzM2MTIzNDU2NzgiLCJ1c2VyX2lkX3R5cGUi
OiJtc2lzZG4iLCJxdWVzdGlvbl9kaXNwbGF5ZWQiOiJXaGljaCBpcyAuLi4_Iiwi
ZGlzcGxheWVkX3N0YXRlbWVudHMiOlsiYmx1ZSIsInJlZCIsInllbGxvdyJdLCJz
dGF0ZW1lbnQiOiJyZWQiLCJzdGF0ZW1lbnRfZGF0ZSI6MTMxMTI4Mjk3NSwidXNl
ZF9hY3IiOiIyIiwidXNlZF9hbXIiOlsiQ0xJQ0tfT0siXX0.bbDeU13rouABOOGr
vIdQ4BN6GZtHvf1_oZEtGMrMoF9y2l66Dnyv_LL0eip2eCT56N7nH8iACNoJawCG
_O2nYfUfJTU8t-tu-MNLe9p69PtUQkxShFzvWXPQfri_OXQSs1zdtZ5NNVUX0ulP
Lm7QOniNFvY4sHwAkci4V1Czj72FGsxcUsUS6KUJRY7B2znP5ykl7m75iCp0Ydx7
2NshWCWzQxDfXPdQpuJoB96OXDuuukYIrOY1yZOqkUGE6AqPcmMUJEWmT7OCHNi0
Acsr0jU-fwxoAfYxQ641pW203PfVHXVRd06Ly0xHT3b50FM1jnJM4tq98j78zu1c
xVc2ww"

}


-
+
<author fullname='James Manger' initials='J.' surname='Manger'>
<organization abbrev='Telstra'>Telstra</organization>
<address>
<email>[e-mail]</email>
</address>
</author>


clarification on the user_questioning_polling_endpoint:
-
The URL of User Questioning Polling Endpoint MUST be configured as the value of <spanx style="verb">user_questioning_polling_endpoint</spanx>.
+
The URL of User Questioning Polling Endpoint MUST be configured as the value of <spanx style="verb">user_questioning_polling_endpoint</spanx>. The <spanx style="verb">user_questioning_polling_endpoint</spanx> MAY contain query parameters, but MUST NOT contain a fragment.


clarification on the MSISDN format:
-
    <xref target="E.164">E.164</xref> 
    is RECOMMENDED as the format of this Claim, 
    for example, <spanx style="verb">[phone]</spanx> 
    or <spanx style="verb">[phone]</spanx>.
+
    <xref target="E.164">E.164</xref> 
    is RECOMMENDED as the format of this Claim, with no bracket, space, or hyphen,
    for example, <spanx style="verb">[phone]</spanx>.


clarification on long polling:
-
The <spanx style="verb">Client_timeout</spanx> indicates how much time, in seconds, the Client will wait for a HTTP response. 
+
The <spanx style="verb">Client_timeout</spanx> indicates how much time, in seconds, the Client will wait for a HTTP response. This header can be used with OP that support long polling. As long polling is an optional feature for OP, the Client must be prepared that the OP ignores this header and responds right away.


clarification on <section title='Pending Response'>:
-
If the User Questioning Response is not ready, the Client will get a HTTP 304 Not Modified.
+
If the User Questioning Response is not ready, the Client will get a HTTP 304 Not Modified. The Client MUST repeat the polling request, until it receives either a successful response or an error. The Client MUST NOT repeat polling requests too rapidly. A waiting time of at least 1 second after the previous polling request was initiated is RECOMMENDED.


clarification on <section title='Client Notification Endpoint'>:
-
The User Questioning Response contains a <spanx style="verb">status</spanx> attribute that indicates if the User Questioning Response is successful or not.
+


clarification on the acknowledgement:
-
The acknowledgement MUST be a HTTP 200 OK. This HTTP response SHOULD be ignored by the OP.
+
The acknowledgement MUST be a HTTP 200 OK. This HTTP response SHOULD be ignored by the OP. If the response is not a HTTP 200 OK, the processing is up to the OP's implementer.


removal of inadequate examples:
-
The User Questioning Request is not valid. The request is missing a required parameter, 
includes an unsupported parameter value (other than grant type), 
repeats a parameter, includes multiple credentials, 
utilizes more than one mechanism for authenticating the client, 
or is otherwise malformed.
+
The User Questioning Request is not valid. The request is missing a required parameter, includes an unsupported parameter value, repeats a parameter or is otherwise malformed.


removal of inadequate examples:
-
The OP can use this error when it does not have a reachability identifier (e.g. MSISDN) for the Question User or when the reachability identifier is not operational (e.g. unsubscribed MSISDN).
+
The OP can use this error when it does not have a reachability identifier (e.g. MSISDN) for the Question User, when the reachability identifier is not operational (e.g. unsubscribed MSISDN or blocked account).

‌

[Bjorn Hjelm]

Approved.