| Table of Contents | ||
|---|---|---|
|
This the home page for a draft drafting of the the ToIP Technology Architecture Specification (TAS), a proposed Draft Deliverable deliverable of the TSWG developed by the the Technology Architecture Task Force.
Links
The Working Draft of this specification is proceeding through two stages:
...
After the publication of the first public review draft of the TAS V1.0 December 2022, the ToIP Foundation also established a home page for the TAS on the ToIP website. It also established a page for a living document about the ToIP stack development process called Evolution of the ToIP Stack.
Links
Work on the TAS began in Google docs but has now moved primarily to the TATF GitHub repository. Following are links to all the current sources:
- TAS GitHub Markdown version
- TAS GitHub Issues
- TAS GitHub Discussions
- TAS Source Diagrams (Google Slides) <== SOURCE DIAGRAMS used in the TAS
- ToIP Protocol Stack Diagrams (Google Slides) <== All of all our past diagrams (some of which have been copied to TAS Source Diagrams)
- TAS WORKING DRAFT 03 Google doc version <== REFERENCE ONLY — NO LONGER ACTIVE
- TAS OLD WORKING DRAFT 02 Google Doc version <== REFERENCE ONLY — NO LONGER ACTIVE
- TATF Google Drive Folder <== WHERE ALL OF THE ABOVE may be found
Contributors
To comply with the intellectual property rights protections in the charter of the ToIP Foundation (as required by all Joint Development Foundation projects hosted the Linux Foundation), all contributors to this Pre-Draft Deliverable MUST be current members of the ToIP Foundation. The following contributors each certify that they meet this requirement:
- Darrell O'Donnell, Continuum Loop
- Drummond Reed, Evernym
- Wenjing Chu , Futurewei
- Tim Bouma, Individual
- isaac henderson, Individual
- Antti Kettunen, Individual
- Jo Spencer, 460degrees / Sezoo
Other contributors MUST also add their name and membership affiliation to the Google doc or wiki page version of the spec as it proceeds through development.
Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL", when appearing in ALL CAPITALS, are to be interpreted as described in RFC 2119.
All other terms in bold will be defined in one or more of the ToIP glossaries in a process being defined by the ToIP Concepts and Terminology Working Group.
Purpose
The purpose of this specification is to define the overall architectural requirements for each of the four layers of the ToIP stack and how they are abstracted from the layer below. This specification will lay the overarching foundation for future ToIP specifications that will specify more detailed interoperability requirements such as specific protocols, interfaces, and test cases. This TF will be adapting the original Hyperledger RFC defining the ToIP stack and following the Design Principles for the ToIP Stack. Note: this specification is intended to serve as a direct a counterpart to the ToIP Governance Architecture Specification deliverable from the GSWG Governance Architecture TFSee the official list of contributors in the current draft.