Stream: implementers
Topic: Validation of Provenance
Lakshmi Thrivarna (Aug 30 2018 at 06:25):
Hi All,Is there any way to validate a Provenance with out using Policy Element??
Lloyd McKenzie (Aug 30 2018 at 06:29):
Can you explain what you mean by "validate"?
Richard Townley-O'Neill (Aug 30 2018 at 06:30):
What do you mean by "validate"?
You could test a provenenace instance against a profile. But I guess that you mean something else.
Lakshmi Thrivarna (Aug 30 2018 at 07:31):
Thanks for reply @Lloyd McKenzie ,@Rechard I want to validate Provenance Resource , Which is related to our organization
Lloyd McKenzie (Aug 30 2018 at 07:43):
Right - but what do you mean by "validate"?
Lakshmi Thrivarna (Aug 31 2018 at 09:09):
Hi, Can any one suggest
How to use Policy in Provenance like OAuth or XACML
John Moehrke (Aug 31 2018 at 12:36):
The policy element in Provenance is there to record the use-case where data are imported with the authorization of the named policy. This is simply a record of the policy (by identifier) that authorized the import. This is not the enforcement or decision engine, this is simply recording a fact.
John Moehrke (Aug 31 2018 at 12:40):
such as when a Patient gives authorization to a Clinical-Research project. The import of each data element (Resource) could then be easily linked back to that one Consent. In this way if that Consent is rescinded then that Clinical-Research project knows all the data that must now be rescinded, as long as that data element don't have other Provenance with policy elements authorizing their retention. --- Note I am using Clinical-Research in my use-case here, but the element is not limited to Clinical-Research, nor is Clinical-Research a specific target use-case. I use it a it is very distinct from Treatment use-cases where this kind of thing is a much less likely used element.
Last updated: Apr 12 2022 at 19:14 UTC
