search

KhronosGroup / KSCAF_DocRequirements

Khronos Safety Critical Advisory Forum’s minimum requirements for developing a safety critical technology specification.
3 stars 1 forks source link

Queries/Comments related to section 2.1 of KSCAF_DocRequirements #37

Open Mandar-Pitale opened 6 years ago

Mandar-Pitale commented 6 years ago

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?

irudkin commented 6 years ago

Changed to An implementation of a Khronos SC API specification which passes its appropriate Khronos conformance test(s) should not be taken as implementation that is safe for any safety critical function it is to be used in. Each SC implementation still has to satisfy the target domain's functional safety standard requirements and safety requirements for each use. The Khronos conformant tests only show the implementation has satisfied the Khronos specification and requirements for that API, not any Functional Safety Requirement.