data provenance community meeting september 25 th, 2014

Data Provenance Community Meeting

September 25th, 2014

2

Meeting Etiquette

Click on the “chat” bubble at the top of the meeting window to

send a chat.

• Please mute your phone when you are not speaking to prevent background noise.– All meetings are recorded.

• Please do not put your phone on hold. – Hang up and dial back in to prevent hold

music.• Please announce your name before

speaking• Use the “Chat” feature to ask questions or

share comments.– Send chats to “All Participants” so they

can be addressed publicly in the chat, or discussed in the meeting (as appropriate).

3

Agenda

Topic Time Allotted

General Announcements 4 minutesUse Case End-to-End Comments Review 55 minutes Next Steps/Questions 1 minutes

4

Next meeting:• All Hands: Thursday, October 2nd, 2014 – 2:30-3:30 pm ET• http://wiki.siframework.org/Data+Provenance+Initiative

• All meeting materials (including this presentation) can be found on the Past Meetings page:• http://wiki.siframework.org/Data+Provenance+Past+Meetings

General Announcements

5

Review your status

6

S&I Framework Phases outlined for Data Provenance

Phase Planned Activities Pre-Discovery Development of Initiative Synopsis

Development of Initiative Charter Definition of Goals & Initiative Outcomes

Discovery Creation/Validation of Use Cases, User Stories & Functional Requirements Identification of interoperability gaps, barriers, obstacles and costs Review of Candidate Standards

Implementation Creation of aligned specification Documentation of relevant specifications and reference implementations

such as guides, design documents, etc. Development of testing tools and reference implementation tools

Pilot Validation of aligned specifications, testing tools, and reference implementation tools

Revision of documentation and toolsEvaluation Measurement of initiative success against goals and outcomes

Identification of best practices and lessons learned from pilots for wider scale deployment

Identification of hard and soft policy tools that could be considered for wider scale deployments

We are Here

7

Data Provenance –Use Case (Discovery)Ahsin Azim

Nisha Maharaja

8

Week Target Date (2014) All Hands WG Meeting Tasks

Review & Comments from Community via Wiki page

due following Tuesday by 8 P.M. Eastern

10 8/21Review: Scenario #1 and #2 Functional Requirements and Sequence DiagramsIntroduce: Scenario #3 Functional Requirements and Sequence Diagrams

Review Scenario #3 Functional Requirements and Sequence Diagrams

11 8/28Review :Scenario #3 Functional Requirements and Sequence DiagramsIntroduce: Dataset Requirements

Review Dataset Requirements

12 9/4 Review Dataset Requirements and Risks/Issues Review Data Set Requirements and Risks And Issues

13 9/11 Review Risks/IssuesBegin End to End Review End to End Review

14 9/25 End-to-End Comments Review & dispositionBegin Consensus Begin casting consensus vote

15 10/2 Address Consensus comments, if any

Proposed Use Case & Functional Requirements Development Timeline

9

Topic Time Allotted

General Announcements 10 minutes

Use Case Discussion

Discuss Timeline/Progress to Date 2 minutes

End to End Comment Review and Dispositions 37 minutes

Overview of Consensus 10 minutes

Next Steps 1 minutes

Agenda

Sections for Review

10

Today we will be reviewing: 1. Review End to End

Comments and Dispositions

2. Discuss Consensus Process

Double click the icon to open up the Word Document with the sections for review

End to End Review Doc

Next Steps

• The Consensus Voting period begins September 25th and closes on September 30th at 8 P.M. ET

• Only committed members are allowed to vote on the Use Case– If you have questions about your status, please contact

Apurva Dharia (apurva.dharia@esacinc.com) or Jamie Parker (jamie.parker@esacinc.com)

5

Consensus• For those of you who are committed members, we ask you to vote on the Data

Provenance Charter:– Yes

• A Yes vote does not necessarily mean that the deliverable is the ideal one from the perspective of the Initiative Member, but that it is better to move forward than to block the deliverable

– Yes with comments• If a Consensus Process attracts significant comments (through Yes with comment votes), it

is expected that the comments be addressed in a future revision of the deliverable.– Formal Objection

• Must provide comments indicating a path to address the objection in a way that meets the known concerns of other members of the Community of Interest. "Formal Objection" vote without such comments will be considered Abstain votes.

• A Formal Objection means that the objector cannot proceed with the project unless the objections are met. It is acceptable and expected to use a Formal Objection in a first consensus round to communicate a point of view or process issue that has not been addressed in the drafting of the initial deliverable.

• Should a Consensus Process attract even one "Formal Objection" vote with comments from an Initiative Member, the deliverable must be revised to address the "Formal Objection" vote (unless an exceptional process is declared).

– Abstain (decline to vote)Note: Each Organization, no matter the number of Committed Members only receives 1 Vote. If there are multiple committed members from your organization please verify your collective vote with them

Verifying your Commitment Level

• To verify you are a committed member go to the Members section of the Data Provenance Wiki page: http://wiki.siframework.org/Data+Provenance+Join+the+Initiative#Members

• Search for your name• Verify your “Role”• If you want to be a committed

member and see that you are not please re-join or re-sign up for the initiative indicating your new role: http://wiki.siframework.org/Data+Provenance+Join+the+Initiative 13

Exam

ple M

embe

r List

Submitting your Vote (September 25th, 2014)1. Review the Data Provenance Use Case

(using the attached word document): http://wiki.siframework.org/Data+Provenance+Use+Case+Consensus

2. Complete the Voting Form:– NOTE: You must be a Committed

Member to Vote• Yes• Yes with comments.• Formal Objection• Abstain (decline to vote)

3. Submit your Vote

4. A message is displayed verifying your vote was recorded

14

2

3

4

Project Charter Section

To participate in the Consensus for Data Provenance please do the following:1

NOTE: Consensus ends on September 30, 2014 @ 8PM Eastern Time.

15

Support Team and QuestionsPlease feel free to reach out to any member of the Data Provenance

Support Team:• Initiative Coordinator: Johnathan Coleman: jc@securityrs.com • OCPO Sponsor: Julie Chua: julie.chua@hhs.gov • OST Sponsor: Mera Choi: mera.choi@hhs.gov• Subject Matter Experts: Kathleen Conner: klc@securityrs.com and Bob Yencha:

bobyencha@maine.rr.com • Support Team:

– Project Management: Jamie Parker: jamie.parker@esacinc.com – Use Case Development: Ahsin Azim: ahsin.azim@accenturefederal.com and

Nisha Maharaja: nisha.maharaja@accenturefederal.com – Harmonization: Rita Torkzadeh: rtorkzadeh@jbsinternational.com – Standards Development Support: Amanda Nash:

amanda.j.nash@accenturefederal.com – Support: Lynette Elliott: lynette.elliott@esacinc.com and Apurva Dharia:

apurva.dharia@esacinc.com