2024.10.02

[seanmcilroy29]

---

2024.10.02 Agenda/Minutes

---

Time: Bi-weekly @ 1700 (BST) - See the time in your timezone

• Co-Chair - Chris Xie- (Futurewei)
• Co-Chair - Vacant
• Convener – Sean Mcilroy (Linux Foundation)

Antitrust Policy

Joint Development Foundation meetings may involve participation by industry competitors, and the Joint Development Foundation intends to conduct all of its activities in accordance with applicable antitrust and competition laws. It is, therefore, extremely important that attendees adhere to meeting agendas and be aware of and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

If you have questions about these matters, please contact your company counsel or counsel to the Joint Development Foundation, DLA Piper.

Recordings

WG agreed to record all Meetings. This meeting recording will be available until the next scheduled meeting.
Meeting recording link

Roll Call

Please add 'Attended' to this issue during the meeting to denote attendance.

Any untracked attendees will be added by the GSF team below:

• Full Name, Affiliation, (optional) GitHub username

Agenda

• Approve agenda
• Approve previous Meeting Minutes

Introductions - Chris

• Any new members?

Discussion - Asim

• Review Spec proposed updates

Discussion - Chris

• [AI]GAISSALabel: A Tool For ML Energy Labeling #87
• Grant Application for Climate Change AI 2024 #86

Project Dashboard

• Review and close stale issues

Future meeting Agenda submissions

• If you have any Agenda submissions, please let Sean know via email [email protected] or open an Issue

Next Meeting

• 16th Oct @ 9 am P/T

Adjourn

• Motion to adjourn

---

Previous meeting AI's

• Chris/Adi - Start setting up an SCR certification lab folder and documentation.
• All - Review Asim's previous comments and suggestions on strengthening the SCR standard.
• All - Provide direct feedback and comments on the SCR documentation.

[seanmcilroy29]

MoM

Summary Notes
The group had a discussion about developing and implementing a new software labelling system. Chris emphasized the need for easy adoption and business value, stressing the importance of making the label accessible and verifiable. Asim provided detailed specifications for the label, which included using a QR code linking to a manifest file for verification. They also talked about the potential policy benefits, such as compliance with EU policies like the CSRD. The conversation ended with the decision to create a comprehensive white paper outlining the new labelling system's business value and policy implications and the importance of providing tools for easy adoption.

---

Minutes

Detailed Discussion on Label Specifications
Asim goes through the specifics of the label, including the need for normative references and ISO standards.
They discuss the importance of clear and detailed specifications for the label, including using QR codes.
Asim emphasizes the need for a designer to provide guidelines on how the label should look and be implemented.
They talk about the importance of making the label accessible to people with different needs, such as those with visual impairments.

Concerns About Ease of Adoption and Business Value
Chris questions how easy it will be for the label to be adopted and used, especially on websites that use large language models. Asim agrees that it's important to find a balance between thorough certification and getting the industry and community to adopt it. Chris stresses the importance of making the label easy for businesses to understand and use. They also talk about how the label could be valuable for businesses, including its potential use in customer relations management and compliance with policies.

Future Directions and Tooling
Asim recommends creating tools and systems to help people use the label, similar to Creative Commons. They emphasize the importance of launching the label with the required tools and resources for adoption. Asim also highlights the necessity of a white paper that explains the label's business value and its relationship to policy compliance. Chris and Asim both agree that hiring more researchers is essential for developing the white paper and promoting the adoption of the label.

Action Items

• Engage the design team to provide guidelines on the visual representation of the SCER label.
• Explore options for verification mechanisms, including using a manifest file and potential third-party attestation.
• Develop a white paper outlining the business value and policy alignment of the SCER label.