KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
Admin: Investigate to get accreditation from Tüv or ISO for better acceptance of SC API
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Illya attended the Scandinavian Conference on System and Software Safety 2017 Stockholm to present in a workshop "Where are safety standards heading?" Illya presented a talk on Khronos SCAP. After it was suggested by Prof. Tor Stalhane that perhaps we should investigate getting addition approval of a SC API from bodies like Tùv or ISO. He suggested this would give additional creditability for adoption and acceptance - confidence.
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
No files, tests, or entry points are named. Start by reviewing the issue context about SC API adoption and the suggested TÜV or ISO approval, then define what accreditation path is being investigated. Done should be a documented determination of the relevant approval options and next steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100