Skip to content

Conversation

@JoanGi
Copy link
Contributor

@JoanGi JoanGi commented Dec 4, 2025

Since the first release, the approach of the Responsible AI (RAI) extension has evolved substantially.

  • Croissant now incorporates two core mechanisms for the responsible use and sharing of data directly into the main specification.
  • Concurrently, the Croissant RAI extension continues to exist; it serves as a machine-readable format for data cards and is intended to be an incubator for new RAI trends emerging from the community.

This pull request updates the presentation of the RAI use case to maintain consistency with this revised approach.

@JoanGi JoanGi requested a review from benjelloun December 4, 2025 14:46
@JoanGi JoanGi requested a review from a team as a code owner December 4, 2025 14:46
@github-actions
Copy link

github-actions bot commented Dec 4, 2025

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

2. **Machine-readable RAI Data Documentation**: This specification proposes a machine-readable vocabulary for capturing and publishing existing Responsible AI (RAI) documentation solutions (such as [Data Cards](https://dl.acm.org/doi/pdf/10.1145/3531146.3533231)), thereby streamlining their publishing, sharing, discovery, and reuse. Further details are available in the [Croissant RAI specification](http://mlcommons.org/croissant/RAI/1.1).


We welcome additional extensions from the community to meet the needs particular and resposible AI aspects of specific data modalities (e.g. audio or video) and domains (e.g. geospatial, life sciences, cultural heritage).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: resposible -> responsible.

1. **Data use and dissemination**: It provides a [set of mechanisms](#responsible-ai-and-governance) to enable the responsible use and dissemination of data. This is achieved by offering a machine-actionable representation of the data's provenance, lineage, and usage conditions at various levels of granularity. These mechanisms are built upon the integration of W3C standards (such as PROV-O and ODRL), ensuring compatibility with existing solutions.

2. It records at a granular level how a dataset was created, processed and enriched throughout its lifecycle – this process is meant to be automated as much as possible by integrating Croissant with popular ML frameworks. By allowing the metadata to be loaded automatically, Croissant also enables developers to compute RAI metrics automatically and systematically, identifying potential data quality issues to be fixed.
2. **Machine-readable RAI Data Documentation**: This specification proposes a machine-readable vocabulary for capturing and publishing existing Responsible AI (RAI) documentation solutions (such as [Data Cards](https://dl.acm.org/doi/pdf/10.1145/3531146.3533231)), thereby streamlining their publishing, sharing, discovery, and reuse. Further details are available in the [Croissant RAI specification](http://mlcommons.org/croissant/RAI/1.1).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The RAI 1.1 spec doesn't exist yet... Do you want to link to RAI 1.0 for now?

This is how Croissant helps address RAI:

1. It proposes a machine-readable way to capture and publish metadata about ML datasets – this makes existing documentation solutions like [Data Cards](https://sites.research.google/datacardsplaybook/) easier to publish, share, discover, and reuse;
1. **Data use and dissemination**: It provides a [set of mechanisms](#responsible-ai-and-governance) to enable the responsible use and dissemination of data. This is achieved by offering a machine-actionable representation of the data's provenance, lineage, and usage conditions at various levels of granularity. These mechanisms are built upon the integration of W3C standards (such as PROV-O and ODRL), ensuring compatibility with existing solutions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's just say provenance instead of provenance, lineage.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, can you link to the relevant sections of the spec?

1. **Data use and dissemination**: It provides a [set of mechanisms](#responsible-ai-and-governance) to enable the responsible use and dissemination of data. This is achieved by offering a machine-actionable representation of the data's provenance, lineage, and usage conditions at various levels of granularity. These mechanisms are built upon the integration of W3C standards (such as PROV-O and ODRL), ensuring compatibility with existing solutions.

2. It records at a granular level how a dataset was created, processed and enriched throughout its lifecycle – this process is meant to be automated as much as possible by integrating Croissant with popular ML frameworks. By allowing the metadata to be loaded automatically, Croissant also enables developers to compute RAI metrics automatically and systematically, identifying potential data quality issues to be fixed.
2. **Machine-readable RAI Data Documentation**: This specification proposes a machine-readable vocabulary for capturing and publishing existing Responsible AI (RAI) documentation solutions (such as [Data Cards](https://dl.acm.org/doi/pdf/10.1145/3531146.3533231)), thereby streamlining their publishing, sharing, discovery, and reuse. Further details are available in the [Croissant RAI specification](http://mlcommons.org/croissant/RAI/1.1).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm.... How is this bullet point different from the one above? Aren't they both about creating machine readable RAI information?

@JoanGi
Copy link
Contributor Author

JoanGi commented Dec 5, 2025

I've uploaded a shortened version with only one bullet point and added graphical support from the PROV example to be consistent with other use cases. Please check it @benjelloun.

@JoanGi JoanGi merged commit df30323 into mlcommons:main Dec 9, 2025
12 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Dec 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants