KhronosGroup / KhronosGroup/KSCAF_DocRequirements
Queries/Comments related to section 2.1 of KSCAF_DocRequirements
- Dominant language
- CSS
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
An implementation of a Khronos SC API standard which passes its appropriate Khronos conformant tests should not be taken that the SC implementation in question has meet all the requirements for its specific usage. The Khronos conformant tests only show the implementation has reached a specified standard of accuracy and behaviour required for Khronos approval.
--> 'conformant' to be changed to 'conformance'
--> The first statement needs to be rephrased as it is not easily comprehensible.
--> 'taken' to be changed to 'considered'
--> what does it mean by "all the requirements"?
--> What does "specified standard of accuracy"mean?
--> What does "Khronos approval" mean?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading section 2.1 of KSCAF_DocRequirements and compare each flagged term and sentence with the surrounding requirements. Confirm the intended meanings of “all the requirements,” “specified standard of accuracy,” and “Khronos approval” before editing. Done means section 2.1 uses the agreed terminology and has clear, comprehensible wording.
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