Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

This the home page for a draft of the ToIP Technology Architecture Specification (TAS), a Draft Deliverable of the TSWG developed by the Technology Architecture Task Force.

Links

Work on the TAS is taking place across a number of documents and repositories:

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 MUST be current members of the ToIP Foundation. See the official list of contributors in the Working Draft.

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 TF.










  • No labels