Disclaimer: The content herein represents preliminary brainstorming.
What is a TIP?
A ToIP Interoperability Profile (TIP) represents a specific combination of technologies that span each layer of the ToIP Technical Stack. TIPs can be designed, refined and supported by interoperable vendors. A TIP will often be applicable to specific design principles and use cases.
...
- Core Principles: Market requirements are necessary when combining technology to formulate a solution architecture.
- White-paper: Documentation outlining purpose, principles and architecture for the TIP.
- Adoption Metrics: Use case correlation backed by case study references demonstrate adoption.
- Interoperability Testing: Community driven certification of test cases and results.
- Vendor InteroperabilitySupport: Vertical integration of the technical stack must be supported by vendors that can demonstrate the interoperability between vendor solutions that adhere to a common vertical architecture.
- Best Practices: Implementation guidance for adoption as well as recommendations for interlock with the Governance Stack.
...
Ultimately, entities (business, governments, organizations) that seek to participate in an interoperable digital trust marketplace will need to assess (compare) solution architectures. Analogous to a Request for Proposal (RFP) process, entities should be able to align their requirements with the principles and expectations described by a TIP and use such a comparison exercise to make educated decisions. Allow when to compare apples-to-apples and when necessary enable clear articulation of apples-to-oranges activities. \.
Who would use a TIP?
As Ecosystem Projects (See Ecosystem Foundry WG) evolve they will need to define governance frameworks and select a TIP.
What is the scope of interoperability for a TIP?
In a utopian world solution architectures would be interoperable both vertically and horizontally across the Technology Stack. But this is not the goal of ToIP and in fact at some layers of the technology Stack, horizontal interoperability is not even necessary.
...
While horizontal interoperability at layer 3 (a wallet affiliated with TIP-A can exchange data with a wallet that supports TIP-B and both TIPs use different Layer 3 tech) would be important, the ability of a Layer 1 Utility based of on technology-A needing to exchange data with a Utility based on technology-B is less important.
Tech Stack WG Responsibilities
The Technical Stack WG is responsible for the processes and procedures of the WG as well as the lifecycle of TIP incubation.
...
- Stack Attributes: One of the deliverables of the Tech Stack WG (TSWG) is to provide guidance on the type of technology that can (could) be considered applicable at each layer of the Technology Stack. Additionally, what the architectural requirements are for vertical interoperability between the layers. This work effort MUST be technology neutral.
- TIP Criteria: What are the requirements for proposing a TIP to the WG?
- TIP Incubation: Establishment and Management of the TIP Lifecycle Process
- TIP Graduation: Review and approval process for the formalization of a TIP into a recommendation (TSS?)
TIP Lifecycle
The ToIP Foundation, which is technology agnostic, represents a collaborative forum where solution “recipes” can be matured and vetted in the market.
...
Note: These lifecycle stages are derived from the Hyperledger Aries RFCs Process.
TEMPORARY CONTENT:
| 2 min | Review of action items from the previous meeting | Chairs |
|
| 5 min | Reminder of IPR Mode Transition & Call for Exclusions | Chairs | As announced by Judith Fleenor on 25 August 2023 in an email to all members, the TSWG is transitioning from its current IPR mode (Creative Commons Attribution 4.0 for copyright, W3C Mode for patents, Apache 2.0 for source code) to a new IPR mode (Open Web Foundation 1.0 for copyright and patent, Apache 2.0 for source code). On 23 August 2023, the ToIP Steering Committee passed a resolution approving this rechartering that directed the Executive Director and the TSWG Co-Chairs to take the following steps to carry out this resolution:
Any TSWG member who wishes to declare any patent claim exclusions on work contributed to existing TSWG deliverables must do so by midnight Pacific Time on 25 October 2023. |
| 5 min | Nomination of new TSWG Co-Chair | Chairs | Kevin Griffin has volunteered to join Darrell O'Donnell and Drummond Reed as a third co-chair of the TSWG. DECISION: Kevin Griffin ______ as co-chair of the Technology Stack Working Group. |