Stream: Security and Privacy
Topic: Provenance.entity.role
Grahame Grieve (Jun 22 2020 at 11:34):
I'm having trouble understanding the definition of removal:
Grahame Grieve (Jun 22 2020 at 11:34):
A derivation for which the entity is removed from accessibility usually through the use of the Delete operation
Grahame Grieve (Jun 22 2020 at 11:35):
does this mean:
- the source contained information that lead to the target being removed?
- the source contained information has been removed from the target?
- something else?
Grahame Grieve (Jun 22 2020 at 11:52):
Also, the provided value sets for Provenance.agent.type and Provenance.agent.role rather confuse things. I note that the US core profile for Provenance uses type for what I would've thought was role?
k connor (Jun 24 2020 at 05:43):
Hi Grahame - John Moehrke and I know that we need to redo the Provenance.agent.type and Provenance.agent.role value sets to differentiate between the functional role/what the actor did in the workflow codes (agent.type) and the structural roles/competencies (agent.role). It's a mess right now. Obviously need to prioritize this especially because IG writers are getting discombobulated with their Provenance agent.type/agent.role code choices. On my to do list.
Lloyd McKenzie (Jun 24 2020 at 06:09):
It would be good to stop using v3 codes that weren't designed for the purpose as part of the process.
Grahame Grieve (Jun 24 2020 at 06:25):
it would be good to have a statement of intent about what we're going to try to achieve
John Moehrke (Jun 29 2020 at 13:26):
having engagement from people trying to use this is fantastic. Theory and reality are different. Please bring on the CR to help.
John Moehrke (Jun 29 2020 at 13:29):
I was thinking that a record of Provenance of a delete would be needed, but we never quite finished the modeling as we didn't get use-cases to help inform what we would need to do. The use-case we have is simply to record WHO deleted the resource WHEN and WHY.
Last updated: Apr 12 2022 at 19:14 UTC
