Define exact steps/algorithms instead generic references to "Protocol Bindings" spec
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
In many algorithms we are referring to the Protocol Bindings specs.
From an algorithm we need to point to exact steps or algorithms from another spec.
If the referred spec doesn't have that, we need to figure that out at least for the HTTP protocol binding and include the steps in the relevant places.
After the Protocol Bindings are updated, we can later refer to algorithms there.
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 algorithms that refer generically to the Protocol Bindings specifications, then compare them with the HTTP protocol binding. Done means each reference points to exact steps or algorithms, with missing HTTP steps included where the binding does not define them.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100