Consensus for LDAF Use Case 1 has been reached

We are pleased to announce that we have achieved unanimous consensus on Use Case 1. To review the final votes and comment dispositions, scroll below to the "Consensus Voting Responses."

Thank you to all those committed members who took time out to review the final Use Case document and to submit a formal vote for the LDAF.

The final Use Case document can be found here.

Consensus Voting Process

We are pleased to be entering the consensus voting process for the first DAF Use Case-Local Data Access via Intra-Organizational Query. The consensus voting period closes at 5:00 pm (EST) on Monday, December 9th.

To successfully submit your vote, please follow the instructions below.

  1. Verify Your Commitment Level
    • To verify you are a committed member, search for your name in the "DAF Members" list below and verify that your "Role" is listed as a "Committed Member." (Move to Step 2)
    • If you are registered as a DAF Member, but are not a “Committed Member,” please e-mail a “Statement of Commitment” to to change your status.
    • If you are not registered for the DAF initiative, please join by visiting: Join the DAF Initiative
  2. Review the Final Use Case Document (including comment dispositions)
  3. Review the Voting Options (below)
  4. Cast Your Vote (below)
    • After you have reviewed the final Use Case document and comment dispositions, you can begin casting your vote by completing the ballot found below. If you would like to add any additional comments to your ballot, remember to provide actionable comments where applicable/necessary.
    • Only “one” vote per committed organization will be counted, please make sure to reconcile your votes with your colleagues
    • All votes are due by 5:00 pm (EST) on Monday, December 9th, 2013.


Consensus Voting OptionsThe goal is unanimous consent on the final Use Case for the Local Data Access Framework (DAF), which is obtained by carefully considering and addressing significant input from the Community of Interest. Each Initiative Member will provide one of the following votes during the Consensus process:
  • 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 with 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.
    • 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: Only one vote will be counted per committed organization no matter how many individuals from that organization are committed members. If committed members of an organization have conflicting votes, those votes will need to be reconciled to the vote that best represents the committed organization. For example, if one member of ACME Corp. votes "Yes (with comment)" another member from ACME Corp. cannot vote "Object (with comment)." Since ACME Corp. gets one vote per organization the member's votes would need to be reconciled to one vote.

If you have questions or need help completing this form please feel free to email Gayathri Jayawardena at .

  • No labels