Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UC: Discourage Transparency #67

Open
Tracked by #61 ...
jawache opened this issue Jun 5, 2024 · 2 comments
Open
Tracked by #61 ...

UC: Discourage Transparency #67

jawache opened this issue Jun 5, 2024 · 2 comments
Assignees
Labels
Action Item documentation Improvements or additions to documentation

Comments

@jawache
Copy link
Contributor

jawache commented Jun 5, 2024

You receive a low rating compared to your competitor and don't want to disclose since no rating is better than a worse rating.

With a percentile based rating system a lack of disclosure is deeply problematic, since only through disclosure and transparency are the boundaries between A - D set.

Equivalence

  • Taking CDP as an example, the ratings are private and not disclosed - only the A lists are disclosed, it's used more as a signal to organizations the work they need to do in order to receive and A rating.

Counter

  • Remove ratings and focus on just being transparent regarding the score, leave it to the user to decide if the trade-offs are worth it. For example, food has had labelling for decades prior to nutri-score, we read the labels and decided if the product was healthy.
  • Make it a regulatory requirements to disclose.
@chrisxie-fw
Copy link
Contributor

chrisxie-fw commented Jun 26, 2024

  1. Percentile based system is a default implementation of the base class (SCER base standard framework), unless the derived class (implementation of the SCER framework) defines a different rating algorithm and rating range.
  2. If SCER is used internally by an organization, the org decides to disclose it or not publicly. If the SCER is used externally, or in a public facing service, it's the service owner's decision to disclose the rating.

By the way, the detailed disclosure of how the rating was calculated is a requirement, which is specified in the base SCER specification in the "User Access and Transparency" part under the Visualization and Labeling section:

"Ensure that the labels are easily accessible and understandable to users, providing detailed explanations of the ratings through tooltips or supplementary guides."

Here is the sample illustration of the rating label with the absolute and relative ratings along with QR code: SCER slide 1
SCER slide 3
SCER slide 4

@seanmcilroy29 seanmcilroy29 mentioned this issue Jul 3, 2024
18 tasks
@seanmcilroy29 seanmcilroy29 mentioned this issue Aug 7, 2024
18 tasks
@chrisxie-fw
Copy link
Contributor

Another way to understand this "UC" is that: should SCER remove the rating portion of it because it could cause potential "tension" by the LLM providers? And leave the rating part to the end users? Think youtube videos have the number of views, and the products sold on Amazon has the rating scores by the customers.

@seanmcilroy29 seanmcilroy29 mentioned this issue Sep 4, 2024
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Action Item documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants