...
Time | Item |
1 min | Welcome & Antitrust Policy |
2 min | Introduction of new members |
1 min | Agenda Review |
5 min | Opportunities of Decentralized Resource Identifiers in the Research Landscape – Dr. Carly Huitema |
| 10 min | Drafting – “Introduction to Trust over IP” white paper (V2)
|
| 5 min | Coordination/integration of the new ToIP graphic |
5 min | Concepts and Terminology WG – Definition of white paper |
5 min | Update – Meeting with Communications Committee – Feb 5, 2021 |
10 min | Update – Meeting with David Luchuk - IP |
15 min | Update – Meeting with WG Chairs and Co-Chairs – Feb 10, 2021 |
| 1 min | Next Steps |
Recording
Agenda & Discussion Notes
- 10 members joined the call
- Update on the Opportunities of Decentralized Resource Identifiers in the Research Landscape white paper - Carly Huitema
- Updates include change in language concerning build vs design
- Table entry at top of document to capture metadata and document control
- Provided abstract summary
- Next steps – final deliverable approval by EFWG
- ToIP community provided opportunity to work with experts to produce this white paper – would not have happened without this support
- Update on ToIP WP0010: Introduction to ToIP White Paper - David Luchuk
- Ideas presented in WP need to be revised to reflect current activities and experiences and to reference deliverables that will be finalized over the next month, (e.g., TSSs, interop specifications and design principles)
- Priority need for community to contribute to this deliverable and framed as important opportunity for all to engage – tied across all WGs and requires time and effort by all members
- Drummond Reed – origins of white paper based on single document, Aries Hyperledger RFC as there was need to publish definition of the ToIP stack, need for reference and basis of ToIP charter, given legal requirement to define scope of work as a Linux Foundation, Joint Development Foundation (JDF)
- Current misconception - ToIP tied to Hyperledger Aries. Although Charter includes definition of the technology stack, the Charter also includes recognition of technology stack succession (e.g., ToIP - native definition), at which point the original publication (Aries Hyperledger RFC) will be superseded by four documents (e.g., to include specifications/overall architecture of the two sides of the stack), specifically: