Governance & Stewardship Aspects

Which problem is this feature request solving?

Came across this while reviewing the Data Quality / DQOps proposal. Usually when DQ Triggers (for warnings or errors) are reached, a notification to the proper data owner or in larger organizations data steward is required.

Describe the solution you'd like

Instead of integrating this as a custom extension into the DQ section, we could think about defining Data and Model / Algo Governance into a dedicated section and the re-use it for other aspects (like the DQ notifications)

In addition to the DQ space we need to be thinking about the EU genAI act: As it is very broad and much wider than just genAI it is reasonable to expect that many organizations could turn to ODPS to manage their data product liability policies. And then the governance section would even become wider as not just the core ownership, but also more specialized ownerships for Algorithm and ML model conformity will fall to different people across the org.

Describe alternatives you've considered

Alternatives could be as follows:

1) Extending each section that requires role or person specific notifications individually. The downside is that this makes the spec less concise and leads to redundancies or worst conflicts.

2) Linking it to an entirely external spec dedicated to Data and Algo / Model governance. I do assume that organizations that do not have this in place have a hard time implementing multiple standards and could possibly opt out because of that.

Can you submit a pull request?

Yes

Something I can do next week, if the community agrees that it makes sense. Also would need to discuss if we create a new section or rather include it in one (or multiple) places that seem a good fit.

---- Leave intact! Approval of Contributor Agreement -----

By submitting issue you approve the Contributor Agreement, https://governance.opendataproducts.org/v1/contributions/contributor-agreement

Open-Data-Product-Initiative / dev