Skip to content

Commit 5897e4c

Browse files
Update TRANSPARENCY_FAQS.md (#9198)
Updates from the RAI team on transparency documentation ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄 --------- Co-authored-by: Chris <[email protected]>
1 parent 69c0640 commit 5897e4c

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

TRANSPARENCY_FAQS.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,7 @@ The intended uses of Microsoft Semantic Kernel include:
2222

2323

2424
## How was Microsoft Semantic Kernel evaluated? What metrics are used to measure performance?
25-
Microsoft Semantic Kernel was reviewed for reliability and performance metrics that include:
26-
- Accuracy: Evaluated based on the correctness of the outputs generated against known facts.
25+
Microsoft Semantic Kernel metrics include:
2726
- Integration Speed: Assessed by the time taken to integrate AI models and initiate functional outputs based on telemetry.
2827
- Performance Consistency: Measurements taken to verify the system's reliability based on telemetry.
2928

0 commit comments

Comments
 (0)