KhronosGroup / KhronosGroup/KSCAF_DocRequirements

Queries/Comments related to section 1.2 of KSCAF_DocRequirements

Open
#34 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
CSS
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

This document, referred to as the KSCAF Requirements document which states requirements that must be strongly and implemented when designing a Khronos API which it to be used for SC software development. A reason would normally need to be recorded as to why a particular requirement was not implemented.

--> 'Strongly' word seems to misplaced. Hence the first sentence needs to be rephrased.
--> 'rationale' word is more suitable than 'reason'.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing section 1.2 of the KSCAF Requirements document. Rephrase the first sentence so “strongly” is correctly placed, and replace “reason” with “rationale.” The work is done when both requested wording changes are reflected in the document.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.