If you separate attestation into 2 parts: (1) the requirement and (2) the certification over a digital object – you can think of using a language like ODRL. In the screenshot below from the EU site, the language of “policy”, reporting/notification/legal/remediating/etc (all types of obligations) is part of the functions and/or extensions. There was a proposal in 2019 for something similar done between UK/EU/JP in 2019 (academic) “This paper addresses the problem of constructing a policy pipeline that enables compliance checking of business processes against regulatory obligations.”

Regards,
___________________________________
Joshua Cornejo
marketdata
embed open standards
across your supply chain
From: open-regulatory-compliance <open-regulatory-compliance-bounces@xxxxxxxxxxx> on behalf of Greg Wallace via open-regulatory-compliance <open-regulatory-compliance@xxxxxxxxxxx>
Reply-To: Open Regulatory Compliance Working Group <open-regulatory-compliance@xxxxxxxxxxx>
Date: Monday 5 August 2024 at 12:32
To: Open Regulatory Compliance Working Group <open-regulatory-compliance@xxxxxxxxxxx>
Cc: Greg Wallace <greg@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [open-regulatory-compliance] Attestations of compliance
I too am interested in understanding this better. I'd suggest that "Attestations" would be a good Open Source Specification Project for the WG.
--
Greg Wallace
Director of Partnerships & Research
_______________________________________________ open-regulatory-compliance mailing list open-regulatory-compliance@xxxxxxxxxxx To unsubscribe from this list, visit https://accounts.eclipse.org