Yet other editorial fixes for ISO adoption
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by Kosuke Koiwai (Kosuke Koiwai) on 2025-11-27
At the Nov26 meeting, Nat asked me to create a new issue for the comments I made on https://bitbucket.org/openid/fapi/commits/64d87a973f6bb14f018ed8fd391957b8aa1a4903
FAPI_1.0/openid-financial-api-part-1-1_0.md
- Line 64-100: Hyphens at the beginning of spec names should be omitted.
- Line 301:
RFC4122 UUIDshould beRFC 4122 UUID(need a space) - Line 311:
BCP195should beBCP 195(need a space)
FAPI_1.0/openid-financial-api-part-2-1_0.md
- Line 69-102: need spaces after
RFCandISOin the spec names in the normative references - Line 817-853: need spaces after
RFCandISOin the spec names in the bibliography - The same (need spaces between RFC/BCP/ISO and numbers) goes to the references within the document
Bitbucket status: new
Bitbucket origin: issue 845
Contributor guide
No contributing guide indexed for this repository
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 with FAPI_1.0/openid-financial-api-part-1-1_0.md and FAPI_1.0/openid-financial-api-part-2-1_0.md, reviewing the cited line ranges and references. Apply the listed spacing and hyphen corrections consistently in normative references, bibliographies, and in-document references, then check both files for remaining RFC, BCP, and ISO names without spaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100