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
jricher opened this issue
Sep 5, 2015
· 2 comments
Labels
coreRelated to (original UMA1) core spec scope; may use obsolete languageeditorialRelated to non-normative text errorsrsrc-regRelated to resource registration (or the original UMA1 resource reg spec)V1.0.1
This same text occurs in §3, §3.2, §3.3.1, and §3.3.2.
xmlgrrl
added
core
Related to (original UMA1) core spec scope; may use obsolete language
rsrc-reg
Related to resource registration (or the original UMA1 resource reg spec)
V1.0.1
editorial
Related to non-normative text errors
and removed
V1.0.1
labels
Sep 5, 2015
But actually, in these cases, the text is technically correct as written. This is because the phrase "as determined through RPT status checking" applies only to the "invalid RPT" and "insufficient authorization data associated with an RPT" options.
I think I can improve the feel of all of these sentences and take away the urge to comma-ize by adding "...or has an invalid RPT, or insufficient...".
coreRelated to (original UMA1) core spec scope; may use obsolete languageeditorialRelated to non-normative text errorsrsrc-regRelated to resource registration (or the original UMA1 resource reg spec)V1.0.1
The following sentence should probably use the oxford comma for clarity:
Replace with:
Other parts of the specification should use it, also, but this is the one example that jumped out.
The text was updated successfully, but these errors were encountered: