[Editorial] Inconsistent terminology: "Aggregate Claim" / "Aggregated Claims" / "Claim Set"

Open Beginner friendly
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Start by searching the Draft 04 text for “Aggregate Claim,” “Aggregated Claims,” “claim sets,” and “signed claims set,” then compare each use with the defined-term wording described in the issue. Done means the RP-facing artifact has one consistent defined term and “Claim Set” capitalization is used consistently throughout the document.

Written by the indexing model from the issue text.

Description

From a security/privacy/interoperability/consistency review of openid-connect-claims-aggregation-1_0, Draft 04, checked against its normative references and RFC 9700 (OAuth 2.0 Security BCP).

Claims Verification uses "Aggregate Claim" and "Aggregated Claims" interchangeably; elsewhere "claim sets" / "signed claims set" appear uncapitalized although "Claim Set" is a defined term.

Proposed fix

  • Pick one defined term for the RP-facing artifact and use the defined "Claim Set" capitalization consistently.
Dominant language
HTML
Stars
0
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openid/claims-aggregation

All issues in openid/claims-aggregation

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.