1. Architecture Tutorial 1 Overview of Today’s Talks Provenance Data Structures Recording and Querying Provenance –Break (30 minutes) Distribution and Scalability Security Methodology

2. Architecture Tutorial Process Documentation: Concepts and Data Structures by Simon Miles (sm@ecs.soton.ac.uk)

3. Architecture Tutorial 3 Process Documentation The provenance of x is the process that led to x. How do we find the provenance of x? Two steps: 1.Document the process in an application 2.Retrieve the process that led to X from the documentation

4. Architecture Tutorial 4 World View Every application is made up of actors Every change that happens is an action by an actor Actors communicate by sending messages. Every action is triggered by a message The outputs of (messages sent by) an actor are caused by the inputs to (messages received by) the actor

5. Architecture Tutorial 5 Interaction in the Organ Transplant Process Donor Data Collector Electronic Healthcare Record System Request healthcare record for patient PID1

6. Architecture Tutorial 6 Request Message Contents … PID1

7. Architecture Tutorial 7 Identifying a Message An interaction is a message being sent by one actor and received by another An interaction is identified by the following –The source of the message (startpoint) –The sink of the message (endpoint) –A unique ID that distinguishes between interactions with the same source and sink

8. Architecture Tutorial 8 Interaction Key Web Services: Endpoint Reference

9. Architecture Tutorial 9 Asserting the Content of a Message In asserting the content of a message it has sent or received, an actor provides the following: –A unique id for the assertion –The style in which the content is asserted –The content of the message

10. Architecture Tutorial 10 Interaction P-Assertion

11. Architecture Tutorial 11 Request Message Contents … PID1

12. Architecture Tutorial 12 Styled P-Assertion 1 http://www.pasoa.org/.../styles#AnonymisedPatient … x93ab4

13. Architecture Tutorial 13 Asserting the State of an Actor In asserting its state, an actor provides the following: –A description of part or all of its state –Optionally, the style in which it is asserted –A unique id for the assertion

14. Architecture Tutorial 14 Actor State P-Assertion

15. Architecture Tutorial 15 Example (Donor Data Collector) 2 PID5 PID16 …

16. Architecture Tutorial 16 Data Within Assertions Application messages and actor states contain parts, e.g. arguments to operations These parts can have independent provenance

17. Architecture Tutorial 17 Another Interaction Donor Data Collector Testing Lab Blood Analysis Results

18. Architecture Tutorial 18 Analysis Results Message Contents … Sample3 negative

19. Architecture Tutorial 19 Referring to Data in a P-Assertion … Sample3 negative

20. Architecture Tutorial 20 Pointing to Data Within Assertions In order to refer to a part of an assertion’s content, we need to provide the following: –The ID of the assertion –How to access the part within the assertion’s content

21. Architecture Tutorial 21 Pointing to Data Within Assertions In order to refer to a part of an assertion’s content, we need to provide the following: –The ID of the assertion –How to access the part within the assertion’s content In the example, the ID of the assertion is given by: –Interaction Key –View Kind –Local P-Assertion ID

22. Architecture Tutorial 22 Pointing to Data Within Assertions In order to refer to a part of an assertion’s content, we need to provide the following: –The ID of the assertion –How to access the part within the assertion’s content In the example, the ID of the assertion is given by: –Interaction Key –View Kind –Local P-Assertion ID The data part is given by a data accessor, such as an XPath expression: –/ soap:envelope / soap:body / testlab:analysisResults / testlab:sampleID

23. Architecture Tutorial 23 Related Interactions Donor Data Collector User Interface Blood Analysis Results Electronic Healthcare Record Organ Donation Decision

24. Architecture Tutorial 24 Functional View of Decision fit for donation Diagnose Potential Organ Decision negative Lab Results … Healthcare Record

25. Architecture Tutorial 25 Functional View of Decision fit for donation Diagnose Potential Organ Decision negative Lab Results … Healthcare Record Parameter Names

26. Architecture Tutorial 26 Functional View of Decision fit for donation Diagnose Potential Organ Decision negative Lab Results … Healthcare Record Subject Relation Object

27. Architecture Tutorial 27 Relationship P-Assertion

28. Architecture Tutorial 28 Sharing Context To connect assertions made by different actors some information must be shared. For example: –A sender & receiver in an interaction need to use the same interaction key. –An actor might like to inform other actors as to which provenance store it used to store assertions. –Messages can be marked as being part of the same process.

29. Architecture Tutorial 29 Demarcating Processes Testing Lab Donor Data Collector User Interface Testing Lab Donor Data Collector User Interface Run 1Run 2

30. Architecture Tutorial 30 Demarcating Processes Testing Lab Donor Data Collector User Interface Testing Lab Donor Data Collector User Interface Run 1Run 2 Tracers

31. Architecture Tutorial 31 Tracers Tracers are added by an originating actor Tracers are passed between actors if the messages are part of the same process

32. Architecture Tutorial 32 Interaction Context States some metadata about an interaction. It contains: – An interaction key for that interaction – And interaction metadata. – Examples of such metadata are: Tracers References to provenance stores that contain assertions about the interaction.

33. Architecture Tutorial 33 P-Header Interaction Contexts can be transferred in P-Headers. P-Headers are additional provenance specific information added to existing application messages. P-Headers can also be used to assign an interaction key to the message that its sent in.

34. Architecture Tutorial 34 P-Header

35. Architecture Tutorial 35 Message with P-Header …Donor Data Collector… … Testing Lab … 345 http://DDC.provenance.store http://process/9467 …

36. Architecture Tutorial 36 Summary Our data structures allow assertions about past processes to be succinctly and exactly specified Interaction and actor state p-assertions can be styled, so that what is asserted differs from that which actually occurred in a well-specified way Relationship p-assertions express functions between wholes or parts of p-assertions Actors share context to ensure that consistent identifiers are used throughout documentation Context can include process identifiers, called tracers

37. Architecture Tutorial 37 Questions? Simon Miles sm@ecs.soton.ac.uk