Skip to content

Conversation

@LisaBobbitt
Copy link

Please review my updates. I still feel there are areas that need attention but I do not have the background to fill it out.

sthagen
sthagen previously approved these changes Dec 18, 2025
The intended use addresses transparency in AI, cybersecurity, supply chains, and other areas where data quality and accountability are foundational to performance
and compliance \- especially in regulated and high-risk environments.
This OASIS Data Provenance Metadata specification provides an information model and several specialized data schemata for describing and managing data provenance and data lineage.
Trust in Artificial Intelligence starts with transparency into data provenance; assessing where data comes from, how it’s created, and in what scenarios it can be used, legally. This is why we developed the first cross-industry data provenance metadata specification, a common language to provide transparency.
Copy link
Contributor

@sthagen sthagen Jan 7, 2026

Choose a reason for hiding this comment

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

The order of reasoning and the form of speech are to me not the best fit for an abstract of a standard. What about the following instead:

The resulting common language provides transparency for data provenance and enables assessing where data comes from,
how it has been created, and in what scenarios it can be used, legally.

sthagen and others added 4 commits January 7, 2026 23:27
Updates with Brian's recommendations and clean up of terminology
fixed typo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants