[S2S]: Property naming convention
Open
Nobody has claimed this yet.
ready-for-PR
server-to-server
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Throughout the spec we should be consistent in naming of object properties.
- OpenID4VCI uses snake_case for it's properties
- APIs and coding languages more commonly use camelCase
Probably, we should use snake_case, as any harmonized property names will need to be done that way anyways.
Issue to track discussion and making the spec consistent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the OpenID4VCI specification and cataloging object-property names that use snake_case or camelCase. Resolve the naming convention through the tracked discussion, then make the specification consistent and verify that no property names remain mixed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100